From d025160cd1aaaa0834bb3ca74625787c01e6d4e8 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 13 Aug 2026 12:20:38 +0000 Subject: [PATCH] docs: publish channels: main api --- main/assets/css/just-the-docs-dark.css.map | 2 +- main/assets/css/just-the-docs-default.css.map | 2 +- main/assets/css/just-the-docs-light.css.map | 2 +- .../css/just-the-docs-meshtastic-dark.css.map | 2 +- .../css/just-the-docs-meshtastic.css.map | 2 +- main/assets/js/search-data.json | 68752 ++++++++-------- main/en/user.html | 2 +- 7 files changed, 34382 insertions(+), 34382 deletions(-) diff --git a/main/assets/css/just-the-docs-dark.css.map b/main/assets/css/just-the-docs-dark.css.map index 0fec68e74b..25bec729a5 100644 --- a/main/assets/css/just-the-docs-dark.css.map +++ b/main/assets/css/just-the-docs-dark.css.map @@ -1 +1 @@ -{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/vendor/accessible-pygments/github-dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/base.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/color_schemes/dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/skiptomain.scss","just-the-docs-dark.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAa;EAAqB;;;AAClC;EAAgB;EAAgB;EAAqB;AACrD;EAAkB;EAAiB;AACnC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAgB;EAAoB;AACpD;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAmB;EAAqB;AACzE;EAAkB;EAAgB;EAAqB;AACvD;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAmB;EAAqB;AACzE;EAAiB;EAAgB;EAA4B;AAC7D;EAAiB;EAAgB;EAAqB;AACtD;EAAkB;EAAgB;EAAmB;EAAqB;AAC1E;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAA4B;AAC7D;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAA0B;EAAgB;EAA6B;AACvE;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AC1FlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCJa;;;ADOf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OIiBY;EJhBZ,kBIYY;EJXZ;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OIjBY;;;AJoBd;EACE;EACA;;;AAGF;EACE,OCzDW;ED0DX;;;AAGF;EACE;EACA,uBInCY;EJoCZ;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBInEY;EJoEZ;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBD4BY;;ADpBV;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBDLQ;;ADpBV;EEuBA;IAKI;IACA,kBDTM;;;ACYR;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,ODnGY;EDVZ,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ3MW;;;AKCb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OL/KO;EKgLP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ONzEO;;AEUT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,OH/EI;;AGkFN;EACE,OHnFI;;AGyFR;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ON9JG;;AMiKL;EACE,ONlKG;;;AM2Kb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTRW;ESSX;EACA;EACA;EACA,kBNiBY;EMhBZ;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OTtEW;ESuEX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,ORTY;EQUZ,kBRfY;EQgBZ;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBRxBU;IQyBV;;;AAGF;EACE;EACA;;AAEA;EACE,OX/DO;;;AWoEb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBRjEY;EQkEZ,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBX3Ha;;;AW+HjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,OXrKS;EWsKT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,ORrJY;EQsJZ;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,ORjKY;EQkKZ;EACA,aR/GO;EQgHP,mBR1KY;;AFrBZ;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBRzMY;EQ0MZ;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBRzPU;;ADnBV;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBTQY;ESPZ;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBbDoB;EaEpB;EACA,eV+EY;;;AU1EhB;EACE,cVcY;;;AUqCd;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBbjEsB;EakEtB,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,OVtDU;EUuDV;;AAEA;AAAA;AAAA;EACE,MV1DQ;;AU6DV;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBb/KoB;EagLpB;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YblOsB;EaqOpB,ObpOoB;;;Aa2OxB;EACE,Yb7OsB;;;AcLxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OpBXW;EoBYX,kBjBkBY;EiBjBZ;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBlByBY;;;AkBtBd;EACI;EACA;EACA,elB4EY;EkB3EZ;EACA;;AAEA;EACI,OlB8BI;EkB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBoBM;EkBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBiDY;EkBhDZ;EACA;;AACA;EACE;EACA;EACA,OlBEM;EkBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBGY;EkBFZ;EACA;;AAEA;EACI,OlB/CG;EkBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBzDK;EkB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBxBY;EkByBZ;EACA;;AACA;EACE;EACA;EACA,OlB3EK;EkB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBtEY;EkBuEZ;EACA;;AAEA;EACI,OlBhHK;EkBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlB1HO;EkB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBjGY;EkBkGZ;EACA;;AACA;EACE;EACA;EACA,OlB5IO;EkB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #6e7681 }\n.highlight { background: #0d1117; color: #E6EDF3 }\n.highlight .c { color: #8B949E; font-style: italic } /* Comment */\n.highlight .err { color: #F85149 } /* Error */\n.highlight .esc { color: #E6EDF3 } /* Escape */\n.highlight .g { color: #E6EDF3 } /* Generic */\n.highlight .k { color: #FF7B72 } /* Keyword */\n.highlight .l { color: #A5D6FF } /* Literal */\n.highlight .n { color: #E6EDF3 } /* Name */\n.highlight .o { color: #FF7B72; font-weight: bold } /* Operator */\n.highlight .x { color: #E6EDF3 } /* Other */\n.highlight .p { color: #E6EDF3 } /* Punctuation */\n.highlight .ch { color: #8B949E; font-style: italic } /* Comment.Hashbang */\n.highlight .cm { color: #8B949E; font-style: italic } /* Comment.Multiline */\n.highlight .cp { color: #8B949E; font-weight: bold; font-style: italic } /* Comment.Preproc */\n.highlight .cpf { color: #8B949E; font-style: italic } /* Comment.PreprocFile */\n.highlight .c1 { color: #8B949E; font-style: italic } /* Comment.Single */\n.highlight .cs { color: #8B949E; font-weight: bold; font-style: italic } /* Comment.Special */\n.highlight .gd { color: #FFA198; background-color: #490202 } /* Generic.Deleted */\n.highlight .ge { color: #E6EDF3; font-style: italic } /* Generic.Emph */\n.highlight .ges { color: #E6EDF3; font-weight: bold; font-style: italic } /* Generic.EmphStrong */\n.highlight .gr { color: #FFA198 } /* Generic.Error */\n.highlight .gh { color: #79C0FF; font-weight: bold } /* Generic.Heading */\n.highlight .gi { color: #56D364; background-color: #0F5323 } /* Generic.Inserted */\n.highlight .go { color: #8B949E } /* Generic.Output */\n.highlight .gp { color: #8B949E } /* Generic.Prompt */\n.highlight .gs { color: #E6EDF3; font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #79C0FF } /* Generic.Subheading */\n.highlight .gt { color: #FF7B72 } /* Generic.Traceback */\n.highlight .g-Underline { color: #E6EDF3; text-decoration: underline } /* Generic.Underline */\n.highlight .kc { color: #79C0FF } /* Keyword.Constant */\n.highlight .kd { color: #FF7B72 } /* Keyword.Declaration */\n.highlight .kn { color: #FF7B72 } /* Keyword.Namespace */\n.highlight .kp { color: #79C0FF } /* Keyword.Pseudo */\n.highlight .kr { color: #FF7B72 } /* Keyword.Reserved */\n.highlight .kt { color: #FF7B72 } /* Keyword.Type */\n.highlight .ld { color: #79C0FF } /* Literal.Date */\n.highlight .m { color: #A5D6FF } /* Literal.Number */\n.highlight .s { color: #A5D6FF } /* Literal.String */\n.highlight .na { color: #E6EDF3 } /* Name.Attribute */\n.highlight .nb { color: #E6EDF3 } /* Name.Builtin */\n.highlight .nc { color: #F0883E; font-weight: bold } /* Name.Class */\n.highlight .no { color: #79C0FF; font-weight: bold } /* Name.Constant */\n.highlight .nd { color: #D2A8FF; font-weight: bold } /* Name.Decorator */\n.highlight .ni { color: #FFA657 } /* Name.Entity */\n.highlight .ne { color: #F0883E; font-weight: bold } /* Name.Exception */\n.highlight .nf { color: #D2A8FF; font-weight: bold } /* Name.Function */\n.highlight .nl { color: #79C0FF; font-weight: bold } /* Name.Label */\n.highlight .nn { color: #FF7B72 } /* Name.Namespace */\n.highlight .nx { color: #E6EDF3 } /* Name.Other */\n.highlight .py { color: #79C0FF } /* Name.Property */\n.highlight .nt { color: #7EE787 } /* Name.Tag */\n.highlight .nv { color: #79C0FF } /* Name.Variable */\n.highlight .ow { color: #FF7B72; font-weight: bold } /* Operator.Word */\n.highlight .pm { color: #E6EDF3 } /* Punctuation.Marker */\n.highlight .w { color: #6E7681 } /* Text.Whitespace */\n.highlight .mb { color: #A5D6FF } /* Literal.Number.Bin */\n.highlight .mf { color: #A5D6FF } /* Literal.Number.Float */\n.highlight .mh { color: #A5D6FF } /* Literal.Number.Hex */\n.highlight .mi { color: #A5D6FF } /* Literal.Number.Integer */\n.highlight .mo { color: #A5D6FF } /* Literal.Number.Oct */\n.highlight .sa { color: #79C0FF } /* Literal.String.Affix */\n.highlight .sb { color: #A5D6FF } /* Literal.String.Backtick */\n.highlight .sc { color: #A5D6FF } /* Literal.String.Char */\n.highlight .dl { color: #79C0FF } /* Literal.String.Delimiter */\n.highlight .sd { color: #A5D6FF } /* Literal.String.Doc */\n.highlight .s2 { color: #A5D6FF } /* Literal.String.Double */\n.highlight .se { color: #79C0FF } /* Literal.String.Escape */\n.highlight .sh { color: #79C0FF } /* Literal.String.Heredoc */\n.highlight .si { color: #A5D6FF } /* Literal.String.Interpol */\n.highlight .sx { color: #A5D6FF } /* Literal.String.Other */\n.highlight .sr { color: #79C0FF } /* Literal.String.Regex */\n.highlight .s1 { color: #A5D6FF } /* Literal.String.Single */\n.highlight .ss { color: #A5D6FF } /* Literal.String.Symbol */\n.highlight .bp { color: #E6EDF3 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #D2A8FF; font-weight: bold } /* Name.Function.Magic */\n.highlight .vc { color: #79C0FF } /* Name.Variable.Class */\n.highlight .vg { color: #79C0FF } /* Name.Variable.Global */\n.highlight .vi { color: #79C0FF } /* Name.Variable.Instance */\n.highlight .vm { color: #79C0FF } /* Name.Variable.Magic */\n.highlight .il { color: #A5D6FF } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","$color-scheme: dark;\n$body-background-color: $grey-dk-300;\n$body-heading-color: $grey-lt-000;\n$body-text-color: $grey-lt-300;\n$link-color: lighten($blue-000, 10%);\n$nav-child-link-color: $grey-dk-000;\n$sidebar-color: $grey-dk-300;\n$base-button-color: $grey-dk-250;\n$btn-primary-color: $blue-200;\n$code-background-color: #0d1117; // github-dark bg color\n$code-linenumber-color: #e6edf3; // github-dark line number color\n$feedback-color: darken($sidebar-color, 3%);\n$table-background-color: $grey-dk-250;\n$search-background-color: $grey-dk-250;\n$search-result-preview-color: $grey-lt-300;\n$border-color: $grey-dk-200;\n\n@import \"./vendor/accessible-pygments/github-dark\";\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/dark\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-300 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-300 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-300 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-300 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-300 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-300 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-dark.css"} \ No newline at end of file +{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/vendor/accessible-pygments/github-dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/base.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/color_schemes/dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/skiptomain.scss","just-the-docs-dark.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAa;EAAqB;;;AAClC;EAAgB;EAAgB;EAAqB;AACrD;EAAkB;EAAiB;AACnC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAgB;EAAoB;AACpD;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAmB;EAAqB;AACzE;EAAkB;EAAgB;EAAqB;AACvD;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAmB;EAAqB;AACzE;EAAiB;EAAgB;EAA4B;AAC7D;EAAiB;EAAgB;EAAqB;AACtD;EAAkB;EAAgB;EAAmB;EAAqB;AAC1E;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAA4B;AAC7D;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAA0B;EAAgB;EAA6B;AACvE;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AC1FlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCJa;;;ADOf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OIiBY;EJhBZ,kBIYY;EJXZ;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OIjBY;;;AJoBd;EACE;EACA;;;AAGF;EACE,OCzDW;ED0DX;;;AAGF;EACE;EACA,uBInCY;EJoCZ;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBInEY;EJoEZ;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBD4BY;;ADpBV;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBDLQ;;ADpBV;EEuBA;IAKI;IACA,kBDTM;;;ACYR;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,ODnGY;EDVZ,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ3MW;;;AKCb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OL/KO;EKgLP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ONzEO;;AEUT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,OH/EI;;AGkFN;EACE,OHnFI;;AGyFR;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ON9JG;;AMiKL;EACE,ONlKG;;;AM2Kb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTRW;ESSX;EACA;EACA;EACA,kBNiBY;EMhBZ;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OTtEW;ESuEX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,ORTY;EQUZ,kBRfY;EQgBZ;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBRxBU;IQyBV;;;AAGF;EACE;EACA;;AAEA;EACE,OX/DO;;;AWoEb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBRjEY;EQkEZ,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBX3Ha;;;AW+HjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,OXrKS;EWsKT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,ORrJY;EQsJZ;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,ORjKY;EQkKZ;EACA,aR/GO;EQgHP,mBR1KY;;AFrBZ;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBRzMY;EQ0MZ;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBRzPU;;ADnBV;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBTQY;ESPZ;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBbDoB;EaEpB;EACA,eV+EY;;;AU1EhB;EACE,cVcY;;;AUqCd;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBbjEsB;EakEtB,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,OVtDU;EUuDV;;AAEA;AAAA;AAAA;EACE,MV1DQ;;AU6DV;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBb/KoB;EagLpB;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YblOsB;EaqOpB,ObpOoB;;;Aa2OxB;EACE,Yb7OsB;;;AcLxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OpBXW;EoBYX,kBjBkBY;EiBjBZ;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBlByBY;;;AkBtBd;EACI;EACA;EACA,elB4EY;EkB3EZ;EACA;;AAEA;EACI,OlB8BI;EkB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBoBM;EkBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBiDY;EkBhDZ;EACA;;AACA;EACE;EACA;EACA,OlBEM;EkBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBGY;EkBFZ;EACA;;AAEA;EACI,OlB/CG;EkBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBzDK;EkB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBxBY;EkByBZ;EACA;;AACA;EACE;EACA;EACA,OlB3EK;EkB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBtEY;EkBuEZ;EACA;;AAEA;EACI,OlBhHK;EkBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlB1HO;EkB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBjGY;EkBkGZ;EACA;;AACA;EACE;EACA;EACA,OlB5IO;EkB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #6e7681 }\n.highlight { background: #0d1117; color: #E6EDF3 }\n.highlight .c { color: #8B949E; font-style: italic } /* Comment */\n.highlight .err { color: #F85149 } /* Error */\n.highlight .esc { color: #E6EDF3 } /* Escape */\n.highlight .g { color: #E6EDF3 } /* Generic */\n.highlight .k { color: #FF7B72 } /* Keyword */\n.highlight .l { color: #A5D6FF } /* Literal */\n.highlight .n { color: #E6EDF3 } /* Name */\n.highlight .o { color: #FF7B72; font-weight: bold } /* Operator */\n.highlight .x { color: #E6EDF3 } /* Other */\n.highlight .p { color: #E6EDF3 } /* Punctuation */\n.highlight .ch { color: #8B949E; font-style: italic } /* Comment.Hashbang */\n.highlight .cm { color: #8B949E; font-style: italic } /* Comment.Multiline */\n.highlight .cp { color: #8B949E; font-weight: bold; font-style: italic } /* Comment.Preproc */\n.highlight .cpf { color: #8B949E; font-style: italic } /* Comment.PreprocFile */\n.highlight .c1 { color: #8B949E; font-style: italic } /* Comment.Single */\n.highlight .cs { color: #8B949E; font-weight: bold; font-style: italic } /* Comment.Special */\n.highlight .gd { color: #FFA198; background-color: #490202 } /* Generic.Deleted */\n.highlight .ge { color: #E6EDF3; font-style: italic } /* Generic.Emph */\n.highlight .ges { color: #E6EDF3; font-weight: bold; font-style: italic } /* Generic.EmphStrong */\n.highlight .gr { color: #FFA198 } /* Generic.Error */\n.highlight .gh { color: #79C0FF; font-weight: bold } /* Generic.Heading */\n.highlight .gi { color: #56D364; background-color: #0F5323 } /* Generic.Inserted */\n.highlight .go { color: #8B949E } /* Generic.Output */\n.highlight .gp { color: #8B949E } /* Generic.Prompt */\n.highlight .gs { color: #E6EDF3; font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #79C0FF } /* Generic.Subheading */\n.highlight .gt { color: #FF7B72 } /* Generic.Traceback */\n.highlight .g-Underline { color: #E6EDF3; text-decoration: underline } /* Generic.Underline */\n.highlight .kc { color: #79C0FF } /* Keyword.Constant */\n.highlight .kd { color: #FF7B72 } /* Keyword.Declaration */\n.highlight .kn { color: #FF7B72 } /* Keyword.Namespace */\n.highlight .kp { color: #79C0FF } /* Keyword.Pseudo */\n.highlight .kr { color: #FF7B72 } /* Keyword.Reserved */\n.highlight .kt { color: #FF7B72 } /* Keyword.Type */\n.highlight .ld { color: #79C0FF } /* Literal.Date */\n.highlight .m { color: #A5D6FF } /* Literal.Number */\n.highlight .s { color: #A5D6FF } /* Literal.String */\n.highlight .na { color: #E6EDF3 } /* Name.Attribute */\n.highlight .nb { color: #E6EDF3 } /* Name.Builtin */\n.highlight .nc { color: #F0883E; font-weight: bold } /* Name.Class */\n.highlight .no { color: #79C0FF; font-weight: bold } /* Name.Constant */\n.highlight .nd { color: #D2A8FF; font-weight: bold } /* Name.Decorator */\n.highlight .ni { color: #FFA657 } /* Name.Entity */\n.highlight .ne { color: #F0883E; font-weight: bold } /* Name.Exception */\n.highlight .nf { color: #D2A8FF; font-weight: bold } /* Name.Function */\n.highlight .nl { color: #79C0FF; font-weight: bold } /* Name.Label */\n.highlight .nn { color: #FF7B72 } /* Name.Namespace */\n.highlight .nx { color: #E6EDF3 } /* Name.Other */\n.highlight .py { color: #79C0FF } /* Name.Property */\n.highlight .nt { color: #7EE787 } /* Name.Tag */\n.highlight .nv { color: #79C0FF } /* Name.Variable */\n.highlight .ow { color: #FF7B72; font-weight: bold } /* Operator.Word */\n.highlight .pm { color: #E6EDF3 } /* Punctuation.Marker */\n.highlight .w { color: #6E7681 } /* Text.Whitespace */\n.highlight .mb { color: #A5D6FF } /* Literal.Number.Bin */\n.highlight .mf { color: #A5D6FF } /* Literal.Number.Float */\n.highlight .mh { color: #A5D6FF } /* Literal.Number.Hex */\n.highlight .mi { color: #A5D6FF } /* Literal.Number.Integer */\n.highlight .mo { color: #A5D6FF } /* Literal.Number.Oct */\n.highlight .sa { color: #79C0FF } /* Literal.String.Affix */\n.highlight .sb { color: #A5D6FF } /* Literal.String.Backtick */\n.highlight .sc { color: #A5D6FF } /* Literal.String.Char */\n.highlight .dl { color: #79C0FF } /* Literal.String.Delimiter */\n.highlight .sd { color: #A5D6FF } /* Literal.String.Doc */\n.highlight .s2 { color: #A5D6FF } /* Literal.String.Double */\n.highlight .se { color: #79C0FF } /* Literal.String.Escape */\n.highlight .sh { color: #79C0FF } /* Literal.String.Heredoc */\n.highlight .si { color: #A5D6FF } /* Literal.String.Interpol */\n.highlight .sx { color: #A5D6FF } /* Literal.String.Other */\n.highlight .sr { color: #79C0FF } /* Literal.String.Regex */\n.highlight .s1 { color: #A5D6FF } /* Literal.String.Single */\n.highlight .ss { color: #A5D6FF } /* Literal.String.Symbol */\n.highlight .bp { color: #E6EDF3 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #D2A8FF; font-weight: bold } /* Name.Function.Magic */\n.highlight .vc { color: #79C0FF } /* Name.Variable.Class */\n.highlight .vg { color: #79C0FF } /* Name.Variable.Global */\n.highlight .vi { color: #79C0FF } /* Name.Variable.Instance */\n.highlight .vm { color: #79C0FF } /* Name.Variable.Magic */\n.highlight .il { color: #A5D6FF } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","$color-scheme: dark;\n$body-background-color: $grey-dk-300;\n$body-heading-color: $grey-lt-000;\n$body-text-color: $grey-lt-300;\n$link-color: lighten($blue-000, 10%);\n$nav-child-link-color: $grey-dk-000;\n$sidebar-color: $grey-dk-300;\n$base-button-color: $grey-dk-250;\n$btn-primary-color: $blue-200;\n$code-background-color: #0d1117; // github-dark bg color\n$code-linenumber-color: #e6edf3; // github-dark line number color\n$feedback-color: darken($sidebar-color, 3%);\n$table-background-color: $grey-dk-250;\n$search-background-color: $grey-dk-250;\n$search-result-preview-color: $grey-lt-300;\n$border-color: $grey-dk-200;\n\n@import \"./vendor/accessible-pygments/github-dark\";\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/dark\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-300 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-300 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-300 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-300 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-300 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-300 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-dark.css"} \ No newline at end of file diff --git a/main/assets/css/just-the-docs-default.css.map b/main/assets/css/just-the-docs-default.css.map index d63d471110..a565c3577f 100644 --- a/main/assets/css/just-the-docs-default.css.map +++ b/main/assets/css/just-the-docs-default.css.map @@ -1 +1 @@ -{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/base.scss","../../_sass/color_schemes/meshtastic.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/skiptomain.scss","just-the-docs-default.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBCTkB;EDUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;EEnGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFgFJ;EEvGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFoFJ;EE3GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFwFJ;EE/GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AF4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AG3HF;EACE;EACA;EACA;EACA,QTgFM;ES/EN,STuEK;EStEL;;AVME;EUZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QT8DK;ES7DL;EACA,eTmEc;ESlEd,YACE;EAEF;;AVdE;EUKJ;IAYI;IACA;IACA,WTwEmB;ISvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OZnCgB;EYoChB,kBZVwB;EYWxB;EACA;EACA;EACA;EACA;;AVvCE;EU2BJ;IAeI;IACA;IACA,kBZhDoB;IYiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OZnDO;;;AYwDb;EACE;EACA;EACA;EACA,cTIK;;ADlEH;EU0DJ;IAOI,cTGG;ISFH;;;AAGF;EACE;EACA;EACA;EACA,OTzDU;;;AS6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBZ5DwB;EY6DxB,4BTRc;ESSd,2BTTc;ESUd,YACE;;AVxFA;EU6EJ;IAeI;IACA,OTFmB;ISGnB;;;;AAIJ;EACE;EACA,eTrCK;ESsCL;;AXpFA;EACE;;AClBA;EUkGJ;IX5EI;;;ACtBA;EDOF;IACE;;;ACRA;EUkGJ;IXtFI;;;;AWiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBZnGa;;;AYuGjB;EACE;EACA,aT9DK;ES+DL,gBT/DK;;ADhEH;EU4HJ;IAMI;IACA;IACA,eTpEG;ISqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AXxIF;EACE;;ACRA;EU8IF;IXlIE;;;ACZA;EDHF;IACE;;;ACEA;EU8IF;IX5IE;;;AWqJF;EACE,OTtFG;ESuFH,QTvFG;ESwFH,cT1FG;ES2FH,OZzJS;EY0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OZtK4B;EYuK5B;EACA;;AX5LA;EACE;;ACYA;EUyKJ;IXjLI;;;;AW2LJ;EACE;EACA,aTrHK;ESsHL,gBTtHK;ESuHL,cTrHK;ESsHL,aTxHK;ESyHL,OZlL4B;EYmL5B;EACA,aT/GO;ESgHP,mBZ9Ka;;ACjBb;EACE;;ACEA;EUmLJ;IXjLI;;;ACFA;EUmLJ;IAaI;IACA;IACA,cTlIG;ISmIH;IACA;;;;AAIJ;EACE,YT1IK;;;AS6IP;EACE;;;AAGF;EACE;;AX1MA;EACE;;ACRA;EUgNJ;IXpMI;;;;AWyMJ;EACE;EACA,OTrJK;ESsJL,QTtJK;ESuJL;EACA,OTnJK;ESoJL,QTpJK;ESqJL,kBZpMwB;EYqMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QTxLI;ESyLJ;;AVjQA;EU+PF;IAKI,OTzKiB;IS0KjB,YACE;;;AAKN;EACE,kBZpPsB;;AExBtB;EU2QF;IAII;;;AV/QF;EUmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;AVlSF;EUwSA;IACE;IACA;IACA;;;AAIJ;EACE,aTxOI;;ADxEJ;EU+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eV0EK;EUzEL;EACA,eVkFc;EUjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBbIuB;EaHvB;EACA;;AZNA;AAAA;EACE;;ACRA;EWOJ;AAAA;IZKI;;;AYKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBVkCD;;;AU3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBdcoB;EcbpB;EACA,eX+EY;;;AW1EhB;EACE,cdUa;;;AcyCf;AAAA;AAAA;EAGE;EACA,eXMK;EWLL,kBdlDsB;EcmDtB,eXgBc;EWfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OXLG;EWMH;EACA;EACA;EACA;EACA,SXVG;EWWH;EACA;EACA,OdhFc;EciFd;;AAEA;AAAA;AAAA;EACE,MdpFY;;AcuFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eXrEK;;AW6CL;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SXpFG;EWqFH;EACA;EACA,eX3EY;;;AWmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBdhKoB;EciKpB;;Ab9KF;AAAA;EACE;;ACEA;EYsKF;AAAA;IbpKE;;;Aa8KF;EACE;EACA,eXjHG;EWkHH,cXlHG;;AWqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SX9HK;EW+HL,eX/HK;EWgIL;EACA;EACA,eXtHc;;AWwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YdnNsB;EcsNpB,OdrNoB;;;Ac4NxB;EACE,Yd9NsB;;;AepBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AdrBE;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AfhHA;EACE;;ACYA;EeZJ;IhBII;;;;AAKF;EACE;;ACEA;EeRJ;IhBUI;;;;AAKF;EACE;;ACRA;EeJJ;IhBgBI;;;;AAKF;EACE;;AClBA;EeAJ;IhBsBI;;;;AAKF;EACE;;AC5BA;EeIJ;IhB4BI;;;;AAKF;EACE;;ACtCA;EeQJ;IhBkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EeYJ;IhB0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EegBJ;IhBiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EeoBJ;IhBwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EewBJ;IhB+DI;;;;AgB3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,adxDiB;;;Ac2DnB;EACE,ad1DyB;;;Ac6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AjBlCA;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AjB7GA;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OrBCW;EqBAX,kBrBNsB;EqBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACnBF;EACE;;;AAGF;EACI;EACA;EACA,enB2EY;EmB1EZ;EACA;;AAEA;EACI,OnB6BI;EmB5BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBmBM;EmBlBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBgDY;EmB/CZ;EACA;;AACA;EACE;EACA;EACA,OnBCM;EmBAN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBEY;EmBDZ;EACA;;AAEA;EACI,OnBhDG;EmBiDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB1DK;EmB2DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBzBY;EmB0BZ;EACA;;AACA;EACE;EACA;EACA,OnB5EK;EmB6EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBvEY;EmBwEZ;EACA;;AAEA;EACI,OnBjHK;EmBkHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB3HO;EmB4HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBlGY;EmBmGZ;EACA;;AACA;EACE;EACA;EACA,OnB7IO;EmB8IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Light color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.2 (Light Scheme)\n//\n// Brand colors:\n// Primary (Light): #2D8F52 (Green 700)\n// Surface (Light): #F5F6FA (Neutral 50)\n\n$color-scheme: light;\n\n// Body / page background\n$body-background-color: #F5F6FA; // Neutral 50 — surfaceLight\n$sidebar-color: #ECEDF3; // Neutral 100 — surfaceContainerLight\n$body-text-color: #2C2D3C; // Neutral 800 — onSurfaceLight\n$body-heading-color: #2C2D3C; // Neutral 800\n\n// Links\n$link-color: #2D8F52; // Green 700 — primaryLight\n$nav-link-color: #2D8F52; // Green 700\n\n// Navigation\n$nav-child-link-color: #555668; // Neutral 600 — secondaryLight\n$search-result-preview-color: #555668;\n\n// Code\n$code-background-color: #ECEDF3; // Neutral 100\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #D5D6E0; // Neutral 200 — outlineVariantLight\n$table-background-color: #F5F6FA; // Neutral 50\n\n// Buttons\n$btn-primary-color: #2D8F52; // Green 700\n\n// Feedback / callouts\n$feedback-color: #E0E1EB; // surfaceContainerHighLight\n\n// Search\n$search-background-color: #FFFFFF; // surfaceContainerLowestLight\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-default.css"} \ No newline at end of file +{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/base.scss","../../_sass/color_schemes/meshtastic.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/skiptomain.scss","just-the-docs-default.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBCTkB;EDUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;EEnGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFgFJ;EEvGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFoFJ;EE3GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFwFJ;EE/GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AF4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AG3HF;EACE;EACA;EACA;EACA,QTgFM;ES/EN,STuEK;EStEL;;AVME;EUZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QT8DK;ES7DL;EACA,eTmEc;ESlEd,YACE;EAEF;;AVdE;EUKJ;IAYI;IACA;IACA,WTwEmB;ISvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OZnCgB;EYoChB,kBZVwB;EYWxB;EACA;EACA;EACA;EACA;;AVvCE;EU2BJ;IAeI;IACA;IACA,kBZhDoB;IYiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OZnDO;;;AYwDb;EACE;EACA;EACA;EACA,cTIK;;ADlEH;EU0DJ;IAOI,cTGG;ISFH;;;AAGF;EACE;EACA;EACA;EACA,OTzDU;;;AS6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBZ5DwB;EY6DxB,4BTRc;ESSd,2BTTc;ESUd,YACE;;AVxFA;EU6EJ;IAeI;IACA,OTFmB;ISGnB;;;;AAIJ;EACE;EACA,eTrCK;ESsCL;;AXpFA;EACE;;AClBA;EUkGJ;IX5EI;;;ACtBA;EDOF;IACE;;;ACRA;EUkGJ;IXtFI;;;;AWiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBZnGa;;;AYuGjB;EACE;EACA,aT9DK;ES+DL,gBT/DK;;ADhEH;EU4HJ;IAMI;IACA;IACA,eTpEG;ISqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AXxIF;EACE;;ACRA;EU8IF;IXlIE;;;ACZA;EDHF;IACE;;;ACEA;EU8IF;IX5IE;;;AWqJF;EACE,OTtFG;ESuFH,QTvFG;ESwFH,cT1FG;ES2FH,OZzJS;EY0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OZtK4B;EYuK5B;EACA;;AX5LA;EACE;;ACYA;EUyKJ;IXjLI;;;;AW2LJ;EACE;EACA,aTrHK;ESsHL,gBTtHK;ESuHL,cTrHK;ESsHL,aTxHK;ESyHL,OZlL4B;EYmL5B;EACA,aT/GO;ESgHP,mBZ9Ka;;ACjBb;EACE;;ACEA;EUmLJ;IXjLI;;;ACFA;EUmLJ;IAaI;IACA;IACA,cTlIG;ISmIH;IACA;;;;AAIJ;EACE,YT1IK;;;AS6IP;EACE;;;AAGF;EACE;;AX1MA;EACE;;ACRA;EUgNJ;IXpMI;;;;AWyMJ;EACE;EACA,OTrJK;ESsJL,QTtJK;ESuJL;EACA,OTnJK;ESoJL,QTpJK;ESqJL,kBZpMwB;EYqMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QTxLI;ESyLJ;;AVjQA;EU+PF;IAKI,OTzKiB;IS0KjB,YACE;;;AAKN;EACE,kBZpPsB;;AExBtB;EU2QF;IAII;;;AV/QF;EUmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;AVlSF;EUwSA;IACE;IACA;IACA;;;AAIJ;EACE,aTxOI;;ADxEJ;EU+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eV0EK;EUzEL;EACA,eVkFc;EUjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBbIuB;EaHvB;EACA;;AZNA;AAAA;EACE;;ACRA;EWOJ;AAAA;IZKI;;;AYKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBVkCD;;;AU3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBdcoB;EcbpB;EACA,eX+EY;;;AW1EhB;EACE,cdUa;;;AcyCf;AAAA;AAAA;EAGE;EACA,eXMK;EWLL,kBdlDsB;EcmDtB,eXgBc;EWfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OXLG;EWMH;EACA;EACA;EACA;EACA,SXVG;EWWH;EACA;EACA,OdhFc;EciFd;;AAEA;AAAA;AAAA;EACE,MdpFY;;AcuFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eXrEK;;AW6CL;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SXpFG;EWqFH;EACA;EACA,eX3EY;;;AWmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBdhKoB;EciKpB;;Ab9KF;AAAA;EACE;;ACEA;EYsKF;AAAA;IbpKE;;;Aa8KF;EACE;EACA,eXjHG;EWkHH,cXlHG;;AWqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SX9HK;EW+HL,eX/HK;EWgIL;EACA;EACA,eXtHc;;AWwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YdnNsB;EcsNpB,OdrNoB;;;Ac4NxB;EACE,Yd9NsB;;;AepBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AdrBE;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AfhHA;EACE;;ACYA;EeZJ;IhBII;;;;AAKF;EACE;;ACEA;EeRJ;IhBUI;;;;AAKF;EACE;;ACRA;EeJJ;IhBgBI;;;;AAKF;EACE;;AClBA;EeAJ;IhBsBI;;;;AAKF;EACE;;AC5BA;EeIJ;IhB4BI;;;;AAKF;EACE;;ACtCA;EeQJ;IhBkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EeYJ;IhB0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EegBJ;IhBiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EeoBJ;IhBwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EewBJ;IhB+DI;;;;AgB3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,adxDiB;;;Ac2DnB;EACE,ad1DyB;;;Ac6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AjBlCA;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AjB7GA;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OrBCW;EqBAX,kBrBNsB;EqBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACnBF;EACE;;;AAGF;EACI;EACA;EACA,enB2EY;EmB1EZ;EACA;;AAEA;EACI,OnB6BI;EmB5BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBmBM;EmBlBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBgDY;EmB/CZ;EACA;;AACA;EACE;EACA;EACA,OnBCM;EmBAN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBEY;EmBDZ;EACA;;AAEA;EACI,OnBhDG;EmBiDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB1DK;EmB2DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBzBY;EmB0BZ;EACA;;AACA;EACE;EACA;EACA,OnB5EK;EmB6EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBvEY;EmBwEZ;EACA;;AAEA;EACI,OnBjHK;EmBkHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB3HO;EmB4HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBlGY;EmBmGZ;EACA;;AACA;EACE;EACA;EACA,OnB7IO;EmB8IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Light color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.2 (Light Scheme)\n//\n// Brand colors:\n// Primary (Light): #2D8F52 (Green 700)\n// Surface (Light): #F5F6FA (Neutral 50)\n\n$color-scheme: light;\n\n// Body / page background\n$body-background-color: #F5F6FA; // Neutral 50 — surfaceLight\n$sidebar-color: #ECEDF3; // Neutral 100 — surfaceContainerLight\n$body-text-color: #2C2D3C; // Neutral 800 — onSurfaceLight\n$body-heading-color: #2C2D3C; // Neutral 800\n\n// Links\n$link-color: #2D8F52; // Green 700 — primaryLight\n$nav-link-color: #2D8F52; // Green 700\n\n// Navigation\n$nav-child-link-color: #555668; // Neutral 600 — secondaryLight\n$search-result-preview-color: #555668;\n\n// Code\n$code-background-color: #ECEDF3; // Neutral 100\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #D5D6E0; // Neutral 200 — outlineVariantLight\n$table-background-color: #F5F6FA; // Neutral 50\n\n// Buttons\n$btn-primary-color: #2D8F52; // Green 700\n\n// Feedback / callouts\n$feedback-color: #E0E1EB; // surfaceContainerHighLight\n\n// Search\n$search-background-color: #FFFFFF; // surfaceContainerLowestLight\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-default.css"} \ No newline at end of file diff --git a/main/assets/css/just-the-docs-light.css.map b/main/assets/css/just-the-docs-light.css.map index 3ee8328dc0..3a13424ea9 100644 --- a/main/assets/css/just-the-docs-light.css.map +++ b/main/assets/css/just-the-docs-light.css.map @@ -1 +1 @@ -{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/base.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/skiptomain.scss","just-the-docs-light.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCJa;;;ADOf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OIUY;EJTZ,kBIOM;EJNN;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OIlBY;;;AJqBd;EACE;EACA;;;AAGF;EACE,OItBW;EJuBX;;;AAGF;EACE;EACA,uBI/BY;EJgCZ;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBI/DY;EJgEZ;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBD6BY;;ADrBV;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBDJQ;;ADrBV;EEuBA;IAKI;IACA,kBDdA;;;ACiBF;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,ODpGY;EDTZ,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,ODxKW;;;AElCb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OF5IO;EE6IP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,OHtCO;;ADzBT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,OH9EI;;AGiFN;EACE,OHlFI;;AGwFR;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,OH3HG;;AG8HL;EACE,OH/HG;;;AGwIb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,ON2BW;EM1BX;EACA;EACA;EACA,kBTTkB;ESUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,ONnCW;EMoCX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,ORhBY;EQiBZ,kBRnBM;EQoBN;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBR7BI;IQ8BJ;;;AAGF;EACE;EACA;;AAEA;EACE,OR5BO;;;AQiCb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBRrEM;EQsEN,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBX5Ha;;;AWgIjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,ORlIS;EQmIT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OR5JY;EQ6JZ;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,ORxKY;EQyKZ;EACA,aR/GO;EQgHP,mBRtKY;;AFzBZ;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBR7MM;EQ8MN;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBR7PI;;ADfJ;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBTIM;ESHN;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBVmBI;EUlBJ;EACA,eV+EY;;;AU1EhB;EACE,cVkBY;;;AUiCd;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBV7CM;EU8CN,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,OV7DU;EU8DV;;AAEA;AAAA;AAAA;EACE,MVjEQ;;AUoEV;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBV3JI;EU4JJ;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YV9MM;EUmNJ,OVjNU;;;AUsNd;EACE,YVzNM;;;AWzBR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OjBwBW;EiBvBX,kBjBaM;EiBZN;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACtBF;EACE,kBlBsBM;;;AkBnBR;EACI;EACA;EACA,elB8EY;EkB7EZ;EACA;;AAEA;EACI,OlBgCI;EkB/BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBsBM;EkBrBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBmDY;EkBlDZ;EACA;;AACA;EACE;EACA;EACA,OlBIM;EkBHN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBKY;EkBJZ;EACA;;AAEA;EACI,OlB7CG;EkB8CH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBvDK;EkBwDL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBtBY;EkBuBZ;EACA;;AACA;EACE;EACA;EACA,OlBzEK;EkB0EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBpEY;EkBqEZ;EACA;;AAEA;EACI,OlB9GK;EkB+GL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBxHO;EkByHP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elB/FY;EkBgGZ;EACA;;AACA;EACE;EACA;EACA,OlB1IO;EkB2IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-light.css"} \ No newline at end of file +{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/base.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/skiptomain.scss","just-the-docs-light.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCJa;;;ADOf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OIUY;EJTZ,kBIOM;EJNN;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OIlBY;;;AJqBd;EACE;EACA;;;AAGF;EACE,OItBW;EJuBX;;;AAGF;EACE;EACA,uBI/BY;EJgCZ;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBI/DY;EJgEZ;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBD6BY;;ADrBV;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBDJQ;;ADrBV;EEuBA;IAKI;IACA,kBDdA;;;ACiBF;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,ODpGY;EDTZ,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,ODxKW;;;AElCb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OF5IO;EE6IP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,OHtCO;;ADzBT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,OH9EI;;AGiFN;EACE,OHlFI;;AGwFR;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,OH3HG;;AG8HL;EACE,OH/HG;;;AGwIb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,ON2BW;EM1BX;EACA;EACA;EACA,kBTTkB;ESUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,ONnCW;EMoCX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,ORhBY;EQiBZ,kBRnBM;EQoBN;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBR7BI;IQ8BJ;;;AAGF;EACE;EACA;;AAEA;EACE,OR5BO;;;AQiCb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBRrEM;EQsEN,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBX5Ha;;;AWgIjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,ORlIS;EQmIT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OR5JY;EQ6JZ;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,ORxKY;EQyKZ;EACA,aR/GO;EQgHP,mBRtKY;;AFzBZ;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBR7MM;EQ8MN;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBR7PI;;ADfJ;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBTIM;ESHN;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBVmBI;EUlBJ;EACA,eV+EY;;;AU1EhB;EACE,cVkBY;;;AUiCd;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBV7CM;EU8CN,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,OV7DU;EU8DV;;AAEA;AAAA;AAAA;EACE,MVjEQ;;AUoEV;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBV3JI;EU4JJ;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YV9MM;EUmNJ,OVjNU;;;AUsNd;EACE,YVzNM;;;AWzBR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OjBwBW;EiBvBX,kBjBaM;EiBZN;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACtBF;EACE,kBlBsBM;;;AkBnBR;EACI;EACA;EACA,elB8EY;EkB7EZ;EACA;;AAEA;EACI,OlBgCI;EkB/BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBsBM;EkBrBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBmDY;EkBlDZ;EACA;;AACA;EACE;EACA;EACA,OlBIM;EkBHN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBKY;EkBJZ;EACA;;AAEA;EACI,OlB7CG;EkB8CH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBvDK;EkBwDL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBtBY;EkBuBZ;EACA;;AACA;EACE;EACA;EACA,OlBzEK;EkB0EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBpEY;EkBqEZ;EACA;;AAEA;EACI,OlB9GK;EkB+GL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBxHO;EkByHP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elB/FY;EkBgGZ;EACA;;AACA;EACE;EACA;EACA,OlB1IO;EkB2IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-light.css"} \ No newline at end of file diff --git a/main/assets/css/just-the-docs-meshtastic-dark.css.map b/main/assets/css/just-the-docs-meshtastic-dark.css.map index 73fcf5f0e3..cbcd252e99 100644 --- a/main/assets/css/just-the-docs-meshtastic-dark.css.map +++ b/main/assets/css/just-the-docs-meshtastic-dark.css.map @@ -1 +1 @@ -{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/base.scss","../../_sass/color_schemes/meshtastic-dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/skiptomain.scss","just-the-docs-meshtastic-dark.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBTiBkB;EShBlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OXnCgB;EWoChB,kBXTwB;EWUxB;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBXhDoB;IWiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OXnDO;;;AWwDb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBX3DwB;EW4DxB,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBXlGa;;;AWsGjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,OXzJS;EW0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OXtK4B;EWuK5B;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,OXlL4B;EWmL5B;EACA,aR/GO;EQgHP,mBX9Ka;;ACjBb;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBXnMwB;EWoMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBXnPsB;;AEzBtB;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBZIuB;EYHvB;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBbcoB;EabpB;EACA,eV+EY;;;AU1EhB;EACE,cbUa;;;AayCf;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBblDsB;EamDtB,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,ObhFc;EaiFd;;AAEA;AAAA;AAAA;EACE,MbpFY;;AauFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBbhKoB;EaiKpB;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YbnNsB;EasNpB,ObrNoB;;;Aa4NxB;EACE,Yb9NsB;;;AcpBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OpBCW;EoBAX,kBpBNsB;EoBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBrBCsB;;;AqBExB;EACI;EACA;EACA,elB4EY;EkB3EZ;EACA;;AAEA;EACI,OlB8BI;EkB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBoBM;EkBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBiDY;EkBhDZ;EACA;;AACA;EACE;EACA;EACA,OlBEM;EkBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBGY;EkBFZ;EACA;;AAEA;EACI,OlB/CG;EkBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBzDK;EkB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBxBY;EkByBZ;EACA;;AACA;EACE;EACA;EACA,OlB3EK;EkB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBtEY;EkBuEZ;EACA;;AAEA;EACI,OlBhHK;EkBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlB1HO;EkB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBjGY;EkBkGZ;EACA;;AACA;EACE;EACA;EACA,OlB5IO;EkB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Dark color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.3 (Dark Scheme)\n//\n// Brand colors:\n// Primary (Dark): #67EA94 (Green 500)\n// Surface (Dark): #1A1B26 (Neutral 900)\n\n$color-scheme: dark;\n\n// Body / page background\n$body-background-color: #1A1B26; // Neutral 900 — surfaceDark\n$sidebar-color: #1A1B26; // Neutral 900\n$body-text-color: #ECEDF3; // Neutral 100 — onSurfaceDark\n$body-heading-color: #ECEDF3; // Neutral 100\n\n// Links\n$link-color: #67EA94; // Green 500 — primaryDark\n$nav-link-color: #67EA94; // Green 500\n\n// Navigation\n$nav-child-link-color: #B8BAC8; // Neutral 300 — secondaryDark\n$search-result-preview-color: #B8BAC8;\n\n// Code\n$code-background-color: #0F1017; // Neutral 950 — surfaceContainerLowestDark\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #3D3E50; // Neutral 700 — outlineVariantDark\n$table-background-color: #242533; // Interpolated — surfaceContainerDark\n\n// Buttons\n$btn-primary-color: #67EA94; // Green 500\n$base-button-color: #2C2D3C; // Neutral 800\n\n// Feedback / callouts\n$feedback-color: #242533; // surfaceContainerDark\n\n// Search\n$search-background-color: #242533; // surfaceContainerDark\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic-dark\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-meshtastic-dark.css"} \ No newline at end of file +{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/base.scss","../../_sass/color_schemes/meshtastic-dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/skiptomain.scss","just-the-docs-meshtastic-dark.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBTiBkB;EShBlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OXnCgB;EWoChB,kBXTwB;EWUxB;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBXhDoB;IWiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OXnDO;;;AWwDb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBX3DwB;EW4DxB,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBXlGa;;;AWsGjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,OXzJS;EW0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OXtK4B;EWuK5B;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,OXlL4B;EWmL5B;EACA,aR/GO;EQgHP,mBX9Ka;;ACjBb;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBXnMwB;EWoMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBXnPsB;;AEzBtB;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBZIuB;EYHvB;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBbcoB;EabpB;EACA,eV+EY;;;AU1EhB;EACE,cbUa;;;AayCf;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBblDsB;EamDtB,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,ObhFc;EaiFd;;AAEA;AAAA;AAAA;EACE,MbpFY;;AauFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBbhKoB;EaiKpB;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YbnNsB;EasNpB,ObrNoB;;;Aa4NxB;EACE,Yb9NsB;;;AcpBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OpBCW;EoBAX,kBpBNsB;EoBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBrBCsB;;;AqBExB;EACI;EACA;EACA,elB4EY;EkB3EZ;EACA;;AAEA;EACI,OlB8BI;EkB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBoBM;EkBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBiDY;EkBhDZ;EACA;;AACA;EACE;EACA;EACA,OlBEM;EkBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBGY;EkBFZ;EACA;;AAEA;EACI,OlB/CG;EkBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBzDK;EkB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBxBY;EkByBZ;EACA;;AACA;EACE;EACA;EACA,OlB3EK;EkB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBtEY;EkBuEZ;EACA;;AAEA;EACI,OlBhHK;EkBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlB1HO;EkB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBjGY;EkBkGZ;EACA;;AACA;EACE;EACA;EACA,OlB5IO;EkB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Dark color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.3 (Dark Scheme)\n//\n// Brand colors:\n// Primary (Dark): #67EA94 (Green 500)\n// Surface (Dark): #1A1B26 (Neutral 900)\n\n$color-scheme: dark;\n\n// Body / page background\n$body-background-color: #1A1B26; // Neutral 900 — surfaceDark\n$sidebar-color: #1A1B26; // Neutral 900\n$body-text-color: #ECEDF3; // Neutral 100 — onSurfaceDark\n$body-heading-color: #ECEDF3; // Neutral 100\n\n// Links\n$link-color: #67EA94; // Green 500 — primaryDark\n$nav-link-color: #67EA94; // Green 500\n\n// Navigation\n$nav-child-link-color: #B8BAC8; // Neutral 300 — secondaryDark\n$search-result-preview-color: #B8BAC8;\n\n// Code\n$code-background-color: #0F1017; // Neutral 950 — surfaceContainerLowestDark\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #3D3E50; // Neutral 700 — outlineVariantDark\n$table-background-color: #242533; // Interpolated — surfaceContainerDark\n\n// Buttons\n$btn-primary-color: #67EA94; // Green 500\n$base-button-color: #2C2D3C; // Neutral 800\n\n// Feedback / callouts\n$feedback-color: #242533; // surfaceContainerDark\n\n// Search\n$search-background-color: #242533; // surfaceContainerDark\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic-dark\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-meshtastic-dark.css"} \ No newline at end of file diff --git a/main/assets/css/just-the-docs-meshtastic.css.map b/main/assets/css/just-the-docs-meshtastic.css.map index 2e1ae5d9bc..4f7ab2d0e3 100644 --- a/main/assets/css/just-the-docs-meshtastic.css.map +++ b/main/assets/css/just-the-docs-meshtastic.css.map @@ -1 +1 @@ -{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/base.scss","../../_sass/color_schemes/meshtastic.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-2946-nubju6/_sass/skiptomain.scss","just-the-docs-meshtastic.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBCTkB;EDUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;EEnGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFgFJ;EEvGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFoFJ;EE3GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFwFJ;EE/GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AF4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AG3HF;EACE;EACA;EACA;EACA,QTgFM;ES/EN,STuEK;EStEL;;AVME;EUZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QT8DK;ES7DL;EACA,eTmEc;ESlEd,YACE;EAEF;;AVdE;EUKJ;IAYI;IACA;IACA,WTwEmB;ISvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OZnCgB;EYoChB,kBZVwB;EYWxB;EACA;EACA;EACA;EACA;;AVvCE;EU2BJ;IAeI;IACA;IACA,kBZhDoB;IYiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OZnDO;;;AYwDb;EACE;EACA;EACA;EACA,cTIK;;ADlEH;EU0DJ;IAOI,cTGG;ISFH;;;AAGF;EACE;EACA;EACA;EACA,OTzDU;;;AS6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBZ5DwB;EY6DxB,4BTRc;ESSd,2BTTc;ESUd,YACE;;AVxFA;EU6EJ;IAeI;IACA,OTFmB;ISGnB;;;;AAIJ;EACE;EACA,eTrCK;ESsCL;;AXpFA;EACE;;AClBA;EUkGJ;IX5EI;;;ACtBA;EDOF;IACE;;;ACRA;EUkGJ;IXtFI;;;;AWiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBZnGa;;;AYuGjB;EACE;EACA,aT9DK;ES+DL,gBT/DK;;ADhEH;EU4HJ;IAMI;IACA;IACA,eTpEG;ISqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AXxIF;EACE;;ACRA;EU8IF;IXlIE;;;ACZA;EDHF;IACE;;;ACEA;EU8IF;IX5IE;;;AWqJF;EACE,OTtFG;ESuFH,QTvFG;ESwFH,cT1FG;ES2FH,OZzJS;EY0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OZtK4B;EYuK5B;EACA;;AX5LA;EACE;;ACYA;EUyKJ;IXjLI;;;;AW2LJ;EACE;EACA,aTrHK;ESsHL,gBTtHK;ESuHL,cTrHK;ESsHL,aTxHK;ESyHL,OZlL4B;EYmL5B;EACA,aT/GO;ESgHP,mBZ9Ka;;ACjBb;EACE;;ACEA;EUmLJ;IXjLI;;;ACFA;EUmLJ;IAaI;IACA;IACA,cTlIG;ISmIH;IACA;;;;AAIJ;EACE,YT1IK;;;AS6IP;EACE;;;AAGF;EACE;;AX1MA;EACE;;ACRA;EUgNJ;IXpMI;;;;AWyMJ;EACE;EACA,OTrJK;ESsJL,QTtJK;ESuJL;EACA,OTnJK;ESoJL,QTpJK;ESqJL,kBZpMwB;EYqMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QTxLI;ESyLJ;;AVjQA;EU+PF;IAKI,OTzKiB;IS0KjB,YACE;;;AAKN;EACE,kBZpPsB;;AExBtB;EU2QF;IAII;;;AV/QF;EUmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;AVlSF;EUwSA;IACE;IACA;IACA;;;AAIJ;EACE,aTxOI;;ADxEJ;EU+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eV0EK;EUzEL;EACA,eVkFc;EUjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBbIuB;EaHvB;EACA;;AZNA;AAAA;EACE;;ACRA;EWOJ;AAAA;IZKI;;;AYKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBVkCD;;;AU3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBdcoB;EcbpB;EACA,eX+EY;;;AW1EhB;EACE,cdUa;;;AcyCf;AAAA;AAAA;EAGE;EACA,eXMK;EWLL,kBdlDsB;EcmDtB,eXgBc;EWfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OXLG;EWMH;EACA;EACA;EACA;EACA,SXVG;EWWH;EACA;EACA,OdhFc;EciFd;;AAEA;AAAA;AAAA;EACE,MdpFY;;AcuFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eXrEK;;AW6CL;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SXpFG;EWqFH;EACA;EACA,eX3EY;;;AWmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBdhKoB;EciKpB;;Ab9KF;AAAA;EACE;;ACEA;EYsKF;AAAA;IbpKE;;;Aa8KF;EACE;EACA,eXjHG;EWkHH,cXlHG;;AWqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SX9HK;EW+HL,eX/HK;EWgIL;EACA;EACA,eXtHc;;AWwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YdnNsB;EcsNpB,OdrNoB;;;Ac4NxB;EACE,Yd9NsB;;;AepBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AdrBE;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AfhHA;EACE;;ACYA;EeZJ;IhBII;;;;AAKF;EACE;;ACEA;EeRJ;IhBUI;;;;AAKF;EACE;;ACRA;EeJJ;IhBgBI;;;;AAKF;EACE;;AClBA;EeAJ;IhBsBI;;;;AAKF;EACE;;AC5BA;EeIJ;IhB4BI;;;;AAKF;EACE;;ACtCA;EeQJ;IhBkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EeYJ;IhB0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EegBJ;IhBiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EeoBJ;IhBwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EewBJ;IhB+DI;;;;AgB3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,adxDiB;;;Ac2DnB;EACE,ad1DyB;;;Ac6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AjBlCA;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AjB7GA;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OrBCW;EqBAX,kBrBNsB;EqBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBtBCsB;;;AsBExB;EACI;EACA;EACA,enB4EY;EmB3EZ;EACA;;AAEA;EACI,OnB8BI;EmB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBoBM;EmBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBiDY;EmBhDZ;EACA;;AACA;EACE;EACA;EACA,OnBEM;EmBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBGY;EmBFZ;EACA;;AAEA;EACI,OnB/CG;EmBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBzDK;EmB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBxBY;EmByBZ;EACA;;AACA;EACE;EACA;EACA,OnB3EK;EmB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBtEY;EmBuEZ;EACA;;AAEA;EACI,OnBhHK;EmBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB1HO;EmB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBjGY;EmBkGZ;EACA;;AACA;EACE;EACA;EACA,OnB5IO;EmB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Light color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.2 (Light Scheme)\n//\n// Brand colors:\n// Primary (Light): #2D8F52 (Green 700)\n// Surface (Light): #F5F6FA (Neutral 50)\n\n$color-scheme: light;\n\n// Body / page background\n$body-background-color: #F5F6FA; // Neutral 50 — surfaceLight\n$sidebar-color: #ECEDF3; // Neutral 100 — surfaceContainerLight\n$body-text-color: #2C2D3C; // Neutral 800 — onSurfaceLight\n$body-heading-color: #2C2D3C; // Neutral 800\n\n// Links\n$link-color: #2D8F52; // Green 700 — primaryLight\n$nav-link-color: #2D8F52; // Green 700\n\n// Navigation\n$nav-child-link-color: #555668; // Neutral 600 — secondaryLight\n$search-result-preview-color: #555668;\n\n// Code\n$code-background-color: #ECEDF3; // Neutral 100\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #D5D6E0; // Neutral 200 — outlineVariantLight\n$table-background-color: #F5F6FA; // Neutral 50\n\n// Buttons\n$btn-primary-color: #2D8F52; // Green 700\n\n// Feedback / callouts\n$feedback-color: #E0E1EB; // surfaceContainerHighLight\n\n// Search\n$search-background-color: #FFFFFF; // surfaceContainerLowestLight\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-meshtastic.css"} \ No newline at end of file +{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/base.scss","../../_sass/color_schemes/meshtastic.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260813-4025-mbnafv/_sass/skiptomain.scss","just-the-docs-meshtastic.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBCTkB;EDUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;EEnGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFgFJ;EEvGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFoFJ;EE3GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFwFJ;EE/GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AF4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AG3HF;EACE;EACA;EACA;EACA,QTgFM;ES/EN,STuEK;EStEL;;AVME;EUZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QT8DK;ES7DL;EACA,eTmEc;ESlEd,YACE;EAEF;;AVdE;EUKJ;IAYI;IACA;IACA,WTwEmB;ISvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OZnCgB;EYoChB,kBZVwB;EYWxB;EACA;EACA;EACA;EACA;;AVvCE;EU2BJ;IAeI;IACA;IACA,kBZhDoB;IYiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OZnDO;;;AYwDb;EACE;EACA;EACA;EACA,cTIK;;ADlEH;EU0DJ;IAOI,cTGG;ISFH;;;AAGF;EACE;EACA;EACA;EACA,OTzDU;;;AS6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBZ5DwB;EY6DxB,4BTRc;ESSd,2BTTc;ESUd,YACE;;AVxFA;EU6EJ;IAeI;IACA,OTFmB;ISGnB;;;;AAIJ;EACE;EACA,eTrCK;ESsCL;;AXpFA;EACE;;AClBA;EUkGJ;IX5EI;;;ACtBA;EDOF;IACE;;;ACRA;EUkGJ;IXtFI;;;;AWiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBZnGa;;;AYuGjB;EACE;EACA,aT9DK;ES+DL,gBT/DK;;ADhEH;EU4HJ;IAMI;IACA;IACA,eTpEG;ISqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AXxIF;EACE;;ACRA;EU8IF;IXlIE;;;ACZA;EDHF;IACE;;;ACEA;EU8IF;IX5IE;;;AWqJF;EACE,OTtFG;ESuFH,QTvFG;ESwFH,cT1FG;ES2FH,OZzJS;EY0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OZtK4B;EYuK5B;EACA;;AX5LA;EACE;;ACYA;EUyKJ;IXjLI;;;;AW2LJ;EACE;EACA,aTrHK;ESsHL,gBTtHK;ESuHL,cTrHK;ESsHL,aTxHK;ESyHL,OZlL4B;EYmL5B;EACA,aT/GO;ESgHP,mBZ9Ka;;ACjBb;EACE;;ACEA;EUmLJ;IXjLI;;;ACFA;EUmLJ;IAaI;IACA;IACA,cTlIG;ISmIH;IACA;;;;AAIJ;EACE,YT1IK;;;AS6IP;EACE;;;AAGF;EACE;;AX1MA;EACE;;ACRA;EUgNJ;IXpMI;;;;AWyMJ;EACE;EACA,OTrJK;ESsJL,QTtJK;ESuJL;EACA,OTnJK;ESoJL,QTpJK;ESqJL,kBZpMwB;EYqMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QTxLI;ESyLJ;;AVjQA;EU+PF;IAKI,OTzKiB;IS0KjB,YACE;;;AAKN;EACE,kBZpPsB;;AExBtB;EU2QF;IAII;;;AV/QF;EUmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;AVlSF;EUwSA;IACE;IACA;IACA;;;AAIJ;EACE,aTxOI;;ADxEJ;EU+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eV0EK;EUzEL;EACA,eVkFc;EUjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBbIuB;EaHvB;EACA;;AZNA;AAAA;EACE;;ACRA;EWOJ;AAAA;IZKI;;;AYKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBVkCD;;;AU3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBdcoB;EcbpB;EACA,eX+EY;;;AW1EhB;EACE,cdUa;;;AcyCf;AAAA;AAAA;EAGE;EACA,eXMK;EWLL,kBdlDsB;EcmDtB,eXgBc;EWfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OXLG;EWMH;EACA;EACA;EACA;EACA,SXVG;EWWH;EACA;EACA,OdhFc;EciFd;;AAEA;AAAA;AAAA;EACE,MdpFY;;AcuFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eXrEK;;AW6CL;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SXpFG;EWqFH;EACA;EACA,eX3EY;;;AWmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBdhKoB;EciKpB;;Ab9KF;AAAA;EACE;;ACEA;EYsKF;AAAA;IbpKE;;;Aa8KF;EACE;EACA,eXjHG;EWkHH,cXlHG;;AWqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SX9HK;EW+HL,eX/HK;EWgIL;EACA;EACA,eXtHc;;AWwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YdnNsB;EcsNpB,OdrNoB;;;Ac4NxB;EACE,Yd9NsB;;;AepBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AdrBE;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AfhHA;EACE;;ACYA;EeZJ;IhBII;;;;AAKF;EACE;;ACEA;EeRJ;IhBUI;;;;AAKF;EACE;;ACRA;EeJJ;IhBgBI;;;;AAKF;EACE;;AClBA;EeAJ;IhBsBI;;;;AAKF;EACE;;AC5BA;EeIJ;IhB4BI;;;;AAKF;EACE;;ACtCA;EeQJ;IhBkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EeYJ;IhB0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EegBJ;IhBiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EeoBJ;IhBwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EewBJ;IhB+DI;;;;AgB3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,adxDiB;;;Ac2DnB;EACE,ad1DyB;;;Ac6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AjBlCA;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AjB7GA;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OrBCW;EqBAX,kBrBNsB;EqBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBtBCsB;;;AsBExB;EACI;EACA;EACA,enB4EY;EmB3EZ;EACA;;AAEA;EACI,OnB8BI;EmB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBoBM;EmBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBiDY;EmBhDZ;EACA;;AACA;EACE;EACA;EACA,OnBEM;EmBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBGY;EmBFZ;EACA;;AAEA;EACI,OnB/CG;EmBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBzDK;EmB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBxBY;EmByBZ;EACA;;AACA;EACE;EACA;EACA,OnB3EK;EmB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBtEY;EmBuEZ;EACA;;AAEA;EACI,OnBhHK;EmBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB1HO;EmB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBjGY;EmBkGZ;EACA;;AACA;EACE;EACA;EACA,OnB5IO;EmB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Light color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.2 (Light Scheme)\n//\n// Brand colors:\n// Primary (Light): #2D8F52 (Green 700)\n// Surface (Light): #F5F6FA (Neutral 50)\n\n$color-scheme: light;\n\n// Body / page background\n$body-background-color: #F5F6FA; // Neutral 50 — surfaceLight\n$sidebar-color: #ECEDF3; // Neutral 100 — surfaceContainerLight\n$body-text-color: #2C2D3C; // Neutral 800 — onSurfaceLight\n$body-heading-color: #2C2D3C; // Neutral 800\n\n// Links\n$link-color: #2D8F52; // Green 700 — primaryLight\n$nav-link-color: #2D8F52; // Green 700\n\n// Navigation\n$nav-child-link-color: #555668; // Neutral 600 — secondaryLight\n$search-result-preview-color: #555668;\n\n// Code\n$code-background-color: #ECEDF3; // Neutral 100\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #D5D6E0; // Neutral 200 — outlineVariantLight\n$table-background-color: #F5F6FA; // Neutral 50\n\n// Buttons\n$btn-primary-color: #2D8F52; // Green 700\n\n// Feedback / callouts\n$feedback-color: #E0E1EB; // surfaceContainerHighLight\n\n// Search\n$search-background-color: #FFFFFF; // surfaceContainerLowestLight\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-meshtastic.css"} \ No newline at end of file diff --git a/main/assets/js/search-data.json b/main/assets/js/search-data.json index 40816fd465..ddb19ef93c 100644 --- a/main/assets/js/search-data.json +++ b/main/assets/js/search-data.json @@ -76,1223 +76,1223 @@ "relUrl": "/en/developer/adding-a-feature-module.html#10-checklist" },"11": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html", - - "relUrl": "/is-rIS/user/android-auto.html" - },"12": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html#overview", - - "relUrl": "/is-rIS/user/android-auto.html#overview" - },"13": { - "doc": "Android Auto", - "title": "Messages", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html#messages", - - "relUrl": "/is-rIS/user/android-auto.html#messages" - },"14": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html#nodes", - - "relUrl": "/is-rIS/user/android-auto.html#nodes" - },"15": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html#status", - - "relUrl": "/is-rIS/user/android-auto.html#status" - },"16": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html#related-topics", - - "relUrl": "/is-rIS/user/android-auto.html#related-topics" - },"17": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic は Android Auto と連携しており、ハンドルから手を、道路から目を離すことなく、運転中もメッシュとつながっていられます。 . ⚠️ 注意： Android Auto のサポートは、Google 版の Android ビルドでのみ利用できます。 F-Droid 版には含まれておらず、デスクトップや iOS でも利用できません。 . ℹ️ 現在提供されている機能： Google Play 版は、通知のみの車載メッセージング機能を提供します。受信メッセージがヘッドユニットで通知され、その通知コントロールから返信します。 以下で説明する、タブ形式の完全なメッセージ／ノード／ステータス体験は、Android Car App Library 上に構築されたベータ版で（Google のテンプレート型車載 UI は現在、Play の Closed／Internal トラックに制限されています）、-PenableCarTemplates=true でコンパイルしたビルドにのみ表示されます。 このページの残りの部分では、そのベータ体験について説明します。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html", - - "relUrl": "/ja-rJP/user/android-auto.html" - },"18": { - "doc": "Android Auto", - "title": "概要", - "content": "スマートフォンが Android Auto のヘッドユニット（または開発用の Desktop Head Unit エミュレーター）に接続されると、ベータ版のビルドは、Android Car App Library で構築されたメッセージングアプリとして Meshtastic を表示し、運転中でも安全にひと目で使えるよう最適化された、タブ形式のホーム画面を備えます： . | メッセージ：最近の会話。ハンズフリーの読み上げと返信ができます。 | ノード：メッシュのノードリスト。ノード詳細ビューを備えます。 | ステータス：現在の接続とメッシュの状態。 | . 車載アプリは、独自の新しい接続を追加しません。 Meshtastic アプリの既存の接続・ノード・メッセージの状態を使うため、スマートフォンがすでに接続している対象をそのまま反映します。 . ⚠️ 注意： 車載アプリがライブデータを表示するには、スマートフォンが Meshtastic 無線機に接続されている必要があります。 アプリが切断されている場合、車載画面はその切断状態を反映します。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html#%E6%A6%82%E8%A6%81", - - "relUrl": "/ja-rJP/user/android-auto.html#概要" - },"19": { - "doc": "Android Auto", - "title": "メッセージ", - "content": "メッセージタブには、最近の会話が一覧表示されます。 運転中は、次のことができます： . | メッセージを読み上げてもらうことで、画面を見る必要がなくなります。 | ヘッドユニットの返信コントロールを使って音声またはテキストで返信し、ハンズフリーで応答を音声入力できます。 | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html#%E3%83%A1%E3%83%83%E3%82%BB%E3%83%BC%E3%82%B8", - - "relUrl": "/ja-rJP/user/android-auto.html#メッセージ" - },"20": { - "doc": "Android Auto", - "title": "ノード", - "content": "ノードタブには、メッシュのノードリストが車載向けのレイアウトで表示されます。 ノードを選択すると、そのノードの主要な情報を含むノード詳細ビューが開きます。 表示される情報の詳しい意味については、ノード を参照してください。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html#%E3%83%8E%E3%83%BC%E3%83%89", - - "relUrl": "/ja-rJP/user/android-auto.html#ノード" - },"21": { - "doc": "Android Auto", - "title": "ステータス", - "content": "ステータスタブは、現在の接続とメッシュの状態をひと目で分かるようにまとめます。スマートフォンを開かずに、無線機にまだ接続されているか確認するのに便利です。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html#%E3%82%B9%E3%83%86%E3%83%BC%E3%82%BF%E3%82%B9", - - "relUrl": "/ja-rJP/user/android-auto.html#ステータス" - },"22": { - "doc": "Android Auto", - "title": "関連トピック", - "content": ". | メッセージとチャンネル：スマートフォンでの完全なメッセージング機能 | ノード：詳細なノードリストとノード詳細の情報 | コネクション：アプリが無線機に接続する方法 | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF", - - "relUrl": "/ja-rJP/user/android-auto.html#関連トピック" - },"23": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html", - - "relUrl": "/ca-rES/user/android-auto.html" - },"24": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html#overview", - - "relUrl": "/ca-rES/user/android-auto.html#overview" - },"25": { - "doc": "Android Auto", - "title": "Messages", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html#messages", - - "relUrl": "/ca-rES/user/android-auto.html#messages" - },"26": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html#nodes", - - "relUrl": "/ca-rES/user/android-auto.html#nodes" - },"27": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html#status", - - "relUrl": "/ca-rES/user/android-auto.html#status" - },"28": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html#related-topics", - - "relUrl": "/ca-rES/user/android-auto.html#related-topics" - },"29": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html", - - "relUrl": "/sr-rLatn/user/android-auto.html" - },"30": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html#overview", - - "relUrl": "/sr-rLatn/user/android-auto.html#overview" - },"31": { - "doc": "Android Auto", - "title": "Поруке", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html#%D0%BF%D0%BE%D1%80%D1%83%D0%BA%D0%B5", - - "relUrl": "/sr-rLatn/user/android-auto.html#поруке" - },"32": { - "doc": "Android Auto", - "title": "Чворови", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html#%D1%87%D0%B2%D0%BE%D1%80%D0%BE%D0%B2%D0%B8", - - "relUrl": "/sr-rLatn/user/android-auto.html#чворови" - },"33": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html#status", - - "relUrl": "/sr-rLatn/user/android-auto.html#status" - },"34": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html#related-topics", - - "relUrl": "/sr-rLatn/user/android-auto.html#related-topics" - },"35": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html", - - "relUrl": "/ko-rKR/user/android-auto.html" - },"36": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html#overview", - - "relUrl": "/ko-rKR/user/android-auto.html#overview" - },"37": { - "doc": "Android Auto", - "title": "메시지기기", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html#%EB%A9%94%EC%8B%9C%EC%A7%80%EA%B8%B0%EA%B8%B0", - - "relUrl": "/ko-rKR/user/android-auto.html#메시지기기" - },"38": { - "doc": "Android Auto", - "title": "노드", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html#%EB%85%B8%EB%93%9C", - - "relUrl": "/ko-rKR/user/android-auto.html#노드" - },"39": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html#status", - - "relUrl": "/ko-rKR/user/android-auto.html#status" - },"40": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html#related-topics", - - "relUrl": "/ko-rKR/user/android-auto.html#related-topics" - },"41": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html", - - "relUrl": "/ro-rRO/user/android-auto.html" - },"42": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html#overview", - - "relUrl": "/ro-rRO/user/android-auto.html#overview" - },"43": { - "doc": "Android Auto", - "title": "Mesaje", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html#mesaje", - - "relUrl": "/ro-rRO/user/android-auto.html#mesaje" - },"44": { - "doc": "Android Auto", - "title": "Noduri", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html#noduri", - - "relUrl": "/ro-rRO/user/android-auto.html#noduri" - },"45": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html#status", - - "relUrl": "/ro-rRO/user/android-auto.html#status" - },"46": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html#related-topics", - - "relUrl": "/ro-rRO/user/android-auto.html#related-topics" - },"47": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html", - - "relUrl": "/ga-rIE/user/android-auto.html" - },"48": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html#overview", - - "relUrl": "/ga-rIE/user/android-auto.html#overview" - },"49": { - "doc": "Android Auto", - "title": "Messages", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html#messages", - - "relUrl": "/ga-rIE/user/android-auto.html#messages" - },"50": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html#nodes", - - "relUrl": "/ga-rIE/user/android-auto.html#nodes" - },"51": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html#status", - - "relUrl": "/ga-rIE/user/android-auto.html#status" - },"52": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html#related-topics", - - "relUrl": "/ga-rIE/user/android-auto.html#related-topics" - },"53": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html", - - "relUrl": "/iw-rIL/user/android-auto.html" - },"54": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html#overview", - - "relUrl": "/iw-rIL/user/android-auto.html#overview" - },"55": { - "doc": "Android Auto", - "title": "הודעות", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html#%D7%94%D7%95%D7%93%D7%A2%D7%95%D7%AA", - - "relUrl": "/iw-rIL/user/android-auto.html#הודעות" - },"56": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html#nodes", - - "relUrl": "/iw-rIL/user/android-auto.html#nodes" - },"57": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html#status", - - "relUrl": "/iw-rIL/user/android-auto.html#status" - },"58": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html#related-topics", - - "relUrl": "/iw-rIL/user/android-auto.html#related-topics" - },"59": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html", - - "relUrl": "/sv-rSE/user/android-auto.html" - },"60": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html#overview", - - "relUrl": "/sv-rSE/user/android-auto.html#overview" - },"61": { - "doc": "Android Auto", - "title": "Meddelanden", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html#meddelanden", - - "relUrl": "/sv-rSE/user/android-auto.html#meddelanden" - },"62": { - "doc": "Android Auto", - "title": "Noder", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html#noder", - - "relUrl": "/sv-rSE/user/android-auto.html#noder" - },"63": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html#status", - - "relUrl": "/sv-rSE/user/android-auto.html#status" - },"64": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html#related-topics", - - "relUrl": "/sv-rSE/user/android-auto.html#related-topics" - },"65": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html", - - "relUrl": "/ht-rHT/user/android-auto.html" - },"66": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html#overview", - - "relUrl": "/ht-rHT/user/android-auto.html#overview" - },"67": { - "doc": "Android Auto", - "title": "Messages", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html#messages", - - "relUrl": "/ht-rHT/user/android-auto.html#messages" - },"68": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html#nodes", - - "relUrl": "/ht-rHT/user/android-auto.html#nodes" - },"69": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html#status", - - "relUrl": "/ht-rHT/user/android-auto.html#status" - },"70": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html#related-topics", - - "relUrl": "/ht-rHT/user/android-auto.html#related-topics" - },"71": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integroituu Android Auton kanssa, joten voit pysyä yhteydessä mesh-verkkoosi ajon aikana ilman, että otat käsiä pois ratista tai katsetta tiestä. ⚠️ Huom: Android Auto -tuki on saatavilla vain Google-version Android-laitteissa. Sitä ei ole mukana F-Droid-versiossa, eikä se ole saatavilla työpöydällä tai iOS:ssä. ℹ️ Mitä on saatavilla tällä hetkellä: Google Play -versio tarjoaa tällä hetkellä vain ilmoituksiin perustuvan viestituen autoon – saapuvat viestit luetaan auton näytöllä, ja voit vastata niihin sen ilmoitusohjaimilla. Alla kuvattu välilehdellinen Viestit / Radiot / Tila -kokemus on Android Car App Libraryyn perustuva beetaversio (Googlen Android Car -mallit ovat toistaiseksi rajoitettuja suljettuihin/sisäisiin Play-jakeluihin), joten se näkyy vain versioissa, jotka on käännetty asetuksella -PenableCarTemplates=true. Tämän sivun loppuosa kuvaa tätä beetakokemusta. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html", - - "relUrl": "/fi-rFI/user/android-auto.html" - },"72": { - "doc": "Android Auto", - "title": "Yleiskatsaus", - "content": "Kun puhelimesi on yhdistetty Android Auto -laitteeseen (tai kehityksessä käytettävään Desktop Head Unit -emulaattoriin), beetaversio näyttää Meshtasticin Android Car App Libraryyn perustuvana viestisovelluksena, jossa on ajon aikaiseen käyttöön optimoitu välilehdellinen aloitusnäyttö: . | Viestit — viimeisimmät keskustelut, ääneen luettava ja äänellä vastattava. | Radiot — mesh-verkon radiolista, sisältää radion yksityiskohtaisen näkymän. | Tila — nykyinen yhteys- ja mesh-verkon tila. | . Autosovellus ei luo omaa yhteyttä. Se käyttää Meshtastic-sovelluksen olemassa olevaa yhteyttä, radioa ja viestitilaa, joten se heijastaa sitä, mihin puhelimesi on jo yhdistetty. ⚠️ Huom: Puhelimen täytyy olla yhdistetty Meshtastic-radioon, jotta autosovellus näyttää reaaliaikaista dataa. Jos sovellus ei ole yhdistetty, auton näyttö näyttää katkaistun yhteyden tilan. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html#yleiskatsaus", - - "relUrl": "/fi-rFI/user/android-auto.html#yleiskatsaus" - },"73": { - "doc": "Android Auto", - "title": "Viestit", - "content": "Viestit-välilehti näyttää viimeisimmät keskustelusi. Ajon aikana voit: . | Kuunnella viestit ääneen, jotta sinun ei tarvitse katsoa näyttöä. | Vastata äänellä tai tekstillä käyttämällä pääyksikön vastaustoimintoa ja sanella vastauksesi hands-free-tilassa. | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html#viestit", - - "relUrl": "/fi-rFI/user/android-auto.html#viestit" - },"74": { - "doc": "Android Auto", - "title": "Laitteet", - "content": "Radiot-välilehti näyttää mesh-verkon radiolistan ajamiseen sopivassa näkymässä. Radion valinta avaa yksityiskohtaisen näkymän, jossa näkyy tärkeimmät tiedot kyseisestä radiosta. Katso Radiot saadaksesi täydellisen selityksen näytettävistä tiedoista. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html#laitteet", - - "relUrl": "/fi-rFI/user/android-auto.html#laitteet" - },"75": { - "doc": "Android Auto", - "title": "Tila", - "content": "Tila-välilehti näyttää nykyisen yhteyden ja mesh-verkon tilan yhdellä silmäyksellä — hyödyllinen varmistamaan, että olet yhä yhteydessä radioon ilman puhelimen avaamista. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html#tila", - - "relUrl": "/fi-rFI/user/android-auto.html#tila" - },"76": { - "doc": "Android Auto", - "title": "Aiheeseen liittyvät aiheet", - "content": ". | Viestit ja kanavat — kaikki viestitoiminnot puhelimessa | Radiot — yksityiskohtainen radiolista ja radion tietonäkymä | Yhteydet — miten sovellus yhdistyy radioon | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html#aiheeseen-liittyv%C3%A4t-aiheet", - - "relUrl": "/fi-rFI/user/android-auto.html#aiheeseen-liittyvät-aiheet" - },"77": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html", - - "relUrl": "/gl-rES/user/android-auto.html" - },"78": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html#overview", - - "relUrl": "/gl-rES/user/android-auto.html#overview" - },"79": { - "doc": "Android Auto", - "title": "Messages", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html#messages", - - "relUrl": "/gl-rES/user/android-auto.html#messages" - },"80": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html#nodes", - - "relUrl": "/gl-rES/user/android-auto.html#nodes" - },"81": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html#status", - - "relUrl": "/gl-rES/user/android-auto.html#status" - },"82": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html#related-topics", - - "relUrl": "/gl-rES/user/android-auto.html#related-topics" - },"83": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html", - - "relUrl": "/uk-rUA/user/android-auto.html" - },"84": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html#overview", - - "relUrl": "/uk-rUA/user/android-auto.html#overview" - },"85": { - "doc": "Android Auto", - "title": "Повідомлення", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html#%D0%BF%D0%BE%D0%B2%D1%96%D0%B4%D0%BE%D0%BC%D0%BB%D0%B5%D0%BD%D0%BD%D1%8F", - - "relUrl": "/uk-rUA/user/android-auto.html#повідомлення" - },"86": { - "doc": "Android Auto", - "title": "Вузли", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html#%D0%B2%D1%83%D0%B7%D0%BB%D0%B8", - - "relUrl": "/uk-rUA/user/android-auto.html#вузли" - },"87": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html#status", - - "relUrl": "/uk-rUA/user/android-auto.html#status" - },"88": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html#related-topics", - - "relUrl": "/uk-rUA/user/android-auto.html#related-topics" - },"89": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", "url": "/Meshtastic-Android/main/de-rDE/user/android-auto.html", "relUrl": "/de-rDE/user/android-auto.html" - },"90": { + },"12": { "doc": "Android Auto", "title": "Übersicht", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", "url": "/Meshtastic-Android/main/de-rDE/user/android-auto.html#%C3%BCbersicht", "relUrl": "/de-rDE/user/android-auto.html#übersicht" - },"91": { + },"13": { "doc": "Android Auto", "title": "Nachrichten", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", "url": "/Meshtastic-Android/main/de-rDE/user/android-auto.html#nachrichten", "relUrl": "/de-rDE/user/android-auto.html#nachrichten" - },"92": { + },"14": { "doc": "Android Auto", "title": "Knoten", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", "url": "/Meshtastic-Android/main/de-rDE/user/android-auto.html#knoten", "relUrl": "/de-rDE/user/android-auto.html#knoten" - },"93": { + },"15": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", "url": "/Meshtastic-Android/main/de-rDE/user/android-auto.html#status", "relUrl": "/de-rDE/user/android-auto.html#status" - },"94": { + },"16": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", "url": "/Meshtastic-Android/main/de-rDE/user/android-auto.html#related-topics", "relUrl": "/de-rDE/user/android-auto.html#related-topics" - },"95": { + },"17": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html", + "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html", - "relUrl": "/hr-rHR/user/android-auto.html" - },"96": { + "relUrl": "/ca-rES/user/android-auto.html" + },"18": { "doc": "Android Auto", "title": "Overview", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html#overview", + "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html#overview", - "relUrl": "/hr-rHR/user/android-auto.html#overview" - },"97": { + "relUrl": "/ca-rES/user/android-auto.html#overview" + },"19": { "doc": "Android Auto", "title": "Messages", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html#messages", + "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html#messages", - "relUrl": "/hr-rHR/user/android-auto.html#messages" - },"98": { + "relUrl": "/ca-rES/user/android-auto.html#messages" + },"20": { "doc": "Android Auto", "title": "Nodes", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html#nodes", + "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html#nodes", - "relUrl": "/hr-rHR/user/android-auto.html#nodes" - },"99": { + "relUrl": "/ca-rES/user/android-auto.html#nodes" + },"21": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html#status", + "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html#status", - "relUrl": "/hr-rHR/user/android-auto.html#status" - },"100": { + "relUrl": "/ca-rES/user/android-auto.html#status" + },"22": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html#related-topics", + "url": "/Meshtastic-Android/main/ca-rES/user/android-auto.html#related-topics", - "relUrl": "/hr-rHR/user/android-auto.html#related-topics" - },"101": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html", - - "relUrl": "/lt-rLT/user/android-auto.html" - },"102": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html#overview", - - "relUrl": "/lt-rLT/user/android-auto.html#overview" - },"103": { - "doc": "Android Auto", - "title": "Messages", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html#messages", - - "relUrl": "/lt-rLT/user/android-auto.html#messages" - },"104": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html#nodes", - - "relUrl": "/lt-rLT/user/android-auto.html#nodes" - },"105": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html#status", - - "relUrl": "/lt-rLT/user/android-auto.html#status" - },"106": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html#related-topics", - - "relUrl": "/lt-rLT/user/android-auto.html#related-topics" - },"107": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/en/user/android-auto.html", - - "relUrl": "/en/user/android-auto.html" - },"108": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/en/user/android-auto.html#overview", - - "relUrl": "/en/user/android-auto.html#overview" - },"109": { - "doc": "Android Auto", - "title": "Messages", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/en/user/android-auto.html#messages", - - "relUrl": "/en/user/android-auto.html#messages" - },"110": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/en/user/android-auto.html#nodes", - - "relUrl": "/en/user/android-auto.html#nodes" - },"111": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/en/user/android-auto.html#status", - - "relUrl": "/en/user/android-auto.html#status" - },"112": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/en/user/android-auto.html#related-topics", - - "relUrl": "/en/user/android-auto.html#related-topics" - },"113": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html", - - "relUrl": "/hu-rHU/user/android-auto.html" - },"114": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html#overview", - - "relUrl": "/hu-rHU/user/android-auto.html#overview" - },"115": { - "doc": "Android Auto", - "title": "Üzenetek", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html#%C3%BCzenetek", - - "relUrl": "/hu-rHU/user/android-auto.html#üzenetek" - },"116": { - "doc": "Android Auto", - "title": "Csomópontok", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html#csom%C3%B3pontok", - - "relUrl": "/hu-rHU/user/android-auto.html#csomópontok" - },"117": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html#status", - - "relUrl": "/hu-rHU/user/android-auto.html#status" - },"118": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html#related-topics", - - "relUrl": "/hu-rHU/user/android-auto.html#related-topics" - },"119": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html", - - "relUrl": "/bg-rBG/user/android-auto.html" - },"120": { - "doc": "Android Auto", - "title": "Общ преглед", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html#%D0%BE%D0%B1%D1%89-%D0%BF%D1%80%D0%B5%D0%B3%D0%BB%D0%B5%D0%B4", - - "relUrl": "/bg-rBG/user/android-auto.html#общ-преглед" - },"121": { - "doc": "Android Auto", - "title": "Съобщения", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html#%D1%81%D1%8A%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F", - - "relUrl": "/bg-rBG/user/android-auto.html#съобщения" - },"122": { - "doc": "Android Auto", - "title": "Възли", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html#%D0%B2%D1%8A%D0%B7%D0%BB%D0%B8", - - "relUrl": "/bg-rBG/user/android-auto.html#възли" - },"123": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html#status", - - "relUrl": "/bg-rBG/user/android-auto.html#status" - },"124": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html#related-topics", - - "relUrl": "/bg-rBG/user/android-auto.html#related-topics" - },"125": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html", - - "relUrl": "/sl-rSI/user/android-auto.html" - },"126": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html#overview", - - "relUrl": "/sl-rSI/user/android-auto.html#overview" - },"127": { - "doc": "Android Auto", - "title": "Messages", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html#messages", - - "relUrl": "/sl-rSI/user/android-auto.html#messages" - },"128": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html#nodes", - - "relUrl": "/sl-rSI/user/android-auto.html#nodes" - },"129": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html#status", - - "relUrl": "/sl-rSI/user/android-auto.html#status" - },"130": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html#related-topics", - - "relUrl": "/sl-rSI/user/android-auto.html#related-topics" - },"131": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html", - - "relUrl": "/pt-rPT/user/android-auto.html" - },"132": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html#overview", - - "relUrl": "/pt-rPT/user/android-auto.html#overview" - },"133": { - "doc": "Android Auto", - "title": "Mensagens", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html#mensagens", - - "relUrl": "/pt-rPT/user/android-auto.html#mensagens" - },"134": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html#nodes", - - "relUrl": "/pt-rPT/user/android-auto.html#nodes" - },"135": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html#status", - - "relUrl": "/pt-rPT/user/android-auto.html#status" - },"136": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html#related-topics", - - "relUrl": "/pt-rPT/user/android-auto.html#related-topics" - },"137": { + "relUrl": "/ca-rES/user/android-auto.html#related-topics" + },"23": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", "url": "/Meshtastic-Android/main/be-rBY/user/android-auto.html", "relUrl": "/be-rBY/user/android-auto.html" - },"138": { + },"24": { "doc": "Android Auto", "title": "Абзор", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", "url": "/Meshtastic-Android/main/be-rBY/user/android-auto.html#%D0%B0%D0%B1%D0%B7%D0%BE%D1%80", "relUrl": "/be-rBY/user/android-auto.html#абзор" - },"139": { + },"25": { "doc": "Android Auto", "title": "Паведамленні", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", "url": "/Meshtastic-Android/main/be-rBY/user/android-auto.html#%D0%BF%D0%B0%D0%B2%D0%B5%D0%B4%D0%B0%D0%BC%D0%BB%D0%B5%D0%BD%D0%BD%D1%96", "relUrl": "/be-rBY/user/android-auto.html#паведамленні" - },"140": { + },"26": { "doc": "Android Auto", "title": "Nodes", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", "url": "/Meshtastic-Android/main/be-rBY/user/android-auto.html#nodes", "relUrl": "/be-rBY/user/android-auto.html#nodes" - },"141": { + },"27": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", "url": "/Meshtastic-Android/main/be-rBY/user/android-auto.html#status", "relUrl": "/be-rBY/user/android-auto.html#status" - },"142": { + },"28": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", "url": "/Meshtastic-Android/main/be-rBY/user/android-auto.html#related-topics", "relUrl": "/be-rBY/user/android-auto.html#related-topics" - },"143": { + },"29": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html", + + "relUrl": "/uk-rUA/user/android-auto.html" + },"30": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html#overview", + + "relUrl": "/uk-rUA/user/android-auto.html#overview" + },"31": { + "doc": "Android Auto", + "title": "Повідомлення", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html#%D0%BF%D0%BE%D0%B2%D1%96%D0%B4%D0%BE%D0%BC%D0%BB%D0%B5%D0%BD%D0%BD%D1%8F", + + "relUrl": "/uk-rUA/user/android-auto.html#повідомлення" + },"32": { + "doc": "Android Auto", + "title": "Вузли", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html#%D0%B2%D1%83%D0%B7%D0%BB%D0%B8", + + "relUrl": "/uk-rUA/user/android-auto.html#вузли" + },"33": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html#status", + + "relUrl": "/uk-rUA/user/android-auto.html#status" + },"34": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/android-auto.html#related-topics", + + "relUrl": "/uk-rUA/user/android-auto.html#related-topics" + },"35": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html", + + "relUrl": "/zh-rCN/user/android-auto.html" + },"36": { + "doc": "Android Auto", + "title": "总览", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html#%E6%80%BB%E8%A7%88", + + "relUrl": "/zh-rCN/user/android-auto.html#总览" + },"37": { + "doc": "Android Auto", + "title": "消息", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html#%E6%B6%88%E6%81%AF", + + "relUrl": "/zh-rCN/user/android-auto.html#消息" + },"38": { + "doc": "Android Auto", + "title": "节点", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html#%E8%8A%82%E7%82%B9", + + "relUrl": "/zh-rCN/user/android-auto.html#节点" + },"39": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html#status", + + "relUrl": "/zh-rCN/user/android-auto.html#status" + },"40": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html#related-topics", + + "relUrl": "/zh-rCN/user/android-auto.html#related-topics" + },"41": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html", + + "relUrl": "/bg-rBG/user/android-auto.html" + },"42": { + "doc": "Android Auto", + "title": "Общ преглед", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html#%D0%BE%D0%B1%D1%89-%D0%BF%D1%80%D0%B5%D0%B3%D0%BB%D0%B5%D0%B4", + + "relUrl": "/bg-rBG/user/android-auto.html#общ-преглед" + },"43": { + "doc": "Android Auto", + "title": "Съобщения", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html#%D1%81%D1%8A%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F", + + "relUrl": "/bg-rBG/user/android-auto.html#съобщения" + },"44": { + "doc": "Android Auto", + "title": "Възли", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html#%D0%B2%D1%8A%D0%B7%D0%BB%D0%B8", + + "relUrl": "/bg-rBG/user/android-auto.html#възли" + },"45": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html#status", + + "relUrl": "/bg-rBG/user/android-auto.html#status" + },"46": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/android-auto.html#related-topics", + + "relUrl": "/bg-rBG/user/android-auto.html#related-topics" + },"47": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html", + + "relUrl": "/zh-rTW/user/android-auto.html" + },"48": { + "doc": "Android Auto", + "title": "總覽", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html#%E7%B8%BD%E8%A6%BD", + + "relUrl": "/zh-rTW/user/android-auto.html#總覽" + },"49": { + "doc": "Android Auto", + "title": "訊息", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html#%E8%A8%8A%E6%81%AF", + + "relUrl": "/zh-rTW/user/android-auto.html#訊息" + },"50": { + "doc": "Android Auto", + "title": "節點", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html#%E7%AF%80%E9%BB%9E", + + "relUrl": "/zh-rTW/user/android-auto.html#節點" + },"51": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html#status", + + "relUrl": "/zh-rTW/user/android-auto.html#status" + },"52": { + "doc": "Android Auto", + "title": "相關主題", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C", + + "relUrl": "/zh-rTW/user/android-auto.html#相關主題" + },"53": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html", + + "relUrl": "/sr-rLatn/user/android-auto.html" + },"54": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html#overview", + + "relUrl": "/sr-rLatn/user/android-auto.html#overview" + },"55": { + "doc": "Android Auto", + "title": "Поруке", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html#%D0%BF%D0%BE%D1%80%D1%83%D0%BA%D0%B5", + + "relUrl": "/sr-rLatn/user/android-auto.html#поруке" + },"56": { + "doc": "Android Auto", + "title": "Чворови", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html#%D1%87%D0%B2%D0%BE%D1%80%D0%BE%D0%B2%D0%B8", + + "relUrl": "/sr-rLatn/user/android-auto.html#чворови" + },"57": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html#status", + + "relUrl": "/sr-rLatn/user/android-auto.html#status" + },"58": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/android-auto.html#related-topics", + + "relUrl": "/sr-rLatn/user/android-auto.html#related-topics" + },"59": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html", + + "relUrl": "/cs-rCZ/user/android-auto.html" + },"60": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html#overview", + + "relUrl": "/cs-rCZ/user/android-auto.html#overview" + },"61": { + "doc": "Android Auto", + "title": "Zprávy", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html#zpr%C3%A1vy", + + "relUrl": "/cs-rCZ/user/android-auto.html#zprávy" + },"62": { + "doc": "Android Auto", + "title": "Uzly", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html#uzly", + + "relUrl": "/cs-rCZ/user/android-auto.html#uzly" + },"63": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html#status", + + "relUrl": "/cs-rCZ/user/android-auto.html#status" + },"64": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html#related-topics", + + "relUrl": "/cs-rCZ/user/android-auto.html#related-topics" + },"65": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/en/user/android-auto.html", + + "relUrl": "/en/user/android-auto.html" + },"66": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/en/user/android-auto.html#overview", + + "relUrl": "/en/user/android-auto.html#overview" + },"67": { + "doc": "Android Auto", + "title": "Messages", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/en/user/android-auto.html#messages", + + "relUrl": "/en/user/android-auto.html#messages" + },"68": { + "doc": "Android Auto", + "title": "Nodes", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/en/user/android-auto.html#nodes", + + "relUrl": "/en/user/android-auto.html#nodes" + },"69": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/en/user/android-auto.html#status", + + "relUrl": "/en/user/android-auto.html#status" + },"70": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/en/user/android-auto.html#related-topics", + + "relUrl": "/en/user/android-auto.html#related-topics" + },"71": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html", + + "relUrl": "/sl-rSI/user/android-auto.html" + },"72": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html#overview", + + "relUrl": "/sl-rSI/user/android-auto.html#overview" + },"73": { + "doc": "Android Auto", + "title": "Messages", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html#messages", + + "relUrl": "/sl-rSI/user/android-auto.html#messages" + },"74": { + "doc": "Android Auto", + "title": "Nodes", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html#nodes", + + "relUrl": "/sl-rSI/user/android-auto.html#nodes" + },"75": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html#status", + + "relUrl": "/sl-rSI/user/android-auto.html#status" + },"76": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/android-auto.html#related-topics", + + "relUrl": "/sl-rSI/user/android-auto.html#related-topics" + },"77": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html", + + "relUrl": "/it-rIT/user/android-auto.html" + },"78": { + "doc": "Android Auto", + "title": "Panoramica", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html#panoramica", + + "relUrl": "/it-rIT/user/android-auto.html#panoramica" + },"79": { + "doc": "Android Auto", + "title": "Messaggi", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html#messaggi", + + "relUrl": "/it-rIT/user/android-auto.html#messaggi" + },"80": { + "doc": "Android Auto", + "title": "Nodi", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html#nodi", + + "relUrl": "/it-rIT/user/android-auto.html#nodi" + },"81": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html#status", + + "relUrl": "/it-rIT/user/android-auto.html#status" + },"82": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html#related-topics", + + "relUrl": "/it-rIT/user/android-auto.html#related-topics" + },"83": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", "url": "/Meshtastic-Android/main/pt-rBR/user/android-auto.html", "relUrl": "/pt-rBR/user/android-auto.html" - },"144": { + },"84": { "doc": "Android Auto", "title": "Overview", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", "url": "/Meshtastic-Android/main/pt-rBR/user/android-auto.html#overview", "relUrl": "/pt-rBR/user/android-auto.html#overview" - },"145": { + },"85": { "doc": "Android Auto", "title": "Mensagens", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/android-auto.html#mensagens", "relUrl": "/pt-rBR/user/android-auto.html#mensagens" - },"146": { + },"86": { "doc": "Android Auto", "title": "Nós", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", "url": "/Meshtastic-Android/main/pt-rBR/user/android-auto.html#n%C3%B3s", "relUrl": "/pt-rBR/user/android-auto.html#nós" - },"147": { + },"87": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", "url": "/Meshtastic-Android/main/pt-rBR/user/android-auto.html#status", "relUrl": "/pt-rBR/user/android-auto.html#status" - },"148": { + },"88": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/android-auto.html#related-topics", "relUrl": "/pt-rBR/user/android-auto.html#related-topics" - },"149": { + },"89": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html", + "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html", - "relUrl": "/el-rGR/user/android-auto.html" - },"150": { + "relUrl": "/is-rIS/user/android-auto.html" + },"90": { "doc": "Android Auto", "title": "Overview", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html#overview", + "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html#overview", - "relUrl": "/el-rGR/user/android-auto.html#overview" - },"151": { - "doc": "Android Auto", - "title": "Μηνύματα", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html#%CE%BC%CE%B7%CE%BD%CF%8D%CE%BC%CE%B1%CF%84%CE%B1", - - "relUrl": "/el-rGR/user/android-auto.html#μηνύματα" - },"152": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html#nodes", - - "relUrl": "/el-rGR/user/android-auto.html#nodes" - },"153": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html#status", - - "relUrl": "/el-rGR/user/android-auto.html#status" - },"154": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html#related-topics", - - "relUrl": "/el-rGR/user/android-auto.html#related-topics" - },"155": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html", - - "relUrl": "/es-rES/user/android-auto.html" - },"156": { - "doc": "Android Auto", - "title": "Visión general", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html#visi%C3%B3n-general", - - "relUrl": "/es-rES/user/android-auto.html#visión-general" - },"157": { - "doc": "Android Auto", - "title": "Mensajes", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html#mensajes", - - "relUrl": "/es-rES/user/android-auto.html#mensajes" - },"158": { - "doc": "Android Auto", - "title": "Nodos", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html#nodos", - - "relUrl": "/es-rES/user/android-auto.html#nodos" - },"159": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html#status", - - "relUrl": "/es-rES/user/android-auto.html#status" - },"160": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html#related-topics", - - "relUrl": "/es-rES/user/android-auto.html#related-topics" - },"161": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html", - - "relUrl": "/tr-rTR/user/android-auto.html" - },"162": { - "doc": "Android Auto", - "title": "Genel Bakış", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html#genel-bak%C4%B1%C5%9F", - - "relUrl": "/tr-rTR/user/android-auto.html#genel-bakış" - },"163": { - "doc": "Android Auto", - "title": "Mesajlar", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html#mesajlar", - - "relUrl": "/tr-rTR/user/android-auto.html#mesajlar" - },"164": { - "doc": "Android Auto", - "title": "Nodelar", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html#nodelar", - - "relUrl": "/tr-rTR/user/android-auto.html#nodelar" - },"165": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html#status", - - "relUrl": "/tr-rTR/user/android-auto.html#status" - },"166": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html#related-topics", - - "relUrl": "/tr-rTR/user/android-auto.html#related-topics" - },"167": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html", - - "relUrl": "/no-rNO/user/android-auto.html" - },"168": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html#overview", - - "relUrl": "/no-rNO/user/android-auto.html#overview" - },"169": { + "relUrl": "/is-rIS/user/android-auto.html#overview" + },"91": { "doc": "Android Auto", "title": "Messages", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html#messages", + "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html#messages", - "relUrl": "/no-rNO/user/android-auto.html#messages" - },"170": { + "relUrl": "/is-rIS/user/android-auto.html#messages" + },"92": { "doc": "Android Auto", "title": "Nodes", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html#nodes", + "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html#nodes", - "relUrl": "/no-rNO/user/android-auto.html#nodes" - },"171": { + "relUrl": "/is-rIS/user/android-auto.html#nodes" + },"93": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html#status", + "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html#status", - "relUrl": "/no-rNO/user/android-auto.html#status" - },"172": { + "relUrl": "/is-rIS/user/android-auto.html#status" + },"94": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html#related-topics", + "url": "/Meshtastic-Android/main/is-rIS/user/android-auto.html#related-topics", - "relUrl": "/no-rNO/user/android-auto.html#related-topics" - },"173": { + "relUrl": "/is-rIS/user/android-auto.html#related-topics" + },"95": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html", + + "relUrl": "/fr-rFR/user/android-auto.html" + },"96": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html#overview", + + "relUrl": "/fr-rFR/user/android-auto.html#overview" + },"97": { + "doc": "Android Auto", + "title": "Messages", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html#messages", + + "relUrl": "/fr-rFR/user/android-auto.html#messages" + },"98": { + "doc": "Android Auto", + "title": "Nœuds", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html#n%C5%93uds", + + "relUrl": "/fr-rFR/user/android-auto.html#nœuds" + },"99": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html#status", + + "relUrl": "/fr-rFR/user/android-auto.html#status" + },"100": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html#related-topics", + + "relUrl": "/fr-rFR/user/android-auto.html#related-topics" + },"101": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/srp/user/android-auto.html", + + "relUrl": "/srp/user/android-auto.html" + },"102": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/srp/user/android-auto.html#overview", + + "relUrl": "/srp/user/android-auto.html#overview" + },"103": { + "doc": "Android Auto", + "title": "Поруке", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/srp/user/android-auto.html#%D0%BF%D0%BE%D1%80%D1%83%D0%BA%D0%B5", + + "relUrl": "/srp/user/android-auto.html#поруке" + },"104": { + "doc": "Android Auto", + "title": "Чворови", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/srp/user/android-auto.html#%D1%87%D0%B2%D0%BE%D1%80%D0%BE%D0%B2%D0%B8", + + "relUrl": "/srp/user/android-auto.html#чворови" + },"105": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/srp/user/android-auto.html#status", + + "relUrl": "/srp/user/android-auto.html#status" + },"106": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/srp/user/android-auto.html#related-topics", + + "relUrl": "/srp/user/android-auto.html#related-topics" + },"107": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html", + + "relUrl": "/sk-rSK/user/android-auto.html" + },"108": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html#overview", + + "relUrl": "/sk-rSK/user/android-auto.html#overview" + },"109": { + "doc": "Android Auto", + "title": "Správy", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html#spr%C3%A1vy", + + "relUrl": "/sk-rSK/user/android-auto.html#správy" + },"110": { + "doc": "Android Auto", + "title": "Nodes", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html#nodes", + + "relUrl": "/sk-rSK/user/android-auto.html#nodes" + },"111": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html#status", + + "relUrl": "/sk-rSK/user/android-auto.html#status" + },"112": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html#related-topics", + + "relUrl": "/sk-rSK/user/android-auto.html#related-topics" + },"113": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integroituu Android Auton kanssa, joten voit pysyä yhteydessä mesh-verkkoosi ajon aikana ilman, että otat käsiä pois ratista tai katsetta tiestä. ⚠️ Huom: Android Auto -tuki on saatavilla vain Google-version Android-laitteissa. Sitä ei ole mukana F-Droid-versiossa, eikä se ole saatavilla työpöydällä tai iOS:ssä. ℹ️ Mitä on saatavilla tällä hetkellä: Google Play -versio tarjoaa tällä hetkellä vain ilmoituksiin perustuvan viestituen autoon – saapuvat viestit luetaan auton näytöllä, ja voit vastata niihin sen ilmoitusohjaimilla. Alla kuvattu välilehdellinen Viestit / Radiot / Tila -kokemus on Android Car App Libraryyn perustuva beetaversio (Googlen Android Car -mallit ovat toistaiseksi rajoitettuja suljettuihin/sisäisiin Play-jakeluihin), joten se näkyy vain versioissa, jotka on käännetty asetuksella -PenableCarTemplates=true. Tämän sivun loppuosa kuvaa tätä beetakokemusta. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html", + + "relUrl": "/fi-rFI/user/android-auto.html" + },"114": { + "doc": "Android Auto", + "title": "Yleiskatsaus", + "content": "Kun puhelimesi on yhdistetty Android Auto -laitteeseen (tai kehityksessä käytettävään Desktop Head Unit -emulaattoriin), beetaversio näyttää Meshtasticin Android Car App Libraryyn perustuvana viestisovelluksena, jossa on ajon aikaiseen käyttöön optimoitu välilehdellinen aloitusnäyttö: . | Viestit — viimeisimmät keskustelut, ääneen luettava ja äänellä vastattava. | Radiot — mesh-verkon radiolista, sisältää radion yksityiskohtaisen näkymän. | Tila — nykyinen yhteys- ja mesh-verkon tila. | . Autosovellus ei luo omaa yhteyttä. Se käyttää Meshtastic-sovelluksen olemassa olevaa yhteyttä, radioa ja viestitilaa, joten se heijastaa sitä, mihin puhelimesi on jo yhdistetty. ⚠️ Huom: Puhelimen täytyy olla yhdistetty Meshtastic-radioon, jotta autosovellus näyttää reaaliaikaista dataa. Jos sovellus ei ole yhdistetty, auton näyttö näyttää katkaistun yhteyden tilan. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html#yleiskatsaus", + + "relUrl": "/fi-rFI/user/android-auto.html#yleiskatsaus" + },"115": { + "doc": "Android Auto", + "title": "Viestit", + "content": "Viestit-välilehti näyttää viimeisimmät keskustelusi. Ajon aikana voit: . | Kuunnella viestit ääneen, jotta sinun ei tarvitse katsoa näyttöä. | Vastata äänellä tai tekstillä käyttämällä pääyksikön vastaustoimintoa ja sanella vastauksesi hands-free-tilassa. | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html#viestit", + + "relUrl": "/fi-rFI/user/android-auto.html#viestit" + },"116": { + "doc": "Android Auto", + "title": "Laitteet", + "content": "Radiot-välilehti näyttää mesh-verkon radiolistan ajamiseen sopivassa näkymässä. Radion valinta avaa yksityiskohtaisen näkymän, jossa näkyy tärkeimmät tiedot kyseisestä radiosta. Katso Radiot saadaksesi täydellisen selityksen näytettävistä tiedoista. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html#laitteet", + + "relUrl": "/fi-rFI/user/android-auto.html#laitteet" + },"117": { + "doc": "Android Auto", + "title": "Tila", + "content": "Tila-välilehti näyttää nykyisen yhteyden ja mesh-verkon tilan yhdellä silmäyksellä — hyödyllinen varmistamaan, että olet yhä yhteydessä radioon ilman puhelimen avaamista. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html#tila", + + "relUrl": "/fi-rFI/user/android-auto.html#tila" + },"118": { + "doc": "Android Auto", + "title": "Aiheeseen liittyvät aiheet", + "content": ". | Viestit ja kanavat — kaikki viestitoiminnot puhelimessa | Radiot — yksityiskohtainen radiolista ja radion tietonäkymä | Yhteydet — miten sovellus yhdistyy radioon | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/android-auto.html#aiheeseen-liittyv%C3%A4t-aiheet", + + "relUrl": "/fi-rFI/user/android-auto.html#aiheeseen-liittyvät-aiheet" + },"119": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic интегрируется с Android Auto, так что ты можешь оставаться на связи со своей сетью, пока едешь, не отрывая рук от руля и глаз от дороги. ⚠️ Примечание: поддержка Android Auto доступна только на Android-сборках от Google. Она не включена в сборку F-Droid и недоступна на ПК или iOS. ℹ️ Что сегодня нового: Сборка для Google Play предоставляет только уведомления для сообщений в машине — входящие сообщения объявляются на головном устройстве, а ответ даётся через его элементы управления уведомлениями. Полная вкладка Сообщения / Ноды / Статус, описанная ниже, является бета-версией, построенной на библиотеке Android Car App (шаблонный интерфейс Google для автомобилей в настоящее время ограничен закрытыми/внутренними треками Play), поэтому он появляется только в сборках, скомпилированных с -PenableCarTemplates=true. Остальная часть этой страницы документирует бета-тестирование. ", "url": "/Meshtastic-Android/main/ru-rRU/user/android-auto.html", "relUrl": "/ru-rRU/user/android-auto.html" - },"174": { + },"120": { "doc": "Android Auto", "title": "Обзор", "content": "Когда твой телефон подключен к головному устройству Android Auto (или к эмулятору Desktop Head Unit, используемому для разработки), бета-версия показывает Meshtastic как приложение для обмена сообщениями, созданное с помощью библиотеки Android Car App, с вкладочной главной страницей, оптимизированной для безопасного вождения и удобного быстрого просмотра: . | Сообщения — недавние разговоры с возможностью чтения и ответов без рук. | Узлы — список нод сети с подробным просмотром каждой ноды. | Статус — текущий статус подключения и сети. | . Приложение для машины само по себе не добавляет новое соединение. Оно использует уже существующее соединение, ноду и состояние сообщений в приложении Meshtastic, так что отображает то, к чему твой телефон уже подключен. ⚠️ Примечание: твой телефон должен быть подключен к радиостанции Meshtastic, чтобы автомобильное приложение показывало данные в реальном времени. Если приложение отключено, экран автомобиля показывает отключенное состояние. ", "url": "/Meshtastic-Android/main/ru-rRU/user/android-auto.html#%D0%BE%D0%B1%D0%B7%D0%BE%D1%80", "relUrl": "/ru-rRU/user/android-auto.html#обзор" - },"175": { + },"121": { "doc": "Android Auto", "title": "Сообщения", "content": "Вкладка «Сообщения» показывает твои недавние разговоры. За рулём ты можешь: . | Прослушивать сообщения вслух, чтобы не приходилось смотреть на экран. | Отвечай голосом или текстом с помощью кнопки ответа на своей головной панели, диктуя свой ответ без рук. | . ", "url": "/Meshtastic-Android/main/ru-rRU/user/android-auto.html#%D1%81%D0%BE%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F", "relUrl": "/ru-rRU/user/android-auto.html#сообщения" - },"176": { + },"122": { "doc": "Android Auto", "title": "Ноды", "content": "Вкладка «Ноды» показывает список нод вашей сетки в удобном для машины формате. Выбор ноды открывает представление с подробной информацией об этой ноде. Смотри Ноды, чтобы полностью понять информацию, показанную здесь. ", "url": "/Meshtastic-Android/main/ru-rRU/user/android-auto.html#%D0%BD%D0%BE%D0%B4%D1%8B", "relUrl": "/ru-rRU/user/android-auto.html#ноды" - },"177": { + },"123": { "doc": "Android Auto", "title": "Статус", "content": "Вкладка «Статус» позволяет одним взглядом увидеть твоё текущее соединение и состояние сети — удобно, чтобы проверить, что ты всё ещё подключен к радиостанции, не открывая телефон. ", "url": "/Meshtastic-Android/main/ru-rRU/user/android-auto.html#%D1%81%D1%82%D0%B0%D1%82%D1%83%D1%81", "relUrl": "/ru-rRU/user/android-auto.html#статус" - },"178": { + },"124": { "doc": "Android Auto", "title": "Связанные темы", "content": ". | Сообщения и Каналы — все функции обмена сообщениями на твоём телефоне | Ноды — подробный список нод и информация о каждой ноде | Подключения — как приложение подключается к твоей радиостанции | . ", "url": "/Meshtastic-Android/main/ru-rRU/user/android-auto.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/android-auto.html#связанные-темы" + },"125": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html", + + "relUrl": "/ko-rKR/user/android-auto.html" + },"126": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html#overview", + + "relUrl": "/ko-rKR/user/android-auto.html#overview" + },"127": { + "doc": "Android Auto", + "title": "메시지기기", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html#%EB%A9%94%EC%8B%9C%EC%A7%80%EA%B8%B0%EA%B8%B0", + + "relUrl": "/ko-rKR/user/android-auto.html#메시지기기" + },"128": { + "doc": "Android Auto", + "title": "노드", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html#%EB%85%B8%EB%93%9C", + + "relUrl": "/ko-rKR/user/android-auto.html#노드" + },"129": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html#status", + + "relUrl": "/ko-rKR/user/android-auto.html#status" + },"130": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/android-auto.html#related-topics", + + "relUrl": "/ko-rKR/user/android-auto.html#related-topics" + },"131": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html", + + "relUrl": "/hr-rHR/user/android-auto.html" + },"132": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html#overview", + + "relUrl": "/hr-rHR/user/android-auto.html#overview" + },"133": { + "doc": "Android Auto", + "title": "Messages", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html#messages", + + "relUrl": "/hr-rHR/user/android-auto.html#messages" + },"134": { + "doc": "Android Auto", + "title": "Nodes", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html#nodes", + + "relUrl": "/hr-rHR/user/android-auto.html#nodes" + },"135": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html#status", + + "relUrl": "/hr-rHR/user/android-auto.html#status" + },"136": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/android-auto.html#related-topics", + + "relUrl": "/hr-rHR/user/android-auto.html#related-topics" + },"137": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html", + + "relUrl": "/sq-rAL/user/android-auto.html" + },"138": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html#overview", + + "relUrl": "/sq-rAL/user/android-auto.html#overview" + },"139": { + "doc": "Android Auto", + "title": "訊息", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html#%E8%A8%8A%E6%81%AF", + + "relUrl": "/sq-rAL/user/android-auto.html#訊息" + },"140": { + "doc": "Android Auto", + "title": "Nodes", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html#nodes", + + "relUrl": "/sq-rAL/user/android-auto.html#nodes" + },"141": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html#status", + + "relUrl": "/sq-rAL/user/android-auto.html#status" + },"142": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html#related-topics", + + "relUrl": "/sq-rAL/user/android-auto.html#related-topics" + },"143": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html", + + "relUrl": "/no-rNO/user/android-auto.html" + },"144": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html#overview", + + "relUrl": "/no-rNO/user/android-auto.html#overview" + },"145": { + "doc": "Android Auto", + "title": "Messages", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html#messages", + + "relUrl": "/no-rNO/user/android-auto.html#messages" + },"146": { + "doc": "Android Auto", + "title": "Nodes", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html#nodes", + + "relUrl": "/no-rNO/user/android-auto.html#nodes" + },"147": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html#status", + + "relUrl": "/no-rNO/user/android-auto.html#status" + },"148": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/android-auto.html#related-topics", + + "relUrl": "/no-rNO/user/android-auto.html#related-topics" + },"149": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html", + + "relUrl": "/lt-rLT/user/android-auto.html" + },"150": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html#overview", + + "relUrl": "/lt-rLT/user/android-auto.html#overview" + },"151": { + "doc": "Android Auto", + "title": "Messages", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html#messages", + + "relUrl": "/lt-rLT/user/android-auto.html#messages" + },"152": { + "doc": "Android Auto", + "title": "Nodes", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html#nodes", + + "relUrl": "/lt-rLT/user/android-auto.html#nodes" + },"153": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html#status", + + "relUrl": "/lt-rLT/user/android-auto.html#status" + },"154": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/android-auto.html#related-topics", + + "relUrl": "/lt-rLT/user/android-auto.html#related-topics" + },"155": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html", + + "relUrl": "/ar-rSA/user/android-auto.html" + },"156": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html#overview", + + "relUrl": "/ar-rSA/user/android-auto.html#overview" + },"157": { + "doc": "Android Auto", + "title": "الرسائل", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html#%D8%A7%D9%84%D8%B1%D8%B3%D8%A7%D8%A6%D9%84", + + "relUrl": "/ar-rSA/user/android-auto.html#الرسائل" + },"158": { + "doc": "Android Auto", + "title": "Nodes", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html#nodes", + + "relUrl": "/ar-rSA/user/android-auto.html#nodes" + },"159": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html#status", + + "relUrl": "/ar-rSA/user/android-auto.html#status" + },"160": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html#related-topics", + + "relUrl": "/ar-rSA/user/android-auto.html#related-topics" + },"161": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html", + + "relUrl": "/pt-rPT/user/android-auto.html" + },"162": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html#overview", + + "relUrl": "/pt-rPT/user/android-auto.html#overview" + },"163": { + "doc": "Android Auto", + "title": "Mensagens", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html#mensagens", + + "relUrl": "/pt-rPT/user/android-auto.html#mensagens" + },"164": { + "doc": "Android Auto", + "title": "Nodes", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html#nodes", + + "relUrl": "/pt-rPT/user/android-auto.html#nodes" + },"165": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html#status", + + "relUrl": "/pt-rPT/user/android-auto.html#status" + },"166": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/android-auto.html#related-topics", + + "relUrl": "/pt-rPT/user/android-auto.html#related-topics" + },"167": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html", + + "relUrl": "/iw-rIL/user/android-auto.html" + },"168": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html#overview", + + "relUrl": "/iw-rIL/user/android-auto.html#overview" + },"169": { + "doc": "Android Auto", + "title": "הודעות", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html#%D7%94%D7%95%D7%93%D7%A2%D7%95%D7%AA", + + "relUrl": "/iw-rIL/user/android-auto.html#הודעות" + },"170": { + "doc": "Android Auto", + "title": "Nodes", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html#nodes", + + "relUrl": "/iw-rIL/user/android-auto.html#nodes" + },"171": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html#status", + + "relUrl": "/iw-rIL/user/android-auto.html#status" + },"172": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/android-auto.html#related-topics", + + "relUrl": "/iw-rIL/user/android-auto.html#related-topics" + },"173": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html", + + "relUrl": "/el-rGR/user/android-auto.html" + },"174": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html#overview", + + "relUrl": "/el-rGR/user/android-auto.html#overview" + },"175": { + "doc": "Android Auto", + "title": "Μηνύματα", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html#%CE%BC%CE%B7%CE%BD%CF%8D%CE%BC%CE%B1%CF%84%CE%B1", + + "relUrl": "/el-rGR/user/android-auto.html#μηνύματα" + },"176": { + "doc": "Android Auto", + "title": "Nodes", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html#nodes", + + "relUrl": "/el-rGR/user/android-auto.html#nodes" + },"177": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html#status", + + "relUrl": "/el-rGR/user/android-auto.html#status" + },"178": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/android-auto.html#related-topics", + + "relUrl": "/el-rGR/user/android-auto.html#related-topics" },"179": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html", + "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html", - "relUrl": "/nl-rNL/user/android-auto.html" + "relUrl": "/ro-rRO/user/android-auto.html" },"180": { "doc": "Android Auto", "title": "Overview", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html#overview", + "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html#overview", - "relUrl": "/nl-rNL/user/android-auto.html#overview" + "relUrl": "/ro-rRO/user/android-auto.html#overview" },"181": { "doc": "Android Auto", - "title": "Berichten", + "title": "Mesaje", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html#berichten", + "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html#mesaje", - "relUrl": "/nl-rNL/user/android-auto.html#berichten" + "relUrl": "/ro-rRO/user/android-auto.html#mesaje" },"182": { "doc": "Android Auto", - "title": "Nodes", + "title": "Noduri", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html#nodes", + "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html#noduri", - "relUrl": "/nl-rNL/user/android-auto.html#nodes" + "relUrl": "/ro-rRO/user/android-auto.html#noduri" },"183": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html#status", + "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html#status", - "relUrl": "/nl-rNL/user/android-auto.html#status" + "relUrl": "/ro-rRO/user/android-auto.html#status" },"184": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html#related-topics", + "url": "/Meshtastic-Android/main/ro-rRO/user/android-auto.html#related-topics", - "relUrl": "/nl-rNL/user/android-auto.html#related-topics" + "relUrl": "/ro-rRO/user/android-auto.html#related-topics" },"185": { "doc": "Android auto", "title": "Android auto", @@ -1339,1234 +1339,1234 @@ "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html", + "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html", - "relUrl": "/it-rIT/user/android-auto.html" + "relUrl": "/ga-rIE/user/android-auto.html" },"192": { "doc": "Android Auto", - "title": "Panoramica", + "title": "Overview", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html#panoramica", + "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html#overview", - "relUrl": "/it-rIT/user/android-auto.html#panoramica" + "relUrl": "/ga-rIE/user/android-auto.html#overview" },"193": { "doc": "Android Auto", - "title": "Messaggi", + "title": "Messages", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html#messaggi", + "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html#messages", - "relUrl": "/it-rIT/user/android-auto.html#messaggi" + "relUrl": "/ga-rIE/user/android-auto.html#messages" },"194": { "doc": "Android Auto", - "title": "Nodi", + "title": "Nodes", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html#nodi", + "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html#nodes", - "relUrl": "/it-rIT/user/android-auto.html#nodi" + "relUrl": "/ga-rIE/user/android-auto.html#nodes" },"195": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html#status", + "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html#status", - "relUrl": "/it-rIT/user/android-auto.html#status" + "relUrl": "/ga-rIE/user/android-auto.html#status" },"196": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/android-auto.html#related-topics", + "url": "/Meshtastic-Android/main/ga-rIE/user/android-auto.html#related-topics", - "relUrl": "/it-rIT/user/android-auto.html#related-topics" + "relUrl": "/ga-rIE/user/android-auto.html#related-topics" },"197": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html", - - "relUrl": "/ar-rSA/user/android-auto.html" - },"198": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html#overview", - - "relUrl": "/ar-rSA/user/android-auto.html#overview" - },"199": { - "doc": "Android Auto", - "title": "الرسائل", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html#%D8%A7%D9%84%D8%B1%D8%B3%D8%A7%D8%A6%D9%84", - - "relUrl": "/ar-rSA/user/android-auto.html#الرسائل" - },"200": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html#nodes", - - "relUrl": "/ar-rSA/user/android-auto.html#nodes" - },"201": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html#status", - - "relUrl": "/ar-rSA/user/android-auto.html#status" - },"202": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/android-auto.html#related-topics", - - "relUrl": "/ar-rSA/user/android-auto.html#related-topics" - },"203": { - "doc": "Android Auto", - "title": "Android Auto", - "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html", - - "relUrl": "/sk-rSK/user/android-auto.html" - },"204": { - "doc": "Android Auto", - "title": "Overview", - "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html#overview", - - "relUrl": "/sk-rSK/user/android-auto.html#overview" - },"205": { - "doc": "Android Auto", - "title": "Správy", - "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html#spr%C3%A1vy", - - "relUrl": "/sk-rSK/user/android-auto.html#správy" - },"206": { - "doc": "Android Auto", - "title": "Nodes", - "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html#nodes", - - "relUrl": "/sk-rSK/user/android-auto.html#nodes" - },"207": { - "doc": "Android Auto", - "title": "Status", - "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html#status", - - "relUrl": "/sk-rSK/user/android-auto.html#status" - },"208": { - "doc": "Android Auto", - "title": "Related Topics", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/android-auto.html#related-topics", - - "relUrl": "/sk-rSK/user/android-auto.html#related-topics" - },"209": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", "url": "/Meshtastic-Android/main/pl-rPL/user/android-auto.html", "relUrl": "/pl-rPL/user/android-auto.html" - },"210": { + },"198": { "doc": "Android Auto", "title": "Overview", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", "url": "/Meshtastic-Android/main/pl-rPL/user/android-auto.html#overview", "relUrl": "/pl-rPL/user/android-auto.html#overview" - },"211": { + },"199": { "doc": "Android Auto", "title": "Wiadomości", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/android-auto.html#wiadomo%C5%9Bci", "relUrl": "/pl-rPL/user/android-auto.html#wiadomości" - },"212": { + },"200": { "doc": "Android Auto", "title": "Węzły", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", "url": "/Meshtastic-Android/main/pl-rPL/user/android-auto.html#w%C4%99z%C5%82y", "relUrl": "/pl-rPL/user/android-auto.html#węzły" - },"213": { + },"201": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", "url": "/Meshtastic-Android/main/pl-rPL/user/android-auto.html#status", "relUrl": "/pl-rPL/user/android-auto.html#status" - },"214": { + },"202": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/android-auto.html#related-topics", "relUrl": "/pl-rPL/user/android-auto.html#related-topics" - },"215": { + },"203": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html", + "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html", - "relUrl": "/zh-rTW/user/android-auto.html" - },"216": { + "relUrl": "/nl-rNL/user/android-auto.html" + },"204": { "doc": "Android Auto", - "title": "總覽", + "title": "Overview", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html#%E7%B8%BD%E8%A6%BD", + "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html#overview", - "relUrl": "/zh-rTW/user/android-auto.html#總覽" - },"217": { + "relUrl": "/nl-rNL/user/android-auto.html#overview" + },"205": { "doc": "Android Auto", - "title": "訊息", + "title": "Berichten", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html#%E8%A8%8A%E6%81%AF", + "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html#berichten", - "relUrl": "/zh-rTW/user/android-auto.html#訊息" - },"218": { + "relUrl": "/nl-rNL/user/android-auto.html#berichten" + },"206": { "doc": "Android Auto", - "title": "節點", + "title": "Nodes", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html#%E7%AF%80%E9%BB%9E", + "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html#nodes", - "relUrl": "/zh-rTW/user/android-auto.html#節點" - },"219": { + "relUrl": "/nl-rNL/user/android-auto.html#nodes" + },"207": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html#status", + "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html#status", - "relUrl": "/zh-rTW/user/android-auto.html#status" + "relUrl": "/nl-rNL/user/android-auto.html#status" + },"208": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/android-auto.html#related-topics", + + "relUrl": "/nl-rNL/user/android-auto.html#related-topics" + },"209": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html", + + "relUrl": "/sv-rSE/user/android-auto.html" + },"210": { + "doc": "Android Auto", + "title": "Overview", + "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html#overview", + + "relUrl": "/sv-rSE/user/android-auto.html#overview" + },"211": { + "doc": "Android Auto", + "title": "Meddelanden", + "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html#meddelanden", + + "relUrl": "/sv-rSE/user/android-auto.html#meddelanden" + },"212": { + "doc": "Android Auto", + "title": "Noder", + "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html#noder", + + "relUrl": "/sv-rSE/user/android-auto.html#noder" + },"213": { + "doc": "Android Auto", + "title": "Status", + "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html#status", + + "relUrl": "/sv-rSE/user/android-auto.html#status" + },"214": { + "doc": "Android Auto", + "title": "Related Topics", + "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/android-auto.html#related-topics", + + "relUrl": "/sv-rSE/user/android-auto.html#related-topics" + },"215": { + "doc": "Android Auto", + "title": "Android Auto", + "content": "Meshtastic は Android Auto と連携しており、ハンドルから手を、道路から目を離すことなく、運転中もメッシュとつながっていられます。 . ⚠️ 注意： Android Auto のサポートは、Google 版の Android ビルドでのみ利用できます。 F-Droid 版には含まれておらず、デスクトップや iOS でも利用できません。 . ℹ️ 現在提供されている機能： Google Play 版は、通知のみの車載メッセージング機能を提供します。受信メッセージがヘッドユニットで通知され、その通知コントロールから返信します。 以下で説明する、タブ形式の完全なメッセージ／ノード／ステータス体験は、Android Car App Library 上に構築されたベータ版で（Google のテンプレート型車載 UI は現在、Play の Closed／Internal トラックに制限されています）、-PenableCarTemplates=true でコンパイルしたビルドにのみ表示されます。 このページの残りの部分では、そのベータ体験について説明します。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html", + + "relUrl": "/ja-rJP/user/android-auto.html" + },"216": { + "doc": "Android Auto", + "title": "概要", + "content": "スマートフォンが Android Auto のヘッドユニット（または開発用の Desktop Head Unit エミュレーター）に接続されると、ベータ版のビルドは、Android Car App Library で構築されたメッセージングアプリとして Meshtastic を表示し、運転中でも安全にひと目で使えるよう最適化された、タブ形式のホーム画面を備えます： . | メッセージ：最近の会話。ハンズフリーの読み上げと返信ができます。 | ノード：メッシュのノードリスト。ノード詳細ビューを備えます。 | ステータス：現在の接続とメッシュの状態。 | . 車載アプリは、独自の新しい接続を追加しません。 Meshtastic アプリの既存の接続・ノード・メッセージの状態を使うため、スマートフォンがすでに接続している対象をそのまま反映します。 . ⚠️ 注意： 車載アプリがライブデータを表示するには、スマートフォンが Meshtastic 無線機に接続されている必要があります。 アプリが切断されている場合、車載画面はその切断状態を反映します。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html#%E6%A6%82%E8%A6%81", + + "relUrl": "/ja-rJP/user/android-auto.html#概要" + },"217": { + "doc": "Android Auto", + "title": "メッセージ", + "content": "メッセージタブには、最近の会話が一覧表示されます。 運転中は、次のことができます： . | メッセージを読み上げてもらうことで、画面を見る必要がなくなります。 | ヘッドユニットの返信コントロールを使って音声またはテキストで返信し、ハンズフリーで応答を音声入力できます。 | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html#%E3%83%A1%E3%83%83%E3%82%BB%E3%83%BC%E3%82%B8", + + "relUrl": "/ja-rJP/user/android-auto.html#メッセージ" + },"218": { + "doc": "Android Auto", + "title": "ノード", + "content": "ノードタブには、メッシュのノードリストが車載向けのレイアウトで表示されます。 ノードを選択すると、そのノードの主要な情報を含むノード詳細ビューが開きます。 表示される情報の詳しい意味については、ノード を参照してください。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html#%E3%83%8E%E3%83%BC%E3%83%89", + + "relUrl": "/ja-rJP/user/android-auto.html#ノード" + },"219": { + "doc": "Android Auto", + "title": "ステータス", + "content": "ステータスタブは、現在の接続とメッシュの状態をひと目で分かるようにまとめます。スマートフォンを開かずに、無線機にまだ接続されているか確認するのに便利です。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html#%E3%82%B9%E3%83%86%E3%83%BC%E3%82%BF%E3%82%B9", + + "relUrl": "/ja-rJP/user/android-auto.html#ステータス" },"220": { "doc": "Android Auto", - "title": "相關主題", - "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/android-auto.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C", + "title": "関連トピック", + "content": ". | メッセージとチャンネル：スマートフォンでの完全なメッセージング機能 | ノード：詳細なノードリストとノード詳細の情報 | コネクション：アプリが無線機に接続する方法 | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/android-auto.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF", - "relUrl": "/zh-rTW/user/android-auto.html#相關主題" + "relUrl": "/ja-rJP/user/android-auto.html#関連トピック" },"221": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html", + "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html", - "relUrl": "/cs-rCZ/user/android-auto.html" + "relUrl": "/hu-rHU/user/android-auto.html" },"222": { "doc": "Android Auto", "title": "Overview", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html#overview", + "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html#overview", - "relUrl": "/cs-rCZ/user/android-auto.html#overview" + "relUrl": "/hu-rHU/user/android-auto.html#overview" },"223": { "doc": "Android Auto", - "title": "Zprávy", + "title": "Üzenetek", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html#zpr%C3%A1vy", + "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html#%C3%BCzenetek", - "relUrl": "/cs-rCZ/user/android-auto.html#zprávy" + "relUrl": "/hu-rHU/user/android-auto.html#üzenetek" },"224": { "doc": "Android Auto", - "title": "Uzly", + "title": "Csomópontok", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html#uzly", + "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html#csom%C3%B3pontok", - "relUrl": "/cs-rCZ/user/android-auto.html#uzly" + "relUrl": "/hu-rHU/user/android-auto.html#csomópontok" },"225": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html#status", + "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html#status", - "relUrl": "/cs-rCZ/user/android-auto.html#status" + "relUrl": "/hu-rHU/user/android-auto.html#status" },"226": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/android-auto.html#related-topics", + "url": "/Meshtastic-Android/main/hu-rHU/user/android-auto.html#related-topics", - "relUrl": "/cs-rCZ/user/android-auto.html#related-topics" + "relUrl": "/hu-rHU/user/android-auto.html#related-topics" },"227": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html", + "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html", - "relUrl": "/fr-rFR/user/android-auto.html" + "relUrl": "/ht-rHT/user/android-auto.html" },"228": { "doc": "Android Auto", "title": "Overview", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html#overview", + "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html#overview", - "relUrl": "/fr-rFR/user/android-auto.html#overview" + "relUrl": "/ht-rHT/user/android-auto.html#overview" },"229": { "doc": "Android Auto", "title": "Messages", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html#messages", + "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html#messages", - "relUrl": "/fr-rFR/user/android-auto.html#messages" + "relUrl": "/ht-rHT/user/android-auto.html#messages" },"230": { "doc": "Android Auto", - "title": "Nœuds", + "title": "Nodes", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html#n%C5%93uds", + "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html#nodes", - "relUrl": "/fr-rFR/user/android-auto.html#nœuds" + "relUrl": "/ht-rHT/user/android-auto.html#nodes" },"231": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html#status", + "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html#status", - "relUrl": "/fr-rFR/user/android-auto.html#status" + "relUrl": "/ht-rHT/user/android-auto.html#status" },"232": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/android-auto.html#related-topics", + "url": "/Meshtastic-Android/main/ht-rHT/user/android-auto.html#related-topics", - "relUrl": "/fr-rFR/user/android-auto.html#related-topics" + "relUrl": "/ht-rHT/user/android-auto.html#related-topics" },"233": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html", + "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html", - "relUrl": "/zh-rCN/user/android-auto.html" + "relUrl": "/gl-rES/user/android-auto.html" },"234": { "doc": "Android Auto", - "title": "总览", + "title": "Overview", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html#%E6%80%BB%E8%A7%88", + "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html#overview", - "relUrl": "/zh-rCN/user/android-auto.html#总览" + "relUrl": "/gl-rES/user/android-auto.html#overview" },"235": { "doc": "Android Auto", - "title": "消息", + "title": "Messages", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html#%E6%B6%88%E6%81%AF", + "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html#messages", - "relUrl": "/zh-rCN/user/android-auto.html#消息" + "relUrl": "/gl-rES/user/android-auto.html#messages" },"236": { "doc": "Android Auto", - "title": "节点", + "title": "Nodes", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html#%E8%8A%82%E7%82%B9", + "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html#nodes", - "relUrl": "/zh-rCN/user/android-auto.html#节点" + "relUrl": "/gl-rES/user/android-auto.html#nodes" },"237": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html#status", + "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html#status", - "relUrl": "/zh-rCN/user/android-auto.html#status" + "relUrl": "/gl-rES/user/android-auto.html#status" },"238": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/android-auto.html#related-topics", + "url": "/Meshtastic-Android/main/gl-rES/user/android-auto.html#related-topics", - "relUrl": "/zh-rCN/user/android-auto.html#related-topics" + "relUrl": "/gl-rES/user/android-auto.html#related-topics" },"239": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/srp/user/android-auto.html", + "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html", - "relUrl": "/srp/user/android-auto.html" + "relUrl": "/tr-rTR/user/android-auto.html" },"240": { "doc": "Android Auto", - "title": "Overview", + "title": "Genel Bakış", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/srp/user/android-auto.html#overview", + "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html#genel-bak%C4%B1%C5%9F", - "relUrl": "/srp/user/android-auto.html#overview" + "relUrl": "/tr-rTR/user/android-auto.html#genel-bakış" },"241": { "doc": "Android Auto", - "title": "Поруке", + "title": "Mesajlar", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/srp/user/android-auto.html#%D0%BF%D0%BE%D1%80%D1%83%D0%BA%D0%B5", + "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html#mesajlar", - "relUrl": "/srp/user/android-auto.html#поруке" + "relUrl": "/tr-rTR/user/android-auto.html#mesajlar" },"242": { "doc": "Android Auto", - "title": "Чворови", + "title": "Nodelar", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/srp/user/android-auto.html#%D1%87%D0%B2%D0%BE%D1%80%D0%BE%D0%B2%D0%B8", + "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html#nodelar", - "relUrl": "/srp/user/android-auto.html#чворови" + "relUrl": "/tr-rTR/user/android-auto.html#nodelar" },"243": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/srp/user/android-auto.html#status", + "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html#status", - "relUrl": "/srp/user/android-auto.html#status" + "relUrl": "/tr-rTR/user/android-auto.html#status" },"244": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/srp/user/android-auto.html#related-topics", + "url": "/Meshtastic-Android/main/tr-rTR/user/android-auto.html#related-topics", - "relUrl": "/srp/user/android-auto.html#related-topics" + "relUrl": "/tr-rTR/user/android-auto.html#related-topics" },"245": { "doc": "Android Auto", "title": "Android Auto", "content": "Meshtastic integrates with Android Auto so you can stay in touch with your mesh while driving, without taking your hands off the wheel or your eyes off the road. ⚠️ Note: Android Auto support is available on Google-flavor Android builds only. It is not included in the F-Droid build, and it is not available on Desktop or iOS. ℹ️ What ships today: The Google Play build provides notification-only car messaging — incoming messages are announced on the head unit and you reply through its notification controls. The full tabbed Messages / Nodes / Status experience described below is a beta built on the Android Car App Library (Google’s templated car UI is currently restricted to Closed/Internal Play tracks), so it appears only in builds compiled with -PenableCarTemplates=true. The rest of this page documents that beta experience. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html", + "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html", - "relUrl": "/sq-rAL/user/android-auto.html" + "relUrl": "/es-rES/user/android-auto.html" },"246": { "doc": "Android Auto", - "title": "Overview", + "title": "Visión general", "content": "When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), the beta build presents Meshtastic as a messaging app built with the Android Car App Library, with a tabbed Home screen optimized for driving-safe, glanceable use: . | Messages — recent conversations, with hands-free reading and replies. | Nodes — the mesh node list, with a node-detail view. | Status — current connection and mesh status. | . The car app does not add a new connection of its own. It uses the Meshtastic app’s existing connection, node, and message state, so it reflects whatever your phone is already connected to. ⚠️ Note: Your phone must be connected to a Meshtastic radio for the car app to show live data. If the app is disconnected, the car screen reflects that disconnected state. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html#overview", + "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html#visi%C3%B3n-general", - "relUrl": "/sq-rAL/user/android-auto.html#overview" + "relUrl": "/es-rES/user/android-auto.html#visión-general" },"247": { "doc": "Android Auto", - "title": "訊息", + "title": "Mensajes", "content": "The Messages tab lists your recent conversations. While driving, you can: . | Have messages read aloud so you don’t need to look at the screen. | Reply by voice or text using your head unit’s reply control, dictating your response hands-free. | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html#%E8%A8%8A%E6%81%AF", + "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html#mensajes", - "relUrl": "/sq-rAL/user/android-auto.html#訊息" + "relUrl": "/es-rES/user/android-auto.html#mensajes" },"248": { "doc": "Android Auto", - "title": "Nodes", + "title": "Nodos", "content": "The Nodes tab shows your mesh node list in a car-friendly layout. Selecting a node opens a node-detail view with key information about that node. See Nodes for the full meaning of the information shown. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html#nodes", + "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html#nodos", - "relUrl": "/sq-rAL/user/android-auto.html#nodes" + "relUrl": "/es-rES/user/android-auto.html#nodos" },"249": { "doc": "Android Auto", "title": "Status", "content": "The Status tab summarizes your current connection and mesh status at a glance — useful for confirming you’re still connected to your radio without opening your phone. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html#status", + "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html#status", - "relUrl": "/sq-rAL/user/android-auto.html#status" + "relUrl": "/es-rES/user/android-auto.html#status" },"250": { "doc": "Android Auto", "title": "Related Topics", "content": ". | Messages & Channels — full messaging features on your phone | Nodes — detailed node list and node-detail information | Connections — how the app connects to your radio | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/android-auto.html#related-topics", + "url": "/Meshtastic-Android/main/es-rES/user/android-auto.html#related-topics", - "relUrl": "/sq-rAL/user/android-auto.html#related-topics" + "relUrl": "/es-rES/user/android-auto.html#related-topics" },"251": { - "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. ⚠️ Note: 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" - },"252": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/app-functions.html#enabling-app-functions", - - "relUrl": "/is-rIS/user/app-functions.html#enabling-app-functions" - },"253": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"254": { - "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" - },"255": { - "doc": "アプリ機能", - "title": "アプリ機能", - "content": "アプリ機能は、Android App Functions API を通じて、Meshtastic の機能を Android システムやオンデバイスの AI アシスタント（Gemini など）に公開します。 有効にすると、アシスタントがあなたに代わってメッシュのワークフロー（例：メッセージの送信やメッシュ状態の確認）を見つけて実行でき、アプリを開く必要がありません。 . ⚠️ 注意： アプリ機能は、Google 版の Android ビルドでのみ利用できます。 . ⚠️ 注意： これは、アプリ内の Chirpy アシスタントとは別のものです。 アプリ機能はシステムの AI アシスタントがあなたのメッシュを操作できるようにするもので、Chirpy は Meshtastic アプリ内の対話型アシスタントです。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/app-functions.html", - - "relUrl": "/ja-rJP/user/app-functions.html" - },"256": { - "doc": "アプリ機能", - "title": "アプリ機能を有効にする", - "content": "アプリ機能は「設定 → システム AI」から制御します（アプリ内の画面は「System AI」と表示されます）。 この画面には次があります： . | 「AI のアクセスを許可」というラベルのマスタートグル。サブタイトルは 「システムの AI アシスタント（例：Gemini）がメッシュ機能を見つけて使えるようにする」 です。 オフの場合、システムには機能が一切公開されません。 | 各機能ごとの個別トグル。公開したい機能だけを公開できます。 | . 機能は、書き込みセクション（何かを変更したり、メッシュにデータを送信したりする機能）と、読み取りセクション（情報を返すだけの機能）に分かれています。 . 書き込み機能 . | 機能 | 内容 | . | メッセージを送信 | 連絡先（ダイレクトメッセージ）またはチャンネルに、最大 237 バイトのテキストメッセージを送信します。 | . 読み取り機能 . | 機能 | 返す内容 | . | メッシュ状態を取得 | メッシュ全体の状態。 | . | ノードリストを取得 | メッシュ上のノードのリスト。 | . | チャンネル情報を取得 | チャンネルに関する情報。 | . | デバイス状態を取得 | 接続中の無線機の状態。 | . | ノード詳細を取得 | 特定のノードに関する詳細情報。 | . | 最近のメッセージを取得 | 会話からの最近のメッセージ。 | . | 未読の概要を取得 | 未読メッセージの概要。 | . | メッシュメトリクスを取得 | メッシュからのテレメトリとメトリクス。 | . ", - "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#アプリ機能を有効にする" - },"257": { - "doc": "アプリ機能", - "title": "プライバシー", - "content": "🔒 プライバシー： 「メッセージを送信」機能は、アシスタントがあなたに代わってメッシュにメッセージを送信できるようにします。 アシスタントに使わせても信頼できる機能だけを有効にしてください。 読み取り機能は、ノード・メッセージ・メトリクスのデータをアシスタントに公開します。共有しても差し支えないものだけを有効にしてください。 各機能には独自のトグルがあり、マスタートグルはそれらすべてを一度にオフにします。 . ", - "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#プライバシー" - },"258": { - "doc": "アプリ機能", - "title": "関連トピック", - "content": ". | メッセージとチャンネル：アプリで直接メッセージを送信する | ノード：読み取り機能が参照するノードリスト | ノードメトリクス：「メッシュメトリクスを取得」の背後にあるテレメトリ | . ", - "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#関連トピック" - },"259": { - "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. ⚠️ Note: 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" - },"260": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/app-functions.html#enabling-app-functions", - - "relUrl": "/ca-rES/user/app-functions.html#enabling-app-functions" - },"261": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"262": { - "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" - },"263": { - "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. ⚠️ Note: 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" - },"264": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/app-functions.html#enabling-app-functions", - - "relUrl": "/sr-rLatn/user/app-functions.html#enabling-app-functions" - },"265": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"266": { - "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" - },"267": { - "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. ⚠️ Note: 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" - },"268": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/app-functions.html#enabling-app-functions", - - "relUrl": "/ko-rKR/user/app-functions.html#enabling-app-functions" - },"269": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"270": { - "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" - },"271": { - "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. ⚠️ Note: 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" - },"272": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/app-functions.html#enabling-app-functions", - - "relUrl": "/ro-rRO/user/app-functions.html#enabling-app-functions" - },"273": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"274": { - "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" - },"275": { - "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. ⚠️ Note: 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" - },"276": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/app-functions.html#enabling-app-functions", - - "relUrl": "/ga-rIE/user/app-functions.html#enabling-app-functions" - },"277": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"278": { - "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" - },"279": { - "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. ⚠️ Note: 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" - },"280": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/app-functions.html#enabling-app-functions", - - "relUrl": "/iw-rIL/user/app-functions.html#enabling-app-functions" - },"281": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"282": { - "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" - },"283": { - "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. ⚠️ Note: 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" - },"284": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/app-functions.html#enabling-app-functions", - - "relUrl": "/sv-rSE/user/app-functions.html#enabling-app-functions" - },"285": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"286": { - "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" - },"287": { - "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. ⚠️ Note: 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" - },"288": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/app-functions.html#enabling-app-functions", - - "relUrl": "/ht-rHT/user/app-functions.html#enabling-app-functions" - },"289": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"290": { - "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" - },"291": { - "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. ⚠️ Huom: Sovellustoiminnot ovat saatavilla vain Google-version Android-laitteissa. ⚠️ Huom: Tämä on erillinen in-app Chirpy -avustajasta. 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" - },"292": { - "doc": "Sovellustoiminnot", - "title": "Sovellustoimintojen käyttöönotto", - "content": "Sovellustoimintoja hallitaan kohdasta Asetukset → Järjestelmän tekoäly (sovelluksen näkymän nimi on “Järjestelmän 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. | . 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). Kirjoitustoiminnot . | Toiminto | Mitä se tekee | . | Lähetä viesti | Lähettää tekstiviestin kontaktille (suora viesti) tai kanavaan, enintään 237 tavua. | . Lukutoiminnot . | Toiminto | Mitä se palauttaa | . | Hae mesh-verkko-tila | Koko mesh-verkon tila. | . | Hae radiolista | Mesh-verkon radiolista. | . | Hae kanavatiedot | Tietoa kanavistasi. | . | Hae laitteen tila | Yhdistetyn radion tila. | . | Hae radion tiedot | Yksityiskohtaiset tiedot tietystä radiosta. | . | Hae viimeisimmät viestit | Viimeisimmät viestisi keskusteluista. | . | Hae lukemattomien yhteenveto | Yhteenveto lukemattomista viesteistä. | . | Hae mesh-metriikat | Mesh-verkon telemetria ja metriikat. | . ", - "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" - },"293": { - "doc": "Sovellustoiminnot", - "title": "Yksityisyys", - "content": "🔒 Tietosuoja: Lähetä viesti -toiminnon avulla avustaja voi lähettää viestejä mesh-verkkoosi puolestasi. Ota käyttöön vain ne toiminnot, joihin luotat avustajan saavan käyttää. Lukutoiminnot tuovat radion, viestien ja metriikoiden tiedot avustajan käyttöön — ota käyttöön vain se, mitä haluat jakaa. Jokaisella toiminnolla on oma kytkin, ja pääkytkin poistaa kaikki käytöstä kerralla. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/app-functions.html#yksityisyys", - - "relUrl": "/fi-rFI/user/app-functions.html#yksityisyys" - },"294": { - "doc": "Sovellustoiminnot", - "title": "Aiheeseen liittyvät aiheet", - "content": ". | Viestit ja kanavat — viestien lähettäminen suoraan sovelluksessa | Radiot — radiolista, josta lukutoiminnot hakevat tiedot | Radiometriikat — telemetria, jonka pohjalta Hae mesh-metriikat muodostuu | . ", - "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" - },"295": { - "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. ⚠️ Note: 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" - },"296": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/app-functions.html#enabling-app-functions", - - "relUrl": "/gl-rES/user/app-functions.html#enabling-app-functions" - },"297": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"298": { - "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" - },"299": { - "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. ⚠️ Note: 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" - },"300": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/app-functions.html#enabling-app-functions", - - "relUrl": "/uk-rUA/user/app-functions.html#enabling-app-functions" - },"301": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"302": { - "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" - },"303": { "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. ⚠️ Note: 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" - },"304": { + },"252": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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. Write Functions . | Funktion | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Funktion | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", "url": "/Meshtastic-Android/main/de-rDE/user/app-functions.html#enabling-app-functions", "relUrl": "/de-rDE/user/app-functions.html#enabling-app-functions" - },"305": { + },"253": { "doc": "App Functions", "title": "Datenschutz", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"306": { + },"254": { "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/de-rDE/user/app-functions.html#related-topics", "relUrl": "/de-rDE/user/app-functions.html#related-topics" - },"307": { + },"255": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/ca-rES/user/app-functions.html", - "relUrl": "/hr-rHR/user/app-functions.html" - },"308": { + "relUrl": "/ca-rES/user/app-functions.html" + },"256": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/ca-rES/user/app-functions.html#enabling-app-functions", - "relUrl": "/hr-rHR/user/app-functions.html#enabling-app-functions" - },"309": { + "relUrl": "/ca-rES/user/app-functions.html#enabling-app-functions" + },"257": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/ca-rES/user/app-functions.html#privacy", - "relUrl": "/hr-rHR/user/app-functions.html#privacy" - },"310": { + "relUrl": "/ca-rES/user/app-functions.html#privacy" + },"258": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/app-functions.html#related-topics", - "relUrl": "/hr-rHR/user/app-functions.html#related-topics" - },"311": { - "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. ⚠️ Note: 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" - },"312": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/app-functions.html#enabling-app-functions", - - "relUrl": "/lt-rLT/user/app-functions.html#enabling-app-functions" - },"313": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"314": { - "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" - },"315": { - "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. ⚠️ Note: 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" - },"316": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/en/user/app-functions.html#enabling-app-functions", - - "relUrl": "/en/user/app-functions.html#enabling-app-functions" - },"317": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/en/user/app-functions.html#privacy", - - "relUrl": "/en/user/app-functions.html#privacy" - },"318": { - "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" - },"319": { - "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. ⚠️ Note: 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" - },"320": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/app-functions.html#enabling-app-functions", - - "relUrl": "/hu-rHU/user/app-functions.html#enabling-app-functions" - },"321": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"322": { - "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" - },"323": { - "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. ⚠️ Note: 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" - },"324": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Функция | Какво прави | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Функция | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/app-functions.html#enabling-app-functions", - - "relUrl": "/bg-rBG/user/app-functions.html#enabling-app-functions" - },"325": { - "doc": "App Functions", - "title": "Поверителност", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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#поверителност" - },"326": { - "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#свързани-теми" - },"327": { - "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. ⚠️ Note: 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" - },"328": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/app-functions.html#enabling-app-functions", - - "relUrl": "/sl-rSI/user/app-functions.html#enabling-app-functions" - },"329": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"330": { - "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" - },"331": { - "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. ⚠️ Note: 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" - },"332": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/app-functions.html#enabling-app-functions", - - "relUrl": "/pt-rPT/user/app-functions.html#enabling-app-functions" - },"333": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"334": { - "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" - },"335": { + "relUrl": "/ca-rES/user/app-functions.html#related-topics" + },"259": { "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. ⚠️ Note: 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" - },"336": { + },"260": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", "url": "/Meshtastic-Android/main/be-rBY/user/app-functions.html#enabling-app-functions", "relUrl": "/be-rBY/user/app-functions.html#enabling-app-functions" - },"337": { + },"261": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"338": { + },"262": { "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" - },"339": { + },"263": { + "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. ⚠️ Note: 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" + },"264": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/app-functions.html#enabling-app-functions", + + "relUrl": "/uk-rUA/user/app-functions.html#enabling-app-functions" + },"265": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"266": { + "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" + },"267": { + "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. ⚠️ Note: 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" + },"268": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/app-functions.html#enabling-app-functions", + + "relUrl": "/zh-rCN/user/app-functions.html#enabling-app-functions" + },"269": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"270": { + "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" + },"271": { + "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. ⚠️ Note: 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" + },"272": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Функция | Какво прави | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Функция | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/app-functions.html#enabling-app-functions", + + "relUrl": "/bg-rBG/user/app-functions.html#enabling-app-functions" + },"273": { + "doc": "App Functions", + "title": "Поверителност", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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#поверителност" + },"274": { + "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#свързани-теми" + },"275": { + "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. ⚠️ Note: 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" + },"276": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/app-functions.html#enabling-app-functions", + + "relUrl": "/zh-rTW/user/app-functions.html#enabling-app-functions" + },"277": { + "doc": "App Functions", + "title": "隱私", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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#隱私" + },"278": { + "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#相關主題" + },"279": { + "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. ⚠️ Note: 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" + },"280": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/app-functions.html#enabling-app-functions", + + "relUrl": "/sr-rLatn/user/app-functions.html#enabling-app-functions" + },"281": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"282": { + "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" + },"283": { + "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. ⚠️ Note: 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" + },"284": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/app-functions.html#enabling-app-functions", + + "relUrl": "/cs-rCZ/user/app-functions.html#enabling-app-functions" + },"285": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"286": { + "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/cs-rCZ/user/app-functions.html#related-topics", + + "relUrl": "/cs-rCZ/user/app-functions.html#related-topics" + },"287": { + "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. ⚠️ Note: 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" + },"288": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/en/user/app-functions.html#enabling-app-functions", + + "relUrl": "/en/user/app-functions.html#enabling-app-functions" + },"289": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", + "url": "/Meshtastic-Android/main/en/user/app-functions.html#privacy", + + "relUrl": "/en/user/app-functions.html#privacy" + },"290": { + "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" + },"291": { + "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. ⚠️ Note: 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" + },"292": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/app-functions.html#enabling-app-functions", + + "relUrl": "/sl-rSI/user/app-functions.html#enabling-app-functions" + },"293": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"294": { + "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" + },"295": { + "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. ⚠️ Note: 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" + },"296": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/app-functions.html#enabling-app-functions", + + "relUrl": "/it-rIT/user/app-functions.html#enabling-app-functions" + },"297": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"298": { + "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" + },"299": { "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. ⚠️ Note: 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" - },"340": { + },"300": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/app-functions.html#enabling-app-functions", "relUrl": "/pt-rBR/user/app-functions.html#enabling-app-functions" - },"341": { + },"301": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"342": { + },"302": { "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" - },"343": { + },"303": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/is-rIS/user/app-functions.html", - "relUrl": "/el-rGR/user/app-functions.html" - },"344": { + "relUrl": "/is-rIS/user/app-functions.html" + },"304": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/is-rIS/user/app-functions.html#enabling-app-functions", - "relUrl": "/el-rGR/user/app-functions.html#enabling-app-functions" - },"345": { + "relUrl": "/is-rIS/user/app-functions.html#enabling-app-functions" + },"305": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/el-rGR/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/is-rIS/user/app-functions.html#privacy", - "relUrl": "/el-rGR/user/app-functions.html#privacy" - },"346": { + "relUrl": "/is-rIS/user/app-functions.html#privacy" + },"306": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/app-functions.html#related-topics", - "relUrl": "/el-rGR/user/app-functions.html#related-topics" - },"347": { + "relUrl": "/is-rIS/user/app-functions.html#related-topics" + },"307": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/app-functions.html", - "relUrl": "/es-rES/user/app-functions.html" - },"348": { + "relUrl": "/fr-rFR/user/app-functions.html" + },"308": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/es-rES/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/fr-rFR/user/app-functions.html#enabling-app-functions", - "relUrl": "/es-rES/user/app-functions.html#enabling-app-functions" - },"349": { + "relUrl": "/fr-rFR/user/app-functions.html#enabling-app-functions" + },"309": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/es-rES/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/fr-rFR/user/app-functions.html#privacy", - "relUrl": "/es-rES/user/app-functions.html#privacy" - },"350": { + "relUrl": "/fr-rFR/user/app-functions.html#privacy" + },"310": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/app-functions.html#related-topics", - "relUrl": "/es-rES/user/app-functions.html#related-topics" - },"351": { + "relUrl": "/fr-rFR/user/app-functions.html#related-topics" + },"311": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/srp/user/app-functions.html", - "relUrl": "/tr-rTR/user/app-functions.html" - },"352": { + "relUrl": "/srp/user/app-functions.html" + },"312": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/srp/user/app-functions.html#enabling-app-functions", - "relUrl": "/tr-rTR/user/app-functions.html#enabling-app-functions" - },"353": { + "relUrl": "/srp/user/app-functions.html#enabling-app-functions" + },"313": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/srp/user/app-functions.html#privacy", - "relUrl": "/tr-rTR/user/app-functions.html#privacy" - },"354": { + "relUrl": "/srp/user/app-functions.html#privacy" + },"314": { "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", + "url": "/Meshtastic-Android/main/srp/user/app-functions.html#related-topics", - "relUrl": "/tr-rTR/user/app-functions.html#related-topics" - },"355": { + "relUrl": "/srp/user/app-functions.html#related-topics" + },"315": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/sk-rSK/user/app-functions.html", - "relUrl": "/no-rNO/user/app-functions.html" - },"356": { + "relUrl": "/sk-rSK/user/app-functions.html" + },"316": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/sk-rSK/user/app-functions.html#enabling-app-functions", - "relUrl": "/no-rNO/user/app-functions.html#enabling-app-functions" - },"357": { + "relUrl": "/sk-rSK/user/app-functions.html#enabling-app-functions" + },"317": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/no-rNO/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/sk-rSK/user/app-functions.html#privacy", - "relUrl": "/no-rNO/user/app-functions.html#privacy" - },"358": { + "relUrl": "/sk-rSK/user/app-functions.html#privacy" + },"318": { "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", + "url": "/Meshtastic-Android/main/sk-rSK/user/app-functions.html#related-topics", - "relUrl": "/no-rNO/user/app-functions.html#related-topics" - },"359": { + "relUrl": "/sk-rSK/user/app-functions.html#related-topics" + },"319": { + "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. ⚠️ Huom: Sovellustoiminnot ovat saatavilla vain Google-version Android-laitteissa. ⚠️ Huom: Tämä on erillinen in-app Chirpy -avustajasta. 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" + },"320": { + "doc": "Sovellustoiminnot", + "title": "Sovellustoimintojen käyttöönotto", + "content": "Sovellustoimintoja hallitaan kohdasta Asetukset → Järjestelmän tekoäly (sovelluksen näkymän nimi on “Järjestelmän 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. | . 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). Kirjoitustoiminnot . | Toiminto | Mitä se tekee | . | Lähetä viesti | Lähettää tekstiviestin kontaktille (suora viesti) tai kanavaan, enintään 237 tavua. | . Lukutoiminnot . | Toiminto | Mitä se palauttaa | . | Hae mesh-verkko-tila | Koko mesh-verkon tila. | . | Hae radiolista | Mesh-verkon radiolista. | . | Hae kanavatiedot | Tietoa kanavistasi. | . | Hae laitteen tila | Yhdistetyn radion tila. | . | Hae radion tiedot | Yksityiskohtaiset tiedot tietystä radiosta. | . | Hae viimeisimmät viestit | Viimeisimmät viestisi keskusteluista. | . | Hae lukemattomien yhteenveto | Yhteenveto lukemattomista viesteistä. | . | Hae mesh-metriikat | Mesh-verkon telemetria ja metriikat. | . ", + "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" + },"321": { + "doc": "Sovellustoiminnot", + "title": "Yksityisyys", + "content": "🔒 Tietosuoja: Lähetä viesti -toiminnon avulla avustaja voi lähettää viestejä mesh-verkkoosi puolestasi. Ota käyttöön vain ne toiminnot, joihin luotat avustajan saavan käyttää. Lukutoiminnot tuovat radion, viestien ja metriikoiden tiedot avustajan käyttöön — ota käyttöön vain se, mitä haluat jakaa. Jokaisella toiminnolla on oma kytkin, ja pääkytkin poistaa kaikki käytöstä kerralla. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/app-functions.html#yksityisyys", + + "relUrl": "/fi-rFI/user/app-functions.html#yksityisyys" + },"322": { + "doc": "Sovellustoiminnot", + "title": "Aiheeseen liittyvät aiheet", + "content": ". | Viestit ja kanavat — viestien lähettäminen suoraan sovelluksessa | Radiot — radiolista, josta lukutoiminnot hakevat tiedot | Radiometriikat — telemetria, jonka pohjalta Hae mesh-metriikat muodostuu | . ", + "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" + },"323": { "doc": "Функции приложения", "title": "Функции приложения", "content": "Функции приложения предоставляют возможности Meshtastic системе Android и встроенным AI-помощникам (таким как Gemini) через API функций приложения Android. С их включением помощник может находить и запускать сетевые рабочие процессы за тебя — например, отправлять сообщение или проверять статус сети — не утруждая тебя открытием приложения. ⚠️ Примечание: Функции приложения доступны только на Android-версиях от Google. ⚠️ Примечание: Это отдельно от встроенного в приложении помощника Chirpy. Функции приложения позволяют системному AI-помощнику действовать с вашей сетью; Chirpy — это голосовой помощник прямо внутри приложения Meshtastic. ", "url": "/Meshtastic-Android/main/ru-rRU/user/app-functions.html", "relUrl": "/ru-rRU/user/app-functions.html" - },"360": { + },"324": { "doc": "Функции приложения", "title": "Включение функций приложения", "content": "Функции приложения управляются через Настройки → Системный ИИ (на экране в приложении указано “Системный ИИ”). Экран содержит: . | Главный переключатель с надписью “Разрешить доступ ИИ” и подзаголовком “Позволь системным ИИ-ассистентам (например, Gemini) обнаруживать и использовать функции сети”. Когда выключено, системе не доступны никакие функции. | Отдельный переключатель для каждой функции, чтобы включать только те возможности, которые хочешь. | . Функции разделены на секцию Запись (функции, которые что-то меняют или отправляют данные в сеть) и Чтение (только возвращают информацию). Функции записи . | Функция | Что она делает | . | Отправить сообщение | Отправляет текстовое сообщение контакту (личное сообщение) или каналу размером до 237 байт. | . Функции записи . | Функция | Что она возвращает | . | Получить состояние сети | Общее состояние сети. | . | Получить список нод | Список узлов в твоей сети. | . | Получить информацию о канале | Информация о твоих каналах. | . | Получить состояние устройства | Состояние подключенного радиоустройства. | . | Получить детали ноды | Подробная информация о конкретной ноде. | . | Получить последние сообщения | Последние сообщения из твоих разговоров. | . | Получить обзор непрочитанного | Сводка непрочитанных сообщений. | . | Получить метрики сети | Телеметрия и метрики твоей сети. | . ", "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#включение-функций-приложения" - },"361": { + },"325": { "doc": "Функции приложения", "title": "Приватность", "content": "🔒 Приватность: Функция Отправить сообщение позволяет помощнику отправлять сообщения в твоей сети от твоего имени. Включай только те функции, по которым ты доверяешь ассистенту. Функции чтения предоставляют ассистенту данные о ноде, сообщениях и метриках — включай только то, чем готов делиться. У каждой функции есть свой переключатель, а главный переключатель выключает их все сразу. ", "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#приватность" - },"362": { + },"326": { "doc": "Функции приложения", "title": "Связанные темы", "content": ". | Сообщения и каналы — отправка сообщений прямо в приложении | Ноды — список нод, из которого берут данные функции чтения | Метрики нод — телеметрия за Получение метрик сети | . ", "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#связанные-темы" + },"327": { + "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. ⚠️ Note: 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" + },"328": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/app-functions.html#enabling-app-functions", + + "relUrl": "/ko-rKR/user/app-functions.html#enabling-app-functions" + },"329": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"330": { + "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" + },"331": { + "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. ⚠️ Note: 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" + },"332": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/app-functions.html#enabling-app-functions", + + "relUrl": "/hr-rHR/user/app-functions.html#enabling-app-functions" + },"333": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"334": { + "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" + },"335": { + "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. ⚠️ Note: 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" + },"336": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/app-functions.html#enabling-app-functions", + + "relUrl": "/sq-rAL/user/app-functions.html#enabling-app-functions" + },"337": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"338": { + "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" + },"339": { + "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. ⚠️ Note: 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" + },"340": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/app-functions.html#enabling-app-functions", + + "relUrl": "/no-rNO/user/app-functions.html#enabling-app-functions" + },"341": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"342": { + "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" + },"343": { + "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. ⚠️ Note: 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" + },"344": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/app-functions.html#enabling-app-functions", + + "relUrl": "/lt-rLT/user/app-functions.html#enabling-app-functions" + },"345": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"346": { + "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" + },"347": { + "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. ⚠️ Note: 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" + },"348": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/app-functions.html#enabling-app-functions", + + "relUrl": "/ar-rSA/user/app-functions.html#enabling-app-functions" + },"349": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"350": { + "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" + },"351": { + "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. ⚠️ Note: 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" + },"352": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/app-functions.html#enabling-app-functions", + + "relUrl": "/pt-rPT/user/app-functions.html#enabling-app-functions" + },"353": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"354": { + "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" + },"355": { + "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. ⚠️ Note: 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" + },"356": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/app-functions.html#enabling-app-functions", + + "relUrl": "/iw-rIL/user/app-functions.html#enabling-app-functions" + },"357": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"358": { + "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" + },"359": { + "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. ⚠️ Note: 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" + },"360": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/app-functions.html#enabling-app-functions", + + "relUrl": "/el-rGR/user/app-functions.html#enabling-app-functions" + },"361": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"362": { + "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" },"363": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/app-functions.html", - "relUrl": "/nl-rNL/user/app-functions.html" + "relUrl": "/ro-rRO/user/app-functions.html" },"364": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/ro-rRO/user/app-functions.html#enabling-app-functions", - "relUrl": "/nl-rNL/user/app-functions.html#enabling-app-functions" + "relUrl": "/ro-rRO/user/app-functions.html#enabling-app-functions" },"365": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/ro-rRO/user/app-functions.html#privacy", - "relUrl": "/nl-rNL/user/app-functions.html#privacy" + "relUrl": "/ro-rRO/user/app-functions.html#privacy" },"366": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/app-functions.html#related-topics", - "relUrl": "/nl-rNL/user/app-functions.html#related-topics" + "relUrl": "/ro-rRO/user/app-functions.html#related-topics" },"367": { "doc": "App Functions", "title": "App Functions", @@ -2599,282 +2599,282 @@ "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/app-functions.html", - "relUrl": "/it-rIT/user/app-functions.html" + "relUrl": "/ga-rIE/user/app-functions.html" },"372": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/ga-rIE/user/app-functions.html#enabling-app-functions", - "relUrl": "/it-rIT/user/app-functions.html#enabling-app-functions" + "relUrl": "/ga-rIE/user/app-functions.html#enabling-app-functions" },"373": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/it-rIT/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/ga-rIE/user/app-functions.html#privacy", - "relUrl": "/it-rIT/user/app-functions.html#privacy" + "relUrl": "/ga-rIE/user/app-functions.html#privacy" },"374": { "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/app-functions.html#related-topics", - "relUrl": "/it-rIT/user/app-functions.html#related-topics" + "relUrl": "/ga-rIE/user/app-functions.html#related-topics" },"375": { - "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. ⚠️ Note: 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" - },"376": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/app-functions.html#enabling-app-functions", - - "relUrl": "/ar-rSA/user/app-functions.html#enabling-app-functions" - },"377": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"378": { - "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" - },"379": { - "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. ⚠️ Note: 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" - },"380": { - "doc": "App Functions", - "title": "Enabling App Functions", - "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/app-functions.html#enabling-app-functions", - - "relUrl": "/sk-rSK/user/app-functions.html#enabling-app-functions" - },"381": { - "doc": "App Functions", - "title": "Privacy", - "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"382": { - "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" - },"383": { "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. ⚠️ Note: 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" - },"384": { + },"376": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/app-functions.html#enabling-app-functions", "relUrl": "/pl-rPL/user/app-functions.html#enabling-app-functions" - },"385": { + },"377": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" - },"386": { + },"378": { "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" - },"387": { + },"379": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/nl-rNL/user/app-functions.html", - "relUrl": "/zh-rTW/user/app-functions.html" - },"388": { + "relUrl": "/nl-rNL/user/app-functions.html" + },"380": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/nl-rNL/user/app-functions.html#enabling-app-functions", - "relUrl": "/zh-rTW/user/app-functions.html#enabling-app-functions" - },"389": { + "relUrl": "/nl-rNL/user/app-functions.html#enabling-app-functions" + },"381": { "doc": "App Functions", - "title": "隱私", + "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/app-functions.html#%E9%9A%B1%E7%A7%81", + "url": "/Meshtastic-Android/main/nl-rNL/user/app-functions.html#privacy", - "relUrl": "/zh-rTW/user/app-functions.html#隱私" - },"390": { + "relUrl": "/nl-rNL/user/app-functions.html#privacy" + },"382": { "doc": "App Functions", - "title": "相關主題", + "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-rTW/user/app-functions.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C", + "url": "/Meshtastic-Android/main/nl-rNL/user/app-functions.html#related-topics", - "relUrl": "/zh-rTW/user/app-functions.html#相關主題" + "relUrl": "/nl-rNL/user/app-functions.html#related-topics" + },"383": { + "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. ⚠️ Note: 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" + },"384": { + "doc": "App Functions", + "title": "Enabling App Functions", + "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/app-functions.html#enabling-app-functions", + + "relUrl": "/sv-rSE/user/app-functions.html#enabling-app-functions" + },"385": { + "doc": "App Functions", + "title": "Privacy", + "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle 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" + },"386": { + "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" + },"387": { + "doc": "アプリ機能", + "title": "アプリ機能", + "content": "アプリ機能は、Android App Functions API を通じて、Meshtastic の機能を Android システムやオンデバイスの AI アシスタント（Gemini など）に公開します。 有効にすると、アシスタントがあなたに代わってメッシュのワークフロー（例：メッセージの送信やメッシュ状態の確認）を見つけて実行でき、アプリを開く必要がありません。 . ⚠️ 注意： アプリ機能は、Google 版の Android ビルドでのみ利用できます。 . ⚠️ 注意： これは、アプリ内の Chirpy アシスタントとは別のものです。 アプリ機能はシステムの AI アシスタントがあなたのメッシュを操作できるようにするもので、Chirpy は Meshtastic アプリ内の対話型アシスタントです。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/app-functions.html", + + "relUrl": "/ja-rJP/user/app-functions.html" + },"388": { + "doc": "アプリ機能", + "title": "アプリ機能を有効にする", + "content": "アプリ機能は「設定 → システム AI」から制御します（アプリ内の画面は「System AI」と表示されます）。 この画面には次があります： . | 「AI のアクセスを許可」というラベルのマスタートグル。サブタイトルは 「システムの AI アシスタント（例：Gemini）がメッシュ機能を見つけて使えるようにする」 です。 オフの場合、システムには機能が一切公開されません。 | 各機能ごとの個別トグル。公開したい機能だけを公開できます。 | . 機能は、書き込みセクション（何かを変更したり、メッシュにデータを送信したりする機能）と、読み取りセクション（情報を返すだけの機能）に分かれています。 . 書き込み機能 . | 機能 | 内容 | . | メッセージを送信 | 連絡先（ダイレクトメッセージ）またはチャンネルに、最大 237 バイトのテキストメッセージを送信します。 | . 読み取り機能 . | 機能 | 返す内容 | . | メッシュ状態を取得 | メッシュ全体の状態。 | . | ノードリストを取得 | メッシュ上のノードのリスト。 | . | チャンネル情報を取得 | チャンネルに関する情報。 | . | デバイス状態を取得 | 接続中の無線機の状態。 | . | ノード詳細を取得 | 特定のノードに関する詳細情報。 | . | 最近のメッセージを取得 | 会話からの最近のメッセージ。 | . | 未読の概要を取得 | 未読メッセージの概要。 | . | メッシュメトリクスを取得 | メッシュからのテレメトリとメトリクス。 | . ", + "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#アプリ機能を有効にする" + },"389": { + "doc": "アプリ機能", + "title": "プライバシー", + "content": "🔒 プライバシー： 「メッセージを送信」機能は、アシスタントがあなたに代わってメッシュにメッセージを送信できるようにします。 アシスタントに使わせても信頼できる機能だけを有効にしてください。 読み取り機能は、ノード・メッセージ・メトリクスのデータをアシスタントに公開します。共有しても差し支えないものだけを有効にしてください。 各機能には独自のトグルがあり、マスタートグルはそれらすべてを一度にオフにします。 . ", + "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#プライバシー" + },"390": { + "doc": "アプリ機能", + "title": "関連トピック", + "content": ". | メッセージとチャンネル：アプリで直接メッセージを送信する | ノード：読み取り機能が参照するノードリスト | ノードメトリクス：「メッシュメトリクスを取得」の背後にあるテレメトリ | . ", + "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#関連トピック" },"391": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/app-functions.html", - "relUrl": "/cs-rCZ/user/app-functions.html" + "relUrl": "/hu-rHU/user/app-functions.html" },"392": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/hu-rHU/user/app-functions.html#enabling-app-functions", - "relUrl": "/cs-rCZ/user/app-functions.html#enabling-app-functions" + "relUrl": "/hu-rHU/user/app-functions.html#enabling-app-functions" },"393": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/hu-rHU/user/app-functions.html#privacy", - "relUrl": "/cs-rCZ/user/app-functions.html#privacy" + "relUrl": "/hu-rHU/user/app-functions.html#privacy" },"394": { "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/cs-rCZ/user/app-functions.html#related-topics", + "url": "/Meshtastic-Android/main/hu-rHU/user/app-functions.html#related-topics", - "relUrl": "/cs-rCZ/user/app-functions.html#related-topics" + "relUrl": "/hu-rHU/user/app-functions.html#related-topics" },"395": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/app-functions.html", - "relUrl": "/fr-rFR/user/app-functions.html" + "relUrl": "/ht-rHT/user/app-functions.html" },"396": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/ht-rHT/user/app-functions.html#enabling-app-functions", - "relUrl": "/fr-rFR/user/app-functions.html#enabling-app-functions" + "relUrl": "/ht-rHT/user/app-functions.html#enabling-app-functions" },"397": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/ht-rHT/user/app-functions.html#privacy", - "relUrl": "/fr-rFR/user/app-functions.html#privacy" + "relUrl": "/ht-rHT/user/app-functions.html#privacy" },"398": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/app-functions.html#related-topics", - "relUrl": "/fr-rFR/user/app-functions.html#related-topics" + "relUrl": "/ht-rHT/user/app-functions.html#related-topics" },"399": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/gl-rES/user/app-functions.html", - "relUrl": "/zh-rCN/user/app-functions.html" + "relUrl": "/gl-rES/user/app-functions.html" },"400": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/gl-rES/user/app-functions.html#enabling-app-functions", - "relUrl": "/zh-rCN/user/app-functions.html#enabling-app-functions" + "relUrl": "/gl-rES/user/app-functions.html#enabling-app-functions" },"401": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/gl-rES/user/app-functions.html#privacy", - "relUrl": "/zh-rCN/user/app-functions.html#privacy" + "relUrl": "/gl-rES/user/app-functions.html#privacy" },"402": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/app-functions.html#related-topics", - "relUrl": "/zh-rCN/user/app-functions.html#related-topics" + "relUrl": "/gl-rES/user/app-functions.html#related-topics" },"403": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/app-functions.html", - "relUrl": "/srp/user/app-functions.html" + "relUrl": "/tr-rTR/user/app-functions.html" },"404": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/srp/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/tr-rTR/user/app-functions.html#enabling-app-functions", - "relUrl": "/srp/user/app-functions.html#enabling-app-functions" + "relUrl": "/tr-rTR/user/app-functions.html#enabling-app-functions" },"405": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/srp/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/tr-rTR/user/app-functions.html#privacy", - "relUrl": "/srp/user/app-functions.html#privacy" + "relUrl": "/tr-rTR/user/app-functions.html#privacy" },"406": { "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/app-functions.html#related-topics", - "relUrl": "/srp/user/app-functions.html#related-topics" + "relUrl": "/tr-rTR/user/app-functions.html#related-topics" },"407": { "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. ⚠️ Note: 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", + "url": "/Meshtastic-Android/main/es-rES/user/app-functions.html", - "relUrl": "/sq-rAL/user/app-functions.html" + "relUrl": "/es-rES/user/app-functions.html" },"408": { "doc": "App Functions", "title": "Enabling App Functions", "content": "App Functions are controlled from Settings → System AI (the in-app screen is labeled “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. | . 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). Write Functions . | Function | What it does | . | Send Message | Sends a text message to a contact (direct message) or to a channel, up to 237 bytes. | . Read Functions . | Function | What it returns | . | Get Mesh Status | Overall mesh status. | . | 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 Recent Messages | Recent messages from your conversations. | . | Get Unread Summary | A summary of unread messages. | . | Get Mesh Metrics | Telemetry and metrics from your mesh. | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/app-functions.html#enabling-app-functions", + "url": "/Meshtastic-Android/main/es-rES/user/app-functions.html#enabling-app-functions", - "relUrl": "/sq-rAL/user/app-functions.html#enabling-app-functions" + "relUrl": "/es-rES/user/app-functions.html#enabling-app-functions" },"409": { "doc": "App Functions", "title": "Privacy", "content": "🔒 Privacy: The Send Message function lets an assistant send messages to your mesh on your behalf. Only enable functions you trust the assistant to use. The read functions expose node, message, and metric data to the assistant — enable only what you’re comfortable sharing. Each function has its own toggle, and the master toggle turns all of them off at once. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/app-functions.html#privacy", + "url": "/Meshtastic-Android/main/es-rES/user/app-functions.html#privacy", - "relUrl": "/sq-rAL/user/app-functions.html#privacy" + "relUrl": "/es-rES/user/app-functions.html#privacy" },"410": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/app-functions.html#related-topics", - "relUrl": "/sq-rAL/user/app-functions.html#related-topics" + "relUrl": "/es-rES/user/app-functions.html#related-topics" },"411": { "doc": "Architecture", "title": "Architecture", @@ -2967,1426 +2967,1426 @@ "relUrl": "/en/developer/codebase.html#version-catalog-highlights" },"424": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/is-rIS/user/connections.html", - - "relUrl": "/is-rIS/user/connections.html" - },"425": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Lýsing | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Aftengd | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#bluetooth-ble", - - "relUrl": "/is-rIS/user/connections.html#bluetooth-ble" - },"426": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#usb-serial", - - "relUrl": "/is-rIS/user/connections.html#usb-serial" - },"427": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#tcpip-network", - - "relUrl": "/is-rIS/user/connections.html#tcpip-network" - },"428": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#reconnection-behavior", - - "relUrl": "/is-rIS/user/connections.html#reconnection-behavior" - },"429": { - "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" - },"430": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"431": { - "doc": "コネクション", - "title": "コネクション", - "content": "Meshtastic は、スマートフォン／デスクトップと無線機ノード間の通信に複数の接続方式をサポートしています。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html", - - "relUrl": "/ja-rJP/user/connections.html" - },"432": { - "doc": "コネクション", - "title": "Bluetooth（BLE）", - "content": "Bluetooth Low Energy は、Android で標準的かつ最も一般的な接続方法です。 . デバイスをペアリングする . | Meshtastic 無線機の電源が入っていて、ペアリングモードになっていることを確認します。 | アプリを開き、「接続」タブに移動します。 | 「Bluetooth デバイスをスキャン」をタップすると、近くの Meshtastic 無線機が表示されます。 | リストからデバイスを選択します。 | Bluetooth のペアリング確認が表示されたら承認します。 | . 接続カードの下にあるセグメント化されたボタン列（接続方式のセレクター）を使って、Bluetooth・ネットワーク・USB の接続方式を切り替えます（一度に 1 つが有効になります）： . 💡 ヒント： デバイスが表示されない場合は、Bluetooth と位置情報の権限が許可されているか、また無線機が別のデバイスにすでに接続されていないかを確認してください。 . 接続ステータス . | アイコン | 状態 | 説明 | . | 🟢 | 接続済 | 無線リンクが確立しています | . | 🟡 | 接続中 | ハンドシェイク中 | . | 🔴 | 切断 | 接続がありません | . | ⚪ | 未設定 | デバイスが選択されていません | . 接続時には、ステータスインジケーターが現在の接続状態を表示します： . デバイスが見つからない場合、アプリは操作手順とともに空の状態を表示します： . Bluetooth のトラブルシューティング . | デバイスが見つからない： Bluetooth をオフ／オンし、位置情報が有効になっていることを確認します。 | 接続が切れる： 無線機に近づき、電波干渉がないか確認します。 | ペアリングが拒否される： Android の Bluetooth 設定でデバイスの登録を解除し、やり直します。 | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html#bluetoothble", - - "relUrl": "/ja-rJP/user/connections.html#bluetoothble" - },"433": { - "doc": "コネクション", - "title": "USB シリアル", - "content": "USB 接続は有線での代替手段で、デスクトップや Bluetooth が使えない場合に便利です。 . セットアップ . | USB ケーブルで無線機をデバイスに接続します。 | アプリが USB の使用許可を求めるので、「許可」をタップします。 | 接続が自動的に確立されます。 | . ⚠️ 注意： USB 接続には、Android デバイスの 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-シリアル" - },"434": { - "doc": "コネクション", - "title": "TCP/IP（ネットワーク）", - "content": "一部の Meshtastic 無線機は WiFi／Ethernet 接続に対応しており、ローカルネットワーク経由の TCP 接続が可能です。 まず、無線機自身の WiFi 設定（ファームウェアのウェブインターフェースや別の接続方法を使用）で無線機をネットワークに接続し、その後アプリから接続します。 . ネットワーク経由で接続する . | 無線機がスマートフォン／デスクトップと同じローカルネットワーク上にあることを確認します。 | 接続画面で、接続方式のセレクターから「ネットワーク」を選択します。 | 無線機は次の 2 通りの方法で選べます： . | ネットワークデバイスをスキャン：これをオンにすると、ローカルネットワーク上で自身を告知している無線機（mDNS ／ _meshtastic._tcp）を自動的に探索します。 見つかったデバイスがリストに表示されるので、タップして接続します。 | デバイスを手動で追加…：無線機の IP アドレス（またはホスト名）とポート（既定：4403）を入力します。 | . | 以前使用したネットワークアドレスは「最近のネットワークデバイス」に記憶され、すばやく再接続できます（長押しで削除できます）。 | . 💡 ヒント： ネットワーク探索は mDNS を使用するため、両方のデバイスが同じサブネット上にある場合にのみ機能します。 Android 17 以降では、スキャンにローカルネットワークの権限が必要です。探索で何も見つからない場合は、IP アドレスでデバイスを手動追加してください。 . TCP を使う場面 . | 無線機が同じローカルネットワーク上にある | シミュレートされた無線機でテストする | Bluetooth の電波干渉が問題になる環境 | . ", - "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ネットワーク" - },"435": { - "doc": "コネクション", - "title": "再接続の動作", - "content": "アプリは起動時に「最後に選択したデバイス」へ再接続します。 接続方式は、接続画面からいつでも切り替えられます。 . 切断するには、接続画面の切断ボタンをタップします： . ", - "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#再接続の動作" - },"436": { - "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#デスクトップでの接続" - },"437": { - "doc": "コネクション", - "title": "関連トピック", - "content": ". | はじめに：初回起動時のセットアップと権限 | 設定：無線機とユーザー：Bluetooth とネットワークの設定 | デスクトップアプリ：デスクトップ固有の接続に関する詳細 | 対応デバイス：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#関連トピック" - },"438": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/ca-rES/user/connections.html", - - "relUrl": "/ca-rES/user/connections.html" - },"439": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descripció | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Desconnectat | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#bluetooth-ble", - - "relUrl": "/ca-rES/user/connections.html#bluetooth-ble" - },"440": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#usb-serial", - - "relUrl": "/ca-rES/user/connections.html#usb-serial" - },"441": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#tcpip-network", - - "relUrl": "/ca-rES/user/connections.html#tcpip-network" - },"442": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#reconnection-behavior", - - "relUrl": "/ca-rES/user/connections.html#reconnection-behavior" - },"443": { - "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" - },"444": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"445": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html", - - "relUrl": "/sr-rLatn/user/connections.html" - },"446": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Иконица | State | Опис | . | 🟢 | Блутут повезан | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Raskačeno | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#bluetooth-ble", - - "relUrl": "/sr-rLatn/user/connections.html#bluetooth-ble" - },"447": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#usb-serial", - - "relUrl": "/sr-rLatn/user/connections.html#usb-serial" - },"448": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#tcpip-network", - - "relUrl": "/sr-rLatn/user/connections.html#tcpip-network" - },"449": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#reconnection-behavior", - - "relUrl": "/sr-rLatn/user/connections.html#reconnection-behavior" - },"450": { - "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" - },"451": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"452": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html", - - "relUrl": "/ko-rKR/user/connections.html" - },"453": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | 설명 | . | 🟢 | 연결됨 | Active radio link established | . | 🟡 | 연결 중 | Handshake in progress | . | 🔴 | 연결 끊김 | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#bluetooth-ble", - - "relUrl": "/ko-rKR/user/connections.html#bluetooth-ble" - },"454": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#usb-serial", - - "relUrl": "/ko-rKR/user/connections.html#usb-serial" - },"455": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#tcpip-network", - - "relUrl": "/ko-rKR/user/connections.html#tcpip-network" - },"456": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#reconnection-behavior", - - "relUrl": "/ko-rKR/user/connections.html#reconnection-behavior" - },"457": { - "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" - },"458": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"459": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html", - - "relUrl": "/ro-rRO/user/connections.html" - },"460": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descriere | . | 🟢 | Conectat | Active radio link established | . | 🟡 | Conectare | Handshake in progress | . | 🔴 | Deconectat | No active connection | . | ⚪ | Not configured | Nici un dispozitiv selectat | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#bluetooth-ble", - - "relUrl": "/ro-rRO/user/connections.html#bluetooth-ble" - },"461": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#usb-serial", - - "relUrl": "/ro-rRO/user/connections.html#usb-serial" - },"462": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#tcpip-network", - - "relUrl": "/ro-rRO/user/connections.html#tcpip-network" - },"463": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#reconnection-behavior", - - "relUrl": "/ro-rRO/user/connections.html#reconnection-behavior" - },"464": { - "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" - },"465": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"466": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html", - - "relUrl": "/ga-rIE/user/connections.html" - },"467": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Cur síos | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Na ceangailte | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#bluetooth-ble", - - "relUrl": "/ga-rIE/user/connections.html#bluetooth-ble" - },"468": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#usb-serial", - - "relUrl": "/ga-rIE/user/connections.html#usb-serial" - },"469": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#tcpip-network", - - "relUrl": "/ga-rIE/user/connections.html#tcpip-network" - },"470": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#reconnection-behavior", - - "relUrl": "/ga-rIE/user/connections.html#reconnection-behavior" - },"471": { - "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" - },"472": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"473": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html", - - "relUrl": "/iw-rIL/user/connections.html" - },"474": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | תיאור | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | מנותק | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#bluetooth-ble", - - "relUrl": "/iw-rIL/user/connections.html#bluetooth-ble" - },"475": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#usb-serial", - - "relUrl": "/iw-rIL/user/connections.html#usb-serial" - },"476": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#tcpip-network", - - "relUrl": "/iw-rIL/user/connections.html#tcpip-network" - },"477": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#reconnection-behavior", - - "relUrl": "/iw-rIL/user/connections.html#reconnection-behavior" - },"478": { - "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" - },"479": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"480": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html", - - "relUrl": "/sv-rSE/user/connections.html" - },"481": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Beskrivning | . | 🟢 | Ansluten | Active radio link established | . | 🟡 | Ansluter | Handshake in progress | . | 🔴 | Frånkopplad | No active connection | . | ⚪ | Not configured | Ingen enhet vald | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#bluetooth-ble", - - "relUrl": "/sv-rSE/user/connections.html#bluetooth-ble" - },"482": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#usb-serial", - - "relUrl": "/sv-rSE/user/connections.html#usb-serial" - },"483": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#tcpip-network", - - "relUrl": "/sv-rSE/user/connections.html#tcpip-network" - },"484": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#reconnection-behavior", - - "relUrl": "/sv-rSE/user/connections.html#reconnection-behavior" - },"485": { - "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" - },"486": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"487": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html", - - "relUrl": "/ht-rHT/user/connections.html" - },"488": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Deskripsyon | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Dekonekte | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#bluetooth-ble", - - "relUrl": "/ht-rHT/user/connections.html#bluetooth-ble" - },"489": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#usb-serial", - - "relUrl": "/ht-rHT/user/connections.html#usb-serial" - },"490": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#tcpip-network", - - "relUrl": "/ht-rHT/user/connections.html#tcpip-network" - },"491": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#reconnection-behavior", - - "relUrl": "/ht-rHT/user/connections.html#reconnection-behavior" - },"492": { - "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" - },"493": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"494": { - "doc": "Yhteydet", - "title": "Yhteydet", - "content": "Meshtastic tukee useita siirtotapoja puhelimen/työpöydän ja radion välillä viestimiseen. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html", - - "relUrl": "/fi-rFI/user/connections.html" - },"495": { - "doc": "Yhteydet", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy on oletus ja yleisin yhteystapa Androidilla. Laitteen pariliitos . | Varmista, että Meshtastic-radio on päällä ja paritustilassa. | Avaa sovellus ja siirry Yhdistä-välilehdelle. | Napauta Hae bluetooth-laitteita — lähellä olevat Meshtastic-radiot ilmestyvät näkyville. | Valitse laitteesi listasta. | Hyväksy Bluetooth-pariliitospyyntö, jos se tulee näkyviin. | . 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 laitteesi ei näy, varmista että Bluetooth ja sijaintiluvat on myönnetty ja että radio ei ole jo yhdistettynä toiseen laitteeseen. Yhteyden tila . | Ikoni | Tila | Kuvaus | . | 🟢 | Yhdistetty | Aktiivinen radiolinkki muodostettu | . | 🟡 | Yhdistetään | Yhteyden muodostus käynnissä | . | 🔴 | Ei yhdistetty | Ei aktiivista yhteyttä | . | ⚪ | Ei määritetty | Ei laitetta valittuna | . Yhdistettäessä tilailmaisin näyttää nykyisen yhteyden tilan: . Jos laitteita ei löydy, sovellus näyttää tyhjän näkymän ohjeiden kanssa: . Bluetoothin vianmääritys . | Laitetta ei löydy: Kytke Bluetooth pois/päälle ja varmista, että sijainti on käytössä. | Yhteys katkeaa: Siirry lähemmäs radiota ja tarkista mahdolliset häiriöt. | Paritus hylätty: Poista laite Androidin Bluetooth-asetuksista ja yritä uudelleen. | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#bluetooth-ble", - - "relUrl": "/fi-rFI/user/connections.html#bluetooth-ble" - },"496": { - "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 . | Yhdistä radio USB-kaapelilla laitteeseesi. | Sovellus pyytää USB-oikeuksia — paina Salli. | Yhteys muodostetaan automaattisesti. | . ⚠️ Huom: USB-yhteydet vaativat OTG-tuen Android-laitteissa. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#usb-sarjaporttiyhteys", - - "relUrl": "/fi-rFI/user/connections.html#usb-sarjaporttiyhteys" - },"497": { - "doc": "Yhteydet", - "title": "TCP/IP (Verkko)", - "content": "Jotkin Meshtastic-radiot tukevat WiFi tai Ethernet-yhteyttä, mikä mahdollistaa TCP-pohjaiset yhteydet lähiverkkosi kautta. Liitä radio ensin verkkoon käyttämällä radion omia WiFi-asetuksia (laiteohjelmiston verkkokäyttöliittymän tai muun yhteystavan kautta) — yhdistä siihen sitten sovelluksesta. Yhdistäminen verkon kautta . | Varmista, että radio on samassa lähiverkossa kuin puhelimesi tai tietokoneesi. | Valitse yhdistä-näytössä yhteysvalitsimesta Verkko. | 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 tallennetaan Viimeisimmät verkkolaitteet -osioon nopeaa uudelleenyhdistämistä varten (poista pitämällä painettuna). | . 💡 Vinkki: Verkkolaitteiden haku käyttää mDNS:ää, joka toimii vain, kun molemmat laitteet ovat samassa aliverkossa. Android 17:ssä ja uudemmissa versioissa sovellus tarvitsee lähiverkon käyttöoikeuden laitteiden hakuun. Jos haku ei löydä mitään, lisää laite manuaalisesti IP-osoitteella. Milloin TCP-yhteyttä kannattaa käyttää . | Radio on samassa lähiverkossa | Testaus simuloidulla radiolla | Ympäristöt, joissa Bluetoothissa on häiriöongelmia | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#tcpip-verkko", - - "relUrl": "/fi-rFI/user/connections.html#tcpip-verkko" - },"498": { - "doc": "Yhteydet", - "title": "Uudelleenyhdistämisen toiminta", - "content": "Sovellus yhdistyy käynnistyksen yhteydessä viimeksi valittuun laitteeseen. Voit vaihtaa yhteystapaa Yhdistä-näkymästä milloin tahansa. Yhteyden katkaisemiseksi paina Yhdistä-näkymän katkaisupainiketta: . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#uudelleenyhdist%C3%A4misen-toiminta", - - "relUrl": "/fi-rFI/user/connections.html#uudelleenyhdistämisen-toiminta" - },"499": { - "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" - },"500": { - "doc": "Yhteydet", - "title": "Aiheeseen liittyvät aiheet", - "content": ". | Aloitus — ensikäynnistyksen käyttöönotto ja käyttöoikeudet | Asetukset — Radio & käyttäjä — Bluetooth- ja verkkoasetukset | 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" - },"501": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/gl-rES/user/connections.html", - - "relUrl": "/gl-rES/user/connections.html" - },"502": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descrición | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Desconectado | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#bluetooth-ble", - - "relUrl": "/gl-rES/user/connections.html#bluetooth-ble" - },"503": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#usb-serial", - - "relUrl": "/gl-rES/user/connections.html#usb-serial" - },"504": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#tcpip-network", - - "relUrl": "/gl-rES/user/connections.html#tcpip-network" - },"505": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#reconnection-behavior", - - "relUrl": "/gl-rES/user/connections.html#reconnection-behavior" - },"506": { - "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" - },"507": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"508": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html", - - "relUrl": "/uk-rUA/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 Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Опис | . | 🟢 | Під’єднано | Active radio link established | . | 🟡 | Під’єднання | Handshake in progress | . | 🔴 | Відключено | No active connection | . | ⚪ | Not configured | Не вибраний пристрій | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#bluetooth-ble", - - "relUrl": "/uk-rUA/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 via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#usb-serial", - - "relUrl": "/uk-rUA/user/connections.html#usb-serial" - },"511": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#tcpip-network", - - "relUrl": "/uk-rUA/user/connections.html#tcpip-network" - },"512": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#reconnection-behavior", - - "relUrl": "/uk-rUA/user/connections.html#reconnection-behavior" - },"513": { - "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" - },"514": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"515": { "doc": "Verbindungen", "title": "Verbindungen", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", "url": "/Meshtastic-Android/main/de-rDE/user/connections.html", "relUrl": "/de-rDE/user/connections.html" - },"516": { + },"425": { "doc": "Verbindungen", "title": "Bluetooth (BLE)", "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Symbol | Status | Beschreibung | . | 🟢 | Verbunden | Active radio link established | . | 🟡 | Wird verbunden | Handshake in progress | . | 🔴 | Verbindung getrennt | No active connection | . | ⚪ | Not configured | Kein Gerät ausgewählt | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", "url": "/Meshtastic-Android/main/de-rDE/user/connections.html#bluetooth-ble", "relUrl": "/de-rDE/user/connections.html#bluetooth-ble" - },"517": { + },"426": { "doc": "Verbindungen", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Einstellungen . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", "url": "/Meshtastic-Android/main/de-rDE/user/connections.html#usb-serial", "relUrl": "/de-rDE/user/connections.html#usb-serial" - },"518": { + },"427": { "doc": "Verbindungen", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", "url": "/Meshtastic-Android/main/de-rDE/user/connections.html#tcpip-network", "relUrl": "/de-rDE/user/connections.html#tcpip-network" - },"519": { + },"428": { "doc": "Verbindungen", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", "url": "/Meshtastic-Android/main/de-rDE/user/connections.html#reconnection-behavior", "relUrl": "/de-rDE/user/connections.html#reconnection-behavior" - },"520": { + },"429": { "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" - },"521": { + },"430": { "doc": "Verbindungen", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"522": { + },"431": { "doc": "Connections", "title": "Connections", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html", + "url": "/Meshtastic-Android/main/ca-rES/user/connections.html", - "relUrl": "/hr-rHR/user/connections.html" - },"523": { + "relUrl": "/ca-rES/user/connections.html" + },"432": { "doc": "Connections", "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Opis | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Odspojeno | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#bluetooth-ble", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descripció | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Desconnectat | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#bluetooth-ble", - "relUrl": "/hr-rHR/user/connections.html#bluetooth-ble" - },"524": { + "relUrl": "/ca-rES/user/connections.html#bluetooth-ble" + },"433": { "doc": "Connections", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#usb-serial", + "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#usb-serial", - "relUrl": "/hr-rHR/user/connections.html#usb-serial" - },"525": { + "relUrl": "/ca-rES/user/connections.html#usb-serial" + },"434": { "doc": "Connections", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#tcpip-network", + "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#tcpip-network", - "relUrl": "/hr-rHR/user/connections.html#tcpip-network" - },"526": { + "relUrl": "/ca-rES/user/connections.html#tcpip-network" + },"435": { "doc": "Connections", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#reconnection-behavior", + "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#reconnection-behavior", - "relUrl": "/hr-rHR/user/connections.html#reconnection-behavior" - },"527": { + "relUrl": "/ca-rES/user/connections.html#reconnection-behavior" + },"436": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#desktop-connections", - "relUrl": "/hr-rHR/user/connections.html#desktop-connections" - },"528": { + "relUrl": "/ca-rES/user/connections.html#desktop-connections" + },"437": { "doc": "Connections", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#related-topics", - "relUrl": "/hr-rHR/user/connections.html#related-topics" - },"529": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html", - - "relUrl": "/lt-rLT/user/connections.html" - },"530": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Aprašymas | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Atsijungta | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#bluetooth-ble", - - "relUrl": "/lt-rLT/user/connections.html#bluetooth-ble" - },"531": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#usb-serial", - - "relUrl": "/lt-rLT/user/connections.html#usb-serial" - },"532": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#tcpip-network", - - "relUrl": "/lt-rLT/user/connections.html#tcpip-network" - },"533": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#reconnection-behavior", - - "relUrl": "/lt-rLT/user/connections.html#reconnection-behavior" - },"534": { - "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" - },"535": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"536": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/en/user/connections.html", - - "relUrl": "/en/user/connections.html" - },"537": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Description | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Disconnected | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/en/user/connections.html#bluetooth-ble", - - "relUrl": "/en/user/connections.html#bluetooth-ble" - },"538": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/en/user/connections.html#usb-serial", - - "relUrl": "/en/user/connections.html#usb-serial" - },"539": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/en/user/connections.html#tcpip-network", - - "relUrl": "/en/user/connections.html#tcpip-network" - },"540": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/en/user/connections.html#reconnection-behavior", - - "relUrl": "/en/user/connections.html#reconnection-behavior" - },"541": { - "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" - },"542": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"543": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html", - - "relUrl": "/hu-rHU/user/connections.html" - },"544": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Leírás | . | 🟢 | Csatlakoztatva | Active radio link established | . | 🟡 | Csatlakozás… | Handshake in progress | . | 🔴 | Szétkapcsolva | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#bluetooth-ble", - - "relUrl": "/hu-rHU/user/connections.html#bluetooth-ble" - },"545": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#usb-serial", - - "relUrl": "/hu-rHU/user/connections.html#usb-serial" - },"546": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#tcpip-network", - - "relUrl": "/hu-rHU/user/connections.html#tcpip-network" - },"547": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#reconnection-behavior", - - "relUrl": "/hu-rHU/user/connections.html#reconnection-behavior" - },"548": { - "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" - },"549": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"550": { - "doc": "Връзки", - "title": "Връзки", - "content": "Meshtastic поддържа множество транспортни методи за за комуникация между вашия телефон/настолен компютър и радио възел. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html", - - "relUrl": "/bg-rBG/user/connections.html" - },"551": { - "doc": "Връзки", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy е методът за свързване по подразбиране и най-често срещаният в Android. Сдвояване на устройство . | Уверете се, че вашето радио Meshtastic е включено и е в режим на сдвояване. | Отворете приложението и отидете в раздела Свързване. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Изберете вашето устройство от списъка. | Приемете подканата за Bluetooth сдвояване, ако се покаже. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Състояние на връзката . | Икона | Състояние | Описание | . | 🟢 | Свързано | Установена активна радиовръзка | . | 🟡 | Свързване | Ръкостискането е в ход | . | 🔴 | Прекъсната връзка | Няма активна връзка | . | ⚪ | Не е конфигурирано | Няма избрано устройство | . При свързване, индикатора за състояние показва текущото състояние на връзката: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#bluetooth-ble", - - "relUrl": "/bg-rBG/user/connections.html#bluetooth-ble" - },"552": { - "doc": "Връзки", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Настройка . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#usb-serial", - - "relUrl": "/bg-rBG/user/connections.html#usb-serial" - },"553": { - "doc": "Връзки", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Свързване през мрежата . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#tcpip-network", - - "relUrl": "/bg-rBG/user/connections.html#tcpip-network" - },"554": { - "doc": "Връзки", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#reconnection-behavior", - - "relUrl": "/bg-rBG/user/connections.html#reconnection-behavior" - },"555": { - "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" - },"556": { - "doc": "Връзки", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"557": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html", - - "relUrl": "/sl-rSI/user/connections.html" - },"558": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Opis | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Prekinjeno | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#bluetooth-ble", - - "relUrl": "/sl-rSI/user/connections.html#bluetooth-ble" - },"559": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#usb-serial", - - "relUrl": "/sl-rSI/user/connections.html#usb-serial" - },"560": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#tcpip-network", - - "relUrl": "/sl-rSI/user/connections.html#tcpip-network" - },"561": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#reconnection-behavior", - - "relUrl": "/sl-rSI/user/connections.html#reconnection-behavior" - },"562": { - "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" - },"563": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"564": { - "doc": "Ligações", - "title": "Ligações", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html", - - "relUrl": "/pt-rPT/user/connections.html" - },"565": { - "doc": "Ligações", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descrição | . | 🟢 | Ligado | Active radio link established | . | 🟡 | A ligar | Handshake in progress | . | 🔴 | Desconectado | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#bluetooth-ble", - - "relUrl": "/pt-rPT/user/connections.html#bluetooth-ble" - },"566": { - "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 via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#usb-serial", - - "relUrl": "/pt-rPT/user/connections.html#usb-serial" - },"567": { - "doc": "Ligações", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#tcpip-network", - - "relUrl": "/pt-rPT/user/connections.html#tcpip-network" - },"568": { - "doc": "Ligações", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#reconnection-behavior", - - "relUrl": "/pt-rPT/user/connections.html#reconnection-behavior" - },"569": { - "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" - },"570": { - "doc": "Ligações", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"571": { + "relUrl": "/ca-rES/user/connections.html#related-topics" + },"438": { "doc": "Connections", "title": "Connections", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", "url": "/Meshtastic-Android/main/be-rBY/user/connections.html", "relUrl": "/be-rBY/user/connections.html" - },"572": { + },"439": { "doc": "Connections", "title": "Bluetooth (BLE)", "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Апісанне | . | 🟢 | Злучаны | Active radio link established | . | 🟡 | Злучаемся | Handshake in progress | . | 🔴 | Адлучана | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", "url": "/Meshtastic-Android/main/be-rBY/user/connections.html#bluetooth-ble", "relUrl": "/be-rBY/user/connections.html#bluetooth-ble" - },"573": { + },"440": { "doc": "Connections", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", "url": "/Meshtastic-Android/main/be-rBY/user/connections.html#usb-serial", "relUrl": "/be-rBY/user/connections.html#usb-serial" - },"574": { + },"441": { "doc": "Connections", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", "url": "/Meshtastic-Android/main/be-rBY/user/connections.html#tcpip-network", "relUrl": "/be-rBY/user/connections.html#tcpip-network" - },"575": { + },"442": { "doc": "Connections", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", "url": "/Meshtastic-Android/main/be-rBY/user/connections.html#reconnection-behavior", "relUrl": "/be-rBY/user/connections.html#reconnection-behavior" - },"576": { + },"443": { "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" - },"577": { + },"444": { "doc": "Connections", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"578": { + },"445": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html", + + "relUrl": "/uk-rUA/user/connections.html" + },"446": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Опис | . | 🟢 | Під’єднано | Active radio link established | . | 🟡 | Під’єднання | Handshake in progress | . | 🔴 | Відключено | No active connection | . | ⚪ | Not configured | Не вибраний пристрій | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#bluetooth-ble", + + "relUrl": "/uk-rUA/user/connections.html#bluetooth-ble" + },"447": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#usb-serial", + + "relUrl": "/uk-rUA/user/connections.html#usb-serial" + },"448": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#tcpip-network", + + "relUrl": "/uk-rUA/user/connections.html#tcpip-network" + },"449": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#reconnection-behavior", + + "relUrl": "/uk-rUA/user/connections.html#reconnection-behavior" + },"450": { + "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" + },"451": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"452": { + "doc": "连接数", + "title": "连接数", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html", + + "relUrl": "/zh-rCN/user/connections.html" + },"453": { + "doc": "连接数", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | 图标 | State | 说明 | . | 🟢 | 已连接 | Active radio link established | . | 🟡 | 正在连接 | Handshake in progress | . | 🔴 | 已断开连接 | No active connection | . | ⚪ | Not configured | 未选择设备 | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#bluetooth-ble", + + "relUrl": "/zh-rCN/user/connections.html#bluetooth-ble" + },"454": { + "doc": "连接数", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#usb-serial", + + "relUrl": "/zh-rCN/user/connections.html#usb-serial" + },"455": { + "doc": "连接数", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#tcpip-network", + + "relUrl": "/zh-rCN/user/connections.html#tcpip-network" + },"456": { + "doc": "连接数", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#reconnection-behavior", + + "relUrl": "/zh-rCN/user/connections.html#reconnection-behavior" + },"457": { + "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" + },"458": { + "doc": "连接数", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"459": { + "doc": "Връзки", + "title": "Връзки", + "content": "Meshtastic поддържа множество транспортни методи за за комуникация между вашия телефон/настолен компютър и радио възел. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html", + + "relUrl": "/bg-rBG/user/connections.html" + },"460": { + "doc": "Връзки", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy е методът за свързване по подразбиране и най-често срещаният в Android. Сдвояване на устройство . | Уверете се, че вашето радио Meshtastic е включено и е в режим на сдвояване. | Отворете приложението и отидете в раздела Свързване. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Изберете вашето устройство от списъка. | Приемете подканата за Bluetooth сдвояване, ако се покаже. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Състояние на връзката . | Икона | Състояние | Описание | . | 🟢 | Свързано | Установена активна радиовръзка | . | 🟡 | Свързване | Ръкостискането е в ход | . | 🔴 | Прекъсната връзка | Няма активна връзка | . | ⚪ | Не е конфигурирано | Няма избрано устройство | . При свързване, индикатора за състояние показва текущото състояние на връзката: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#bluetooth-ble", + + "relUrl": "/bg-rBG/user/connections.html#bluetooth-ble" + },"461": { + "doc": "Връзки", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Настройка . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#usb-serial", + + "relUrl": "/bg-rBG/user/connections.html#usb-serial" + },"462": { + "doc": "Връзки", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Свързване през мрежата . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#tcpip-network", + + "relUrl": "/bg-rBG/user/connections.html#tcpip-network" + },"463": { + "doc": "Връзки", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#reconnection-behavior", + + "relUrl": "/bg-rBG/user/connections.html#reconnection-behavior" + },"464": { + "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" + },"465": { + "doc": "Връзки", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"466": { + "doc": "連線", + "title": "連線", + "content": "Meshtastic 支援多種傳輸方式，以便您的手機或電腦與無線電節點進行通訊。 . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html", + + "relUrl": "/zh-rTW/user/connections.html" + },"467": { + "doc": "連線", + "title": "藍牙（BLE）", + "content": "藍牙低功耗是 Android 上預設且最常見的連線方式。 . 配對裝置 . | 請確認您的 Meshtastic 無線電裝置已開機，並進入配對模式。 | 開啟應用程式，並前往「連線」頁籤。 | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | 從清單中選取您的裝置。 | 若出現藍牙配對提示，請點選接受。 | . 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): . 💡 提示：若裝置未顯示，請確認已授予藍牙與位置權限，且該無線電裝置尚未連接至其他裝置。 . 連線狀態 . | 圖示 | 狀態 | 描述說明 | . | 🟢 | 已連線 | 無線電連線已建立 | . | 🟡 | 正在連線 | 交握進行中 | . | 🔴 | 已中斷連線 | 無作用中連線 | . | ⚪ | 尚未設定 | 未選擇裝置 | . 連線過程中，狀態指示器會顯示目前的連線狀態： . 若未找到任何裝置，應用程式將顯示空白畫面並提供操作說明： . 藍牙疑難排解 . | 找不到裝置：請關閉再開啟藍牙，並確認已啟用位置服務。 | 連線中斷：請靠近無線電裝置，並檢查是否有訊號干擾。 | 配對遭拒：請至 Android 藍牙設定中移除該裝置後重新配對。 | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#%E8%97%8D%E7%89%99ble", + + "relUrl": "/zh-rTW/user/connections.html#藍牙ble" + },"468": { + "doc": "連線", + "title": "USB 序列埠", + "content": "USB 連線提供有線替代方案，適用於桌上型電腦或藍牙無法使用的情況。 . 設定 . | 請使用 USB 傳輸線將無線電裝置連接至您的裝置。 | 應用程式將提示要求 USB 權限——請點選「允許」。 | 連線將自動建立。 | . ⚠️ 注意：USB 連線需要 Android 裝置支援 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-序列埠" + },"469": { + "doc": "連線", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. 何時使用 TCP . | 無線電裝置與裝置位於同一區域網路 | 使用模擬無線電裝置進行測試 | 藍牙訊號受干擾的環境 | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#tcpip-network", + + "relUrl": "/zh-rTW/user/connections.html#tcpip-network" + },"470": { + "doc": "連線", + "title": "重新連線行為", + "content": "應用程式啟動時將自動重新連接至上次選取的裝置。 您可隨時在連線畫面切換傳輸方式。 . 若要中斷連線，請點選連線畫面上的中斷連線按鈕： . ", + "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#重新連線行為" + },"471": { + "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#桌面版連線" + },"472": { + "doc": "連線", + "title": "相關主題", + "content": ". | 〔快速入門〕(onboarding) — 首次啟動的設定與權限 | 〔設定 — 無線電與使用者〕(settings-radio-user) — 藍牙與網路設定 | 〔桌面版應用程式〕(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#相關主題" + },"473": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html", + + "relUrl": "/sr-rLatn/user/connections.html" + },"474": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Иконица | State | Опис | . | 🟢 | Блутут повезан | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Raskačeno | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#bluetooth-ble", + + "relUrl": "/sr-rLatn/user/connections.html#bluetooth-ble" + },"475": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#usb-serial", + + "relUrl": "/sr-rLatn/user/connections.html#usb-serial" + },"476": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#tcpip-network", + + "relUrl": "/sr-rLatn/user/connections.html#tcpip-network" + },"477": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#reconnection-behavior", + + "relUrl": "/sr-rLatn/user/connections.html#reconnection-behavior" + },"478": { + "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" + },"479": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"480": { + "doc": "Připojení", + "title": "Připojení", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html", + + "relUrl": "/cs-rCZ/user/connections.html" + },"481": { + "doc": "Připojení", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Popis | . | 🟢 | Připojeno | Active radio link established | . | 🟡 | Připojování | Handshake in progress | . | 🔴 | Odpojeno | No active connection | . | ⚪ | Not configured | Není vybráno žádné zařízení | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#bluetooth-ble", + + "relUrl": "/cs-rCZ/user/connections.html#bluetooth-ble" + },"482": { + "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 via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#usb-serial", + + "relUrl": "/cs-rCZ/user/connections.html#usb-serial" + },"483": { + "doc": "Připojení", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#tcpip-network", + + "relUrl": "/cs-rCZ/user/connections.html#tcpip-network" + },"484": { + "doc": "Připojení", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#reconnection-behavior", + + "relUrl": "/cs-rCZ/user/connections.html#reconnection-behavior" + },"485": { + "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" + },"486": { + "doc": "Připojení", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"487": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/en/user/connections.html", + + "relUrl": "/en/user/connections.html" + },"488": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Description | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Disconnected | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/en/user/connections.html#bluetooth-ble", + + "relUrl": "/en/user/connections.html#bluetooth-ble" + },"489": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/en/user/connections.html#usb-serial", + + "relUrl": "/en/user/connections.html#usb-serial" + },"490": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/en/user/connections.html#tcpip-network", + + "relUrl": "/en/user/connections.html#tcpip-network" + },"491": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/en/user/connections.html#reconnection-behavior", + + "relUrl": "/en/user/connections.html#reconnection-behavior" + },"492": { + "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" + },"493": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"494": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html", + + "relUrl": "/sl-rSI/user/connections.html" + },"495": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Opis | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Prekinjeno | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#bluetooth-ble", + + "relUrl": "/sl-rSI/user/connections.html#bluetooth-ble" + },"496": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#usb-serial", + + "relUrl": "/sl-rSI/user/connections.html#usb-serial" + },"497": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#tcpip-network", + + "relUrl": "/sl-rSI/user/connections.html#tcpip-network" + },"498": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#reconnection-behavior", + + "relUrl": "/sl-rSI/user/connections.html#reconnection-behavior" + },"499": { + "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" + },"500": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"501": { + "doc": "Connessioni", + "title": "Connessioni", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/it-rIT/user/connections.html", + + "relUrl": "/it-rIT/user/connections.html" + },"502": { + "doc": "Connessioni", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descrizione | . | 🟢 | Connesso | Active radio link established | . | 🟡 | Connessione in corso | Handshake in progress | . | 🔴 | Disconnesso | No active connection | . | ⚪ | Not configured | Nessun dispositivo selezionato | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#bluetooth-ble", + + "relUrl": "/it-rIT/user/connections.html#bluetooth-ble" + },"503": { + "doc": "Connessioni", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Configurazione . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#usb-serial", + + "relUrl": "/it-rIT/user/connections.html#usb-serial" + },"504": { + "doc": "Connessioni", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#tcpip-network", + + "relUrl": "/it-rIT/user/connections.html#tcpip-network" + },"505": { + "doc": "Connessioni", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#reconnection-behavior", + + "relUrl": "/it-rIT/user/connections.html#reconnection-behavior" + },"506": { + "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" + },"507": { + "doc": "Connessioni", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"508": { "doc": "Conexões", "title": "Conexões", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html", "relUrl": "/pt-rBR/user/connections.html" - },"579": { + },"509": { "doc": "Conexões", "title": "Bluetooth (BLE)", "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descrição | . | 🟢 | Conectado | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Desconectado | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html#bluetooth-ble", "relUrl": "/pt-rBR/user/connections.html#bluetooth-ble" - },"580": { + },"510": { "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 via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html#usb-serial", "relUrl": "/pt-rBR/user/connections.html#usb-serial" - },"581": { + },"511": { "doc": "Conexões", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html#tcpip-network", "relUrl": "/pt-rBR/user/connections.html#tcpip-network" - },"582": { + },"512": { "doc": "Conexões", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html#reconnection-behavior", "relUrl": "/pt-rBR/user/connections.html#reconnection-behavior" - },"583": { + },"513": { "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" - },"584": { + },"514": { "doc": "Conexões", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"585": { + },"515": { "doc": "Connections", "title": "Connections", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/el-rGR/user/connections.html", + "url": "/Meshtastic-Android/main/is-rIS/user/connections.html", - "relUrl": "/el-rGR/user/connections.html" - },"586": { + "relUrl": "/is-rIS/user/connections.html" + },"516": { "doc": "Connections", "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Περιγραφή | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Αποσυνδεδεμένο | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#bluetooth-ble", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Lýsing | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Aftengd | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#bluetooth-ble", - "relUrl": "/el-rGR/user/connections.html#bluetooth-ble" - },"587": { + "relUrl": "/is-rIS/user/connections.html#bluetooth-ble" + },"517": { "doc": "Connections", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#usb-serial", + "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#usb-serial", - "relUrl": "/el-rGR/user/connections.html#usb-serial" - },"588": { + "relUrl": "/is-rIS/user/connections.html#usb-serial" + },"518": { "doc": "Connections", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#tcpip-network", + "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#tcpip-network", - "relUrl": "/el-rGR/user/connections.html#tcpip-network" - },"589": { + "relUrl": "/is-rIS/user/connections.html#tcpip-network" + },"519": { "doc": "Connections", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#reconnection-behavior", + "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#reconnection-behavior", - "relUrl": "/el-rGR/user/connections.html#reconnection-behavior" - },"590": { + "relUrl": "/is-rIS/user/connections.html#reconnection-behavior" + },"520": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#desktop-connections", - "relUrl": "/el-rGR/user/connections.html#desktop-connections" - },"591": { + "relUrl": "/is-rIS/user/connections.html#desktop-connections" + },"521": { "doc": "Connections", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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", + "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#related-topics", - "relUrl": "/el-rGR/user/connections.html#related-topics" - },"592": { - "doc": "Conexiones", - "title": "Conexiones", + "relUrl": "/is-rIS/user/connections.html#related-topics" + },"522": { + "doc": "Connexions", + "title": "Connexions", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/es-rES/user/connections.html", + "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html", - "relUrl": "/es-rES/user/connections.html" - },"593": { - "doc": "Conexiones", + "relUrl": "/fr-rFR/user/connections.html" + },"523": { + "doc": "Connexions", "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descripción | . | 🟢 | Conectado | Active radio link established | . | 🟡 | Conectando | Handshake in progress | . | 🔴 | Desconectado | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/es-rES/user/connections.html#bluetooth-ble", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Description | . | 🟢 | Connecté | Active radio link established | . | 🟡 | Connexion en cours | Handshake in progress | . | 🔴 | Déconnecté | No active connection | . | ⚪ | Not configured | Aucun appareil sélectionné | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#bluetooth-ble", - "relUrl": "/es-rES/user/connections.html#bluetooth-ble" - },"594": { - "doc": "Conexiones", + "relUrl": "/fr-rFR/user/connections.html#bluetooth-ble" + },"524": { + "doc": "Connexions", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/es-rES/user/connections.html#usb-serial", + "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#usb-serial", - "relUrl": "/es-rES/user/connections.html#usb-serial" - },"595": { - "doc": "Conexiones", + "relUrl": "/fr-rFR/user/connections.html#usb-serial" + },"525": { + "doc": "Connexions", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/es-rES/user/connections.html#tcpip-network", + "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#tcpip-network", - "relUrl": "/es-rES/user/connections.html#tcpip-network" - },"596": { - "doc": "Conexiones", + "relUrl": "/fr-rFR/user/connections.html#tcpip-network" + },"526": { + "doc": "Connexions", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/es-rES/user/connections.html#reconnection-behavior", + "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#reconnection-behavior", - "relUrl": "/es-rES/user/connections.html#reconnection-behavior" - },"597": { - "doc": "Conexiones", + "relUrl": "/fr-rFR/user/connections.html#reconnection-behavior" + },"527": { + "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/es-rES/user/connections.html#desktop-connections", + "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#desktop-connections", - "relUrl": "/es-rES/user/connections.html#desktop-connections" - },"598": { - "doc": "Conexiones", + "relUrl": "/fr-rFR/user/connections.html#desktop-connections" + },"528": { + "doc": "Connexions", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#related-topics", - "relUrl": "/es-rES/user/connections.html#related-topics" - },"599": { - "doc": "Bağlantılar", - "title": "Bağlantılar", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html", - - "relUrl": "/tr-rTR/user/connections.html" - },"600": { - "doc": "Bağlantılar", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Açıklaması | . | 🟢 | Bağlandı | Active radio link established | . | 🟡 | Bağlanıyor | Handshake in progress | . | 🔴 | Bağlantı kesildi | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#bluetooth-ble", - - "relUrl": "/tr-rTR/user/connections.html#bluetooth-ble" - },"601": { - "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 via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#usb-serial", - - "relUrl": "/tr-rTR/user/connections.html#usb-serial" - },"602": { - "doc": "Bağlantılar", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#tcpip-network", - - "relUrl": "/tr-rTR/user/connections.html#tcpip-network" - },"603": { - "doc": "Bağlantılar", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#reconnection-behavior", - - "relUrl": "/tr-rTR/user/connections.html#reconnection-behavior" - },"604": { - "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" - },"605": { - "doc": "Bağlantılar", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"606": { + "relUrl": "/fr-rFR/user/connections.html#related-topics" + },"529": { "doc": "Connections", "title": "Connections", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/no-rNO/user/connections.html", + "url": "/Meshtastic-Android/main/srp/user/connections.html", - "relUrl": "/no-rNO/user/connections.html" - },"607": { + "relUrl": "/srp/user/connections.html" + },"530": { "doc": "Connections", "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Beskrivelse | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Frakoblet | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#bluetooth-ble", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Иконица | State | Опис | . | 🟢 | Блутут повезан | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Раскачено | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/srp/user/connections.html#bluetooth-ble", - "relUrl": "/no-rNO/user/connections.html#bluetooth-ble" - },"608": { + "relUrl": "/srp/user/connections.html#bluetooth-ble" + },"531": { "doc": "Connections", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#usb-serial", + "url": "/Meshtastic-Android/main/srp/user/connections.html#usb-serial", - "relUrl": "/no-rNO/user/connections.html#usb-serial" - },"609": { + "relUrl": "/srp/user/connections.html#usb-serial" + },"532": { "doc": "Connections", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#tcpip-network", + "url": "/Meshtastic-Android/main/srp/user/connections.html#tcpip-network", - "relUrl": "/no-rNO/user/connections.html#tcpip-network" - },"610": { + "relUrl": "/srp/user/connections.html#tcpip-network" + },"533": { "doc": "Connections", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#reconnection-behavior", + "url": "/Meshtastic-Android/main/srp/user/connections.html#reconnection-behavior", - "relUrl": "/no-rNO/user/connections.html#reconnection-behavior" - },"611": { + "relUrl": "/srp/user/connections.html#reconnection-behavior" + },"534": { "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", + "url": "/Meshtastic-Android/main/srp/user/connections.html#desktop-connections", - "relUrl": "/no-rNO/user/connections.html#desktop-connections" - },"612": { + "relUrl": "/srp/user/connections.html#desktop-connections" + },"535": { "doc": "Connections", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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", + "url": "/Meshtastic-Android/main/srp/user/connections.html#related-topics", - "relUrl": "/no-rNO/user/connections.html#related-topics" - },"613": { + "relUrl": "/srp/user/connections.html#related-topics" + },"536": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html", + + "relUrl": "/sk-rSK/user/connections.html" + },"537": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Popis | . | 🟢 | Pripojený | Active radio link established | . | 🟡 | Prebieha pripájanie | Handshake in progress | . | 🔴 | Odpojené | No active connection | . | ⚪ | Not configured | Nebolo vybrané žiadne zariadenie | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#bluetooth-ble", + + "relUrl": "/sk-rSK/user/connections.html#bluetooth-ble" + },"538": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#usb-serial", + + "relUrl": "/sk-rSK/user/connections.html#usb-serial" + },"539": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#tcpip-network", + + "relUrl": "/sk-rSK/user/connections.html#tcpip-network" + },"540": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#reconnection-behavior", + + "relUrl": "/sk-rSK/user/connections.html#reconnection-behavior" + },"541": { + "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" + },"542": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"543": { + "doc": "Yhteydet", + "title": "Yhteydet", + "content": "Meshtastic tukee useita siirtotapoja puhelimen/työpöydän ja radion välillä viestimiseen. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html", + + "relUrl": "/fi-rFI/user/connections.html" + },"544": { + "doc": "Yhteydet", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy on oletus ja yleisin yhteystapa Androidilla. Laitteen pariliitos . | Varmista, että Meshtastic-radio on päällä ja paritustilassa. | Avaa sovellus ja siirry Yhdistä-välilehdelle. | Napauta Hae bluetooth-laitteita — lähellä olevat Meshtastic-radiot ilmestyvät näkyville. | Valitse laitteesi listasta. | Hyväksy Bluetooth-pariliitospyyntö, jos se tulee näkyviin. | . 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 laitteesi ei näy, varmista että Bluetooth ja sijaintiluvat on myönnetty ja että radio ei ole jo yhdistettynä toiseen laitteeseen. Yhteyden tila . | Ikoni | Tila | Kuvaus | . | 🟢 | Yhdistetty | Aktiivinen radiolinkki muodostettu | . | 🟡 | Yhdistetään | Yhteyden muodostus käynnissä | . | 🔴 | Ei yhdistetty | Ei aktiivista yhteyttä | . | ⚪ | Ei määritetty | Ei laitetta valittuna | . Yhdistettäessä tilailmaisin näyttää nykyisen yhteyden tilan: . Jos laitteita ei löydy, sovellus näyttää tyhjän näkymän ohjeiden kanssa: . Bluetoothin vianmääritys . | Laitetta ei löydy: Kytke Bluetooth pois/päälle ja varmista, että sijainti on käytössä. | Yhteys katkeaa: Siirry lähemmäs radiota ja tarkista mahdolliset häiriöt. | Paritus hylätty: Poista laite Androidin Bluetooth-asetuksista ja yritä uudelleen. | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#bluetooth-ble", + + "relUrl": "/fi-rFI/user/connections.html#bluetooth-ble" + },"545": { + "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 . | Yhdistä radio USB-kaapelilla laitteeseesi. | Sovellus pyytää USB-oikeuksia — paina Salli. | Yhteys muodostetaan automaattisesti. | . ⚠️ Huom: USB-yhteydet vaativat OTG-tuen Android-laitteissa. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#usb-sarjaporttiyhteys", + + "relUrl": "/fi-rFI/user/connections.html#usb-sarjaporttiyhteys" + },"546": { + "doc": "Yhteydet", + "title": "TCP/IP (Verkko)", + "content": "Jotkin Meshtastic-radiot tukevat WiFi tai Ethernet-yhteyttä, mikä mahdollistaa TCP-pohjaiset yhteydet lähiverkkosi kautta. Liitä radio ensin verkkoon käyttämällä radion omia WiFi-asetuksia (laiteohjelmiston verkkokäyttöliittymän tai muun yhteystavan kautta) — yhdistä siihen sitten sovelluksesta. Yhdistäminen verkon kautta . | Varmista, että radio on samassa lähiverkossa kuin puhelimesi tai tietokoneesi. | Valitse yhdistä-näytössä yhteysvalitsimesta Verkko. | 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 tallennetaan Viimeisimmät verkkolaitteet -osioon nopeaa uudelleenyhdistämistä varten (poista pitämällä painettuna). | . 💡 Vinkki: Verkkolaitteiden haku käyttää mDNS:ää, joka toimii vain, kun molemmat laitteet ovat samassa aliverkossa. Android 17:ssä ja uudemmissa versioissa sovellus tarvitsee lähiverkon käyttöoikeuden laitteiden hakuun. Jos haku ei löydä mitään, lisää laite manuaalisesti IP-osoitteella. Milloin TCP-yhteyttä kannattaa käyttää . | Radio on samassa lähiverkossa | Testaus simuloidulla radiolla | Ympäristöt, joissa Bluetoothissa on häiriöongelmia | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#tcpip-verkko", + + "relUrl": "/fi-rFI/user/connections.html#tcpip-verkko" + },"547": { + "doc": "Yhteydet", + "title": "Uudelleenyhdistämisen toiminta", + "content": "Sovellus yhdistyy käynnistyksen yhteydessä viimeksi valittuun laitteeseen. Voit vaihtaa yhteystapaa Yhdistä-näkymästä milloin tahansa. Yhteyden katkaisemiseksi paina Yhdistä-näkymän katkaisupainiketta: . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#uudelleenyhdist%C3%A4misen-toiminta", + + "relUrl": "/fi-rFI/user/connections.html#uudelleenyhdistämisen-toiminta" + },"548": { + "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" + },"549": { + "doc": "Yhteydet", + "title": "Aiheeseen liittyvät aiheet", + "content": ". | Aloitus — ensikäynnistyksen käyttöönotto ja käyttöoikeudet | Asetukset — Radio & käyttäjä — Bluetooth- ja verkkoasetukset | 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" + },"550": { "doc": "Соединения", "title": "Соединения", "content": "Meshtastic поддерживает несколько способов передачи данных между вашим телефоном/компьютером и радионодой. ", "url": "/Meshtastic-Android/main/ru-rRU/user/connections.html", "relUrl": "/ru-rRU/user/connections.html" - },"614": { + },"551": { "doc": "Соединения", "title": "Bluetooth (BLE)", "content": "Bluetooth Low Energy является наиболее распространенным методом подключения на Android. Привязка устройства . | Убедитесь, что устройство Meshtastic включено и находится в режиме сопряжения. | Откройте приложение и перейдите на вкладку Подключение. | Нажми Сканировать Bluetooth-устройства — рядом появятся радиостанции Meshtastic. | Выберите ваше устройство из списка. | Примите запрос на соединение Bluetooth, если показано. | . Используйте селектор транспорта — ряд сегментированных кнопок под карточкой подключения — для переключения между транспортами Bluetooth, Network и USB (одновременно активен только один): . 💡 Подсказка: Если ваше радио Meshtastic не отображается, проверьте, предоставлены ли разрешения на Bluetooth и геолокацию, а также не подключено ли ваше радио к другому устройству. Статус подключения . | Иконка | Состояние | Описание | . | 🟢 | Подключено | Подключение активно | . | 🟡 | Подключение | Выполняется рукопожатие | . | 🔴 | Отключено | Нет активного соединения | . | ⚪ | Не настроено | Устройство не выбрано | . При подключении индикатор состояния показывает текущее состояние соединения: . Если устройства не найдены, приложение показывает пустое состояние с инструкциями: . Устранение неполадок Bluetooth . | Устройство не найдено: Выключи и снова включи Bluetooth, убедись, что включена служба определения местоположения. | Потеря связи: Подойди ближе к ноде; проверь наличие помех. | Сопряжение отклонено: Забыть устройство в настройках Bluetooth на Android и повторить попытку. | . ", "url": "/Meshtastic-Android/main/ru-rRU/user/connections.html#bluetooth-ble", "relUrl": "/ru-rRU/user/connections.html#bluetooth-ble" - },"615": { + },"552": { "doc": "Соединения", "title": "Последовательный USB", "content": "Подключения через USB предоставляют проводную альтернативу, полезную для настольных компьютеров или когда Bluetooth недоступен. Настройка . | Подключи свою ноду к устройству с помощью USB-кабеля. | Приложение запросит разрешение на доступ к USB — нажми Разрешить. | Соединение устанавливается автоматически. | . ⚠️ Примечание: Для подключения USB требуется поддержка OTG на устройствах Android. ", "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" - },"616": { + },"553": { "doc": "Соединения", "title": "TCP/IP (Сеть)", "content": "Некоторые радиостанции Meshtastic поддерживают подключение по WiFi/Ethernet, что позволяет устанавливать TCP-соединения через локальную сеть. Сначала подключи радиоустройство к своей сети — используя его собственные настройки Wi-Fi (через веб-интерфейс прошивки или другое подключение) — затем подключайся к нему через приложение. Подключение к сети . | Убедись, что радио подключено к той же локальной сети, что и твой телефон/компьютер. | На экране “Подключение” выберите Network в селекторе транспорта. | Выбери радиоустройство одним из двух способов: . | Сканировать сетевые устройства — включи эту опцию чтобы автоматически обнаруживать радиоустройства, которые объявляют о себе в локальной сети (mDNS / _meshtastic._tcp). Обнаруженные устройства появляются в списке; нажми на одно, чтобы подключиться. | Добавить устройство вручную… — введи IP-адрес радиостанции (или имя хоста) и порт (по умолчанию: 4403). | . | Ранее использованные сетевые адреса запоминаются в разделе Недавние сетевые устройства для быстрого повторного подключения (удерживай пальцем, чтобы удалить). | . 💡 Совет: Обнаружение сети использует mDNS, который работает только когда оба устройства находятся в одной подсети. На Android 17+ приложению нужно разрешение на локальную сеть для сканирования; если поиск ничего не находит, добавь устройство вручную по IP. Когда использовать TCP . | Радиостанция находится в той же локальной сети | Тестирование с использованием имитирования радиоприемника | Окружающая среда, где возникают помехи Bluetooth | . ", "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-сеть" - },"617": { + },"554": { "doc": "Соединения", "title": "Поведение при повторном подключении", "content": "Приложение подключается к последнему выбранному устройству при запуске. Вы можете переключать транспорт с экрана подключения в любое время. Чтобы отключиться, нажми кнопку отключения на экране подключения: . ", "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#поведение-при-повторном-подключении" - },"618": { + },"555": { "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#подключение-к-компьютеру" - },"619": { + },"556": { "doc": "Соединения", "title": "Связанные темы", "content": ". | Начало работы — настройка при первом запуске и разрешения | Настройки — Радио и пользователь — настройка Bluetooth и сети | Десктопное приложение — детали подключения, специфичные для настольных компьютеров | Поддерживаемые устройства — полный список совместимых радиоустройств на 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#связанные-темы" + },"557": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html", + + "relUrl": "/ko-rKR/user/connections.html" + },"558": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | 설명 | . | 🟢 | 연결됨 | Active radio link established | . | 🟡 | 연결 중 | Handshake in progress | . | 🔴 | 연결 끊김 | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#bluetooth-ble", + + "relUrl": "/ko-rKR/user/connections.html#bluetooth-ble" + },"559": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#usb-serial", + + "relUrl": "/ko-rKR/user/connections.html#usb-serial" + },"560": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#tcpip-network", + + "relUrl": "/ko-rKR/user/connections.html#tcpip-network" + },"561": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#reconnection-behavior", + + "relUrl": "/ko-rKR/user/connections.html#reconnection-behavior" + },"562": { + "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" + },"563": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"564": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html", + + "relUrl": "/hr-rHR/user/connections.html" + },"565": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Opis | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Odspojeno | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#bluetooth-ble", + + "relUrl": "/hr-rHR/user/connections.html#bluetooth-ble" + },"566": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#usb-serial", + + "relUrl": "/hr-rHR/user/connections.html#usb-serial" + },"567": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#tcpip-network", + + "relUrl": "/hr-rHR/user/connections.html#tcpip-network" + },"568": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#reconnection-behavior", + + "relUrl": "/hr-rHR/user/connections.html#reconnection-behavior" + },"569": { + "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" + },"570": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"571": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html", + + "relUrl": "/sq-rAL/user/connections.html" + },"572": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Përshkrimi | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | I shkëputur | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#bluetooth-ble", + + "relUrl": "/sq-rAL/user/connections.html#bluetooth-ble" + },"573": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#usb-serial", + + "relUrl": "/sq-rAL/user/connections.html#usb-serial" + },"574": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#tcpip-network", + + "relUrl": "/sq-rAL/user/connections.html#tcpip-network" + },"575": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#reconnection-behavior", + + "relUrl": "/sq-rAL/user/connections.html#reconnection-behavior" + },"576": { + "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" + },"577": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"578": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/no-rNO/user/connections.html", + + "relUrl": "/no-rNO/user/connections.html" + },"579": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Beskrivelse | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Frakoblet | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#bluetooth-ble", + + "relUrl": "/no-rNO/user/connections.html#bluetooth-ble" + },"580": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#usb-serial", + + "relUrl": "/no-rNO/user/connections.html#usb-serial" + },"581": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#tcpip-network", + + "relUrl": "/no-rNO/user/connections.html#tcpip-network" + },"582": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#reconnection-behavior", + + "relUrl": "/no-rNO/user/connections.html#reconnection-behavior" + },"583": { + "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" + },"584": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"585": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html", + + "relUrl": "/lt-rLT/user/connections.html" + },"586": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Aprašymas | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Atsijungta | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#bluetooth-ble", + + "relUrl": "/lt-rLT/user/connections.html#bluetooth-ble" + },"587": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#usb-serial", + + "relUrl": "/lt-rLT/user/connections.html#usb-serial" + },"588": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#tcpip-network", + + "relUrl": "/lt-rLT/user/connections.html#tcpip-network" + },"589": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#reconnection-behavior", + + "relUrl": "/lt-rLT/user/connections.html#reconnection-behavior" + },"590": { + "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" + },"591": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"592": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html", + + "relUrl": "/ar-rSA/user/connections.html" + },"593": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | الوصف | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | انقطع الاتصال | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#bluetooth-ble", + + "relUrl": "/ar-rSA/user/connections.html#bluetooth-ble" + },"594": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#usb-serial", + + "relUrl": "/ar-rSA/user/connections.html#usb-serial" + },"595": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#tcpip-network", + + "relUrl": "/ar-rSA/user/connections.html#tcpip-network" + },"596": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#reconnection-behavior", + + "relUrl": "/ar-rSA/user/connections.html#reconnection-behavior" + },"597": { + "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" + },"598": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"599": { + "doc": "Ligações", + "title": "Ligações", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html", + + "relUrl": "/pt-rPT/user/connections.html" + },"600": { + "doc": "Ligações", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descrição | . | 🟢 | Ligado | Active radio link established | . | 🟡 | A ligar | Handshake in progress | . | 🔴 | Desconectado | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#bluetooth-ble", + + "relUrl": "/pt-rPT/user/connections.html#bluetooth-ble" + },"601": { + "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 via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#usb-serial", + + "relUrl": "/pt-rPT/user/connections.html#usb-serial" + },"602": { + "doc": "Ligações", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#tcpip-network", + + "relUrl": "/pt-rPT/user/connections.html#tcpip-network" + },"603": { + "doc": "Ligações", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#reconnection-behavior", + + "relUrl": "/pt-rPT/user/connections.html#reconnection-behavior" + },"604": { + "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" + },"605": { + "doc": "Ligações", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"606": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html", + + "relUrl": "/iw-rIL/user/connections.html" + },"607": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | תיאור | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | מנותק | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#bluetooth-ble", + + "relUrl": "/iw-rIL/user/connections.html#bluetooth-ble" + },"608": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#usb-serial", + + "relUrl": "/iw-rIL/user/connections.html#usb-serial" + },"609": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#tcpip-network", + + "relUrl": "/iw-rIL/user/connections.html#tcpip-network" + },"610": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#reconnection-behavior", + + "relUrl": "/iw-rIL/user/connections.html#reconnection-behavior" + },"611": { + "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" + },"612": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"613": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/el-rGR/user/connections.html", + + "relUrl": "/el-rGR/user/connections.html" + },"614": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Περιγραφή | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Αποσυνδεδεμένο | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#bluetooth-ble", + + "relUrl": "/el-rGR/user/connections.html#bluetooth-ble" + },"615": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#usb-serial", + + "relUrl": "/el-rGR/user/connections.html#usb-serial" + },"616": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#tcpip-network", + + "relUrl": "/el-rGR/user/connections.html#tcpip-network" + },"617": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#reconnection-behavior", + + "relUrl": "/el-rGR/user/connections.html#reconnection-behavior" + },"618": { + "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" + },"619": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" },"620": { "doc": "Connections", "title": "Connections", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html", + "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html", - "relUrl": "/nl-rNL/user/connections.html" + "relUrl": "/ro-rRO/user/connections.html" },"621": { "doc": "Connections", "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Beschrijving | . | 🟢 | Verbonden | Active radio link established | . | 🟡 | Bezig met verbinden | Handshake in progress | . | 🔴 | Niet verbonden | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#bluetooth-ble", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descriere | . | 🟢 | Conectat | Active radio link established | . | 🟡 | Conectare | Handshake in progress | . | 🔴 | Deconectat | No active connection | . | ⚪ | Not configured | Nici un dispozitiv selectat | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#bluetooth-ble", - "relUrl": "/nl-rNL/user/connections.html#bluetooth-ble" + "relUrl": "/ro-rRO/user/connections.html#bluetooth-ble" },"622": { "doc": "Connections", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#usb-serial", + "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#usb-serial", - "relUrl": "/nl-rNL/user/connections.html#usb-serial" + "relUrl": "/ro-rRO/user/connections.html#usb-serial" },"623": { "doc": "Connections", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#tcpip-network", + "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#tcpip-network", - "relUrl": "/nl-rNL/user/connections.html#tcpip-network" + "relUrl": "/ro-rRO/user/connections.html#tcpip-network" },"624": { "doc": "Connections", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#reconnection-behavior", + "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#reconnection-behavior", - "relUrl": "/nl-rNL/user/connections.html#reconnection-behavior" + "relUrl": "/ro-rRO/user/connections.html#reconnection-behavior" },"625": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#desktop-connections", - "relUrl": "/nl-rNL/user/connections.html#desktop-connections" + "relUrl": "/ro-rRO/user/connections.html#desktop-connections" },"626": { "doc": "Connections", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#related-topics", - "relUrl": "/nl-rNL/user/connections.html#related-topics" + "relUrl": "/ro-rRO/user/connections.html#related-topics" },"627": { "doc": "Ühendus", "title": "Ühendus", @@ -4437,495 +4437,495 @@ "relUrl": "/et-rEE/user/connections.html#related-topics" },"634": { - "doc": "Connessioni", - "title": "Connessioni", + "doc": "Connections", + "title": "Connections", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/it-rIT/user/connections.html", + "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html", - "relUrl": "/it-rIT/user/connections.html" + "relUrl": "/ga-rIE/user/connections.html" },"635": { - "doc": "Connessioni", + "doc": "Connections", "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descrizione | . | 🟢 | Connesso | Active radio link established | . | 🟡 | Connessione in corso | Handshake in progress | . | 🔴 | Disconnesso | No active connection | . | ⚪ | Not configured | Nessun dispositivo selezionato | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#bluetooth-ble", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Cur síos | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Na ceangailte | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#bluetooth-ble", - "relUrl": "/it-rIT/user/connections.html#bluetooth-ble" + "relUrl": "/ga-rIE/user/connections.html#bluetooth-ble" },"636": { - "doc": "Connessioni", + "doc": "Connections", "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Configurazione . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#usb-serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#usb-serial", - "relUrl": "/it-rIT/user/connections.html#usb-serial" + "relUrl": "/ga-rIE/user/connections.html#usb-serial" },"637": { - "doc": "Connessioni", + "doc": "Connections", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#tcpip-network", + "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#tcpip-network", - "relUrl": "/it-rIT/user/connections.html#tcpip-network" + "relUrl": "/ga-rIE/user/connections.html#tcpip-network" },"638": { - "doc": "Connessioni", + "doc": "Connections", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#reconnection-behavior", + "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#reconnection-behavior", - "relUrl": "/it-rIT/user/connections.html#reconnection-behavior" + "relUrl": "/ga-rIE/user/connections.html#reconnection-behavior" },"639": { - "doc": "Connessioni", + "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/it-rIT/user/connections.html#desktop-connections", + "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#desktop-connections", - "relUrl": "/it-rIT/user/connections.html#desktop-connections" + "relUrl": "/ga-rIE/user/connections.html#desktop-connections" },"640": { - "doc": "Connessioni", + "doc": "Connections", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#related-topics", - "relUrl": "/it-rIT/user/connections.html#related-topics" + "relUrl": "/ga-rIE/user/connections.html#related-topics" },"641": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html", - - "relUrl": "/ar-rSA/user/connections.html" - },"642": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | الوصف | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | انقطع الاتصال | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#bluetooth-ble", - - "relUrl": "/ar-rSA/user/connections.html#bluetooth-ble" - },"643": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#usb-serial", - - "relUrl": "/ar-rSA/user/connections.html#usb-serial" - },"644": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#tcpip-network", - - "relUrl": "/ar-rSA/user/connections.html#tcpip-network" - },"645": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#reconnection-behavior", - - "relUrl": "/ar-rSA/user/connections.html#reconnection-behavior" - },"646": { - "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" - },"647": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"648": { - "doc": "Connections", - "title": "Connections", - "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html", - - "relUrl": "/sk-rSK/user/connections.html" - },"649": { - "doc": "Connections", - "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Popis | . | 🟢 | Pripojený | Active radio link established | . | 🟡 | Prebieha pripájanie | Handshake in progress | . | 🔴 | Odpojené | No active connection | . | ⚪ | Not configured | Nebolo vybrané žiadne zariadenie | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#bluetooth-ble", - - "relUrl": "/sk-rSK/user/connections.html#bluetooth-ble" - },"650": { - "doc": "Connections", - "title": "USB Serial", - "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#usb-serial", - - "relUrl": "/sk-rSK/user/connections.html#usb-serial" - },"651": { - "doc": "Connections", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#tcpip-network", - - "relUrl": "/sk-rSK/user/connections.html#tcpip-network" - },"652": { - "doc": "Connections", - "title": "Reconnection Behavior", - "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#reconnection-behavior", - - "relUrl": "/sk-rSK/user/connections.html#reconnection-behavior" - },"653": { - "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" - },"654": { - "doc": "Connections", - "title": "Related Topics", - "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" - },"655": { "doc": "Connections", "title": "Connections", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html", "relUrl": "/pl-rPL/user/connections.html" - },"656": { + },"642": { "doc": "Connections", "title": "Bluetooth (BLE)", "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Opis | . | 🟢 | Połączony | Active radio link established | . | 🟡 | Łączenie | Handshake in progress | . | 🔴 | Rozłączono | No active connection | . | ⚪ | Not configured | Nie wybrano urządzenia | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html#bluetooth-ble", "relUrl": "/pl-rPL/user/connections.html#bluetooth-ble" - },"657": { + },"643": { "doc": "Connections", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html#usb-serial", "relUrl": "/pl-rPL/user/connections.html#usb-serial" - },"658": { + },"644": { "doc": "Connections", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html#tcpip-network", "relUrl": "/pl-rPL/user/connections.html#tcpip-network" - },"659": { + },"645": { "doc": "Connections", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html#reconnection-behavior", "relUrl": "/pl-rPL/user/connections.html#reconnection-behavior" - },"660": { + },"646": { "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" - },"661": { + },"647": { "doc": "Connections", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"648": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html", + + "relUrl": "/nl-rNL/user/connections.html" + },"649": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Beschrijving | . | 🟢 | Verbonden | Active radio link established | . | 🟡 | Bezig met verbinden | Handshake in progress | . | 🔴 | Niet verbonden | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#bluetooth-ble", + + "relUrl": "/nl-rNL/user/connections.html#bluetooth-ble" + },"650": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#usb-serial", + + "relUrl": "/nl-rNL/user/connections.html#usb-serial" + },"651": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#tcpip-network", + + "relUrl": "/nl-rNL/user/connections.html#tcpip-network" + },"652": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#reconnection-behavior", + + "relUrl": "/nl-rNL/user/connections.html#reconnection-behavior" + },"653": { + "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" + },"654": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" + },"655": { + "doc": "Connections", + "title": "Connections", + "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html", + + "relUrl": "/sv-rSE/user/connections.html" + },"656": { + "doc": "Connections", + "title": "Bluetooth (BLE)", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Beskrivning | . | 🟢 | Ansluten | Active radio link established | . | 🟡 | Ansluter | Handshake in progress | . | 🔴 | Frånkopplad | No active connection | . | ⚪ | Not configured | Ingen enhet vald | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#bluetooth-ble", + + "relUrl": "/sv-rSE/user/connections.html#bluetooth-ble" + },"657": { + "doc": "Connections", + "title": "USB Serial", + "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#usb-serial", + + "relUrl": "/sv-rSE/user/connections.html#usb-serial" + },"658": { + "doc": "Connections", + "title": "TCP/IP (Network)", + "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#tcpip-network", + + "relUrl": "/sv-rSE/user/connections.html#tcpip-network" + },"659": { + "doc": "Connections", + "title": "Reconnection Behavior", + "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#reconnection-behavior", + + "relUrl": "/sv-rSE/user/connections.html#reconnection-behavior" + },"660": { + "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" + },"661": { + "doc": "Connections", + "title": "Related Topics", + "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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" },"662": { - "doc": "連線", - "title": "連線", - "content": "Meshtastic 支援多種傳輸方式，以便您的手機或電腦與無線電節點進行通訊。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html", + "doc": "コネクション", + "title": "コネクション", + "content": "Meshtastic は、スマートフォン／デスクトップと無線機ノード間の通信に複数の接続方式をサポートしています。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html", - "relUrl": "/zh-rTW/user/connections.html" + "relUrl": "/ja-rJP/user/connections.html" },"663": { - "doc": "連線", - "title": "藍牙（BLE）", - "content": "藍牙低功耗是 Android 上預設且最常見的連線方式。 . 配對裝置 . | 請確認您的 Meshtastic 無線電裝置已開機，並進入配對模式。 | 開啟應用程式，並前往「連線」頁籤。 | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | 從清單中選取您的裝置。 | 若出現藍牙配對提示，請點選接受。 | . 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): . 💡 提示：若裝置未顯示，請確認已授予藍牙與位置權限，且該無線電裝置尚未連接至其他裝置。 . 連線狀態 . | 圖示 | 狀態 | 描述說明 | . | 🟢 | 已連線 | 無線電連線已建立 | . | 🟡 | 正在連線 | 交握進行中 | . | 🔴 | 已中斷連線 | 無作用中連線 | . | ⚪ | 尚未設定 | 未選擇裝置 | . 連線過程中，狀態指示器會顯示目前的連線狀態： . 若未找到任何裝置，應用程式將顯示空白畫面並提供操作說明： . 藍牙疑難排解 . | 找不到裝置：請關閉再開啟藍牙，並確認已啟用位置服務。 | 連線中斷：請靠近無線電裝置，並檢查是否有訊號干擾。 | 配對遭拒：請至 Android 藍牙設定中移除該裝置後重新配對。 | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#%E8%97%8D%E7%89%99ble", + "doc": "コネクション", + "title": "Bluetooth（BLE）", + "content": "Bluetooth Low Energy は、Android で標準的かつ最も一般的な接続方法です。 . デバイスをペアリングする . | Meshtastic 無線機の電源が入っていて、ペアリングモードになっていることを確認します。 | アプリを開き、「接続」タブに移動します。 | 「Bluetooth デバイスをスキャン」をタップすると、近くの Meshtastic 無線機が表示されます。 | リストからデバイスを選択します。 | Bluetooth のペアリング確認が表示されたら承認します。 | . 接続カードの下にあるセグメント化されたボタン列（接続方式のセレクター）を使って、Bluetooth・ネットワーク・USB の接続方式を切り替えます（一度に 1 つが有効になります）： . 💡 ヒント： デバイスが表示されない場合は、Bluetooth と位置情報の権限が許可されているか、また無線機が別のデバイスにすでに接続されていないかを確認してください。 . 接続ステータス . | アイコン | 状態 | 説明 | . | 🟢 | 接続済 | 無線リンクが確立しています | . | 🟡 | 接続中 | ハンドシェイク中 | . | 🔴 | 切断 | 接続がありません | . | ⚪ | 未設定 | デバイスが選択されていません | . 接続時には、ステータスインジケーターが現在の接続状態を表示します： . デバイスが見つからない場合、アプリは操作手順とともに空の状態を表示します： . Bluetooth のトラブルシューティング . | デバイスが見つからない： Bluetooth をオフ／オンし、位置情報が有効になっていることを確認します。 | 接続が切れる： 無線機に近づき、電波干渉がないか確認します。 | ペアリングが拒否される： Android の Bluetooth 設定でデバイスの登録を解除し、やり直します。 | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html#bluetoothble", - "relUrl": "/zh-rTW/user/connections.html#藍牙ble" + "relUrl": "/ja-rJP/user/connections.html#bluetoothble" },"664": { - "doc": "連線", - "title": "USB 序列埠", - "content": "USB 連線提供有線替代方案，適用於桌上型電腦或藍牙無法使用的情況。 . 設定 . | 請使用 USB 傳輸線將無線電裝置連接至您的裝置。 | 應用程式將提示要求 USB 權限——請點選「允許」。 | 連線將自動建立。 | . ⚠️ 注意：USB 連線需要 Android 裝置支援 OTG 功能。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#usb-%E5%BA%8F%E5%88%97%E5%9F%A0", + "doc": "コネクション", + "title": "USB シリアル", + "content": "USB 接続は有線での代替手段で、デスクトップや Bluetooth が使えない場合に便利です。 . セットアップ . | USB ケーブルで無線機をデバイスに接続します。 | アプリが USB の使用許可を求めるので、「許可」をタップします。 | 接続が自動的に確立されます。 | . ⚠️ 注意： USB 接続には、Android デバイスの OTG 対応が必要です。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html#usb-%E3%82%B7%E3%83%AA%E3%82%A2%E3%83%AB", - "relUrl": "/zh-rTW/user/connections.html#usb-序列埠" + "relUrl": "/ja-rJP/user/connections.html#usb-シリアル" },"665": { - "doc": "連線", - "title": "TCP/IP (Network)", - "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. 何時使用 TCP . | 無線電裝置與裝置位於同一區域網路 | 使用模擬無線電裝置進行測試 | 藍牙訊號受干擾的環境 | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#tcpip-network", + "doc": "コネクション", + "title": "TCP/IP（ネットワーク）", + "content": "一部の Meshtastic 無線機は WiFi／Ethernet 接続に対応しており、ローカルネットワーク経由の TCP 接続が可能です。 まず、無線機自身の WiFi 設定（ファームウェアのウェブインターフェースや別の接続方法を使用）で無線機をネットワークに接続し、その後アプリから接続します。 . ネットワーク経由で接続する . | 無線機がスマートフォン／デスクトップと同じローカルネットワーク上にあることを確認します。 | 接続画面で、接続方式のセレクターから「ネットワーク」を選択します。 | 無線機は次の 2 通りの方法で選べます： . | ネットワークデバイスをスキャン：これをオンにすると、ローカルネットワーク上で自身を告知している無線機（mDNS ／ _meshtastic._tcp）を自動的に探索します。 見つかったデバイスがリストに表示されるので、タップして接続します。 | デバイスを手動で追加…：無線機の IP アドレス（またはホスト名）とポート（既定：4403）を入力します。 | . | 以前使用したネットワークアドレスは「最近のネットワークデバイス」に記憶され、すばやく再接続できます（長押しで削除できます）。 | . 💡 ヒント： ネットワーク探索は mDNS を使用するため、両方のデバイスが同じサブネット上にある場合にのみ機能します。 Android 17 以降では、スキャンにローカルネットワークの権限が必要です。探索で何も見つからない場合は、IP アドレスでデバイスを手動追加してください。 . TCP を使う場面 . | 無線機が同じローカルネットワーク上にある | シミュレートされた無線機でテストする | Bluetooth の電波干渉が問題になる環境 | . ", + "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": "/zh-rTW/user/connections.html#tcpip-network" + "relUrl": "/ja-rJP/user/connections.html#tcpipネットワーク" },"666": { - "doc": "連線", - "title": "重新連線行為", - "content": "應用程式啟動時將自動重新連接至上次選取的裝置。 您可隨時在連線畫面切換傳輸方式。 . 若要中斷連線，請點選連線畫面上的中斷連線按鈕： . ", - "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", + "doc": "コネクション", + "title": "再接続の動作", + "content": "アプリは起動時に「最後に選択したデバイス」へ再接続します。 接続方式は、接続画面からいつでも切り替えられます。 . 切断するには、接続画面の切断ボタンをタップします： . ", + "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": "/zh-rTW/user/connections.html#重新連線行為" + "relUrl": "/ja-rJP/user/connections.html#再接続の動作" },"667": { - "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", + "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": "/zh-rTW/user/connections.html#桌面版連線" + "relUrl": "/ja-rJP/user/connections.html#デスクトップでの接続" },"668": { - "doc": "連線", - "title": "相關主題", - "content": ". | 〔快速入門〕(onboarding) — 首次啟動的設定與權限 | 〔設定 — 無線電與使用者〕(settings-radio-user) — 藍牙與網路設定 | 〔桌面版應用程式〕(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", + "doc": "コネクション", + "title": "関連トピック", + "content": ". | はじめに：初回起動時のセットアップと権限 | 設定：無線機とユーザー：Bluetooth とネットワークの設定 | デスクトップアプリ：デスクトップ固有の接続に関する詳細 | 対応デバイス：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": "/zh-rTW/user/connections.html#相關主題" + "relUrl": "/ja-rJP/user/connections.html#関連トピック" },"669": { - "doc": "Připojení", - "title": "Připojení", + "doc": "Connections", + "title": "Connections", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html", + "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html", - "relUrl": "/cs-rCZ/user/connections.html" + "relUrl": "/hu-rHU/user/connections.html" },"670": { - "doc": "Připojení", + "doc": "Connections", "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Popis | . | 🟢 | Připojeno | Active radio link established | . | 🟡 | Připojování | Handshake in progress | . | 🔴 | Odpojeno | No active connection | . | ⚪ | Not configured | Není vybráno žádné zařízení | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#bluetooth-ble", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Leírás | . | 🟢 | Csatlakoztatva | Active radio link established | . | 🟡 | Csatlakozás… | Handshake in progress | . | 🔴 | Szétkapcsolva | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#bluetooth-ble", - "relUrl": "/cs-rCZ/user/connections.html#bluetooth-ble" + "relUrl": "/hu-rHU/user/connections.html#bluetooth-ble" },"671": { - "doc": "Připojení", + "doc": "Connections", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#usb-serial", + "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#usb-serial", - "relUrl": "/cs-rCZ/user/connections.html#usb-serial" + "relUrl": "/hu-rHU/user/connections.html#usb-serial" },"672": { - "doc": "Připojení", + "doc": "Connections", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#tcpip-network", + "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#tcpip-network", - "relUrl": "/cs-rCZ/user/connections.html#tcpip-network" + "relUrl": "/hu-rHU/user/connections.html#tcpip-network" },"673": { - "doc": "Připojení", + "doc": "Connections", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#reconnection-behavior", + "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#reconnection-behavior", - "relUrl": "/cs-rCZ/user/connections.html#reconnection-behavior" + "relUrl": "/hu-rHU/user/connections.html#reconnection-behavior" },"674": { - "doc": "Připojení", + "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/cs-rCZ/user/connections.html#desktop-connections", + "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#desktop-connections", - "relUrl": "/cs-rCZ/user/connections.html#desktop-connections" + "relUrl": "/hu-rHU/user/connections.html#desktop-connections" },"675": { - "doc": "Připojení", + "doc": "Connections", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#related-topics", - "relUrl": "/cs-rCZ/user/connections.html#related-topics" + "relUrl": "/hu-rHU/user/connections.html#related-topics" },"676": { - "doc": "Connexions", - "title": "Connexions", + "doc": "Connections", + "title": "Connections", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html", + "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html", - "relUrl": "/fr-rFR/user/connections.html" + "relUrl": "/ht-rHT/user/connections.html" },"677": { - "doc": "Connexions", + "doc": "Connections", "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Description | . | 🟢 | Connecté | Active radio link established | . | 🟡 | Connexion en cours | Handshake in progress | . | 🔴 | Déconnecté | No active connection | . | ⚪ | Not configured | Aucun appareil sélectionné | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#bluetooth-ble", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Deskripsyon | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Dekonekte | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#bluetooth-ble", - "relUrl": "/fr-rFR/user/connections.html#bluetooth-ble" + "relUrl": "/ht-rHT/user/connections.html#bluetooth-ble" },"678": { - "doc": "Connexions", + "doc": "Connections", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#usb-serial", + "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#usb-serial", - "relUrl": "/fr-rFR/user/connections.html#usb-serial" + "relUrl": "/ht-rHT/user/connections.html#usb-serial" },"679": { - "doc": "Connexions", + "doc": "Connections", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#tcpip-network", + "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#tcpip-network", - "relUrl": "/fr-rFR/user/connections.html#tcpip-network" + "relUrl": "/ht-rHT/user/connections.html#tcpip-network" },"680": { - "doc": "Connexions", + "doc": "Connections", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#reconnection-behavior", + "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#reconnection-behavior", - "relUrl": "/fr-rFR/user/connections.html#reconnection-behavior" + "relUrl": "/ht-rHT/user/connections.html#reconnection-behavior" },"681": { - "doc": "Connexions", + "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/fr-rFR/user/connections.html#desktop-connections", + "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#desktop-connections", - "relUrl": "/fr-rFR/user/connections.html#desktop-connections" + "relUrl": "/ht-rHT/user/connections.html#desktop-connections" },"682": { - "doc": "Connexions", + "doc": "Connections", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#related-topics", - "relUrl": "/fr-rFR/user/connections.html#related-topics" + "relUrl": "/ht-rHT/user/connections.html#related-topics" },"683": { - "doc": "连接数", - "title": "连接数", + "doc": "Connections", + "title": "Connections", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html", + "url": "/Meshtastic-Android/main/gl-rES/user/connections.html", - "relUrl": "/zh-rCN/user/connections.html" + "relUrl": "/gl-rES/user/connections.html" },"684": { - "doc": "连接数", + "doc": "Connections", "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | 图标 | State | 说明 | . | 🟢 | 已连接 | Active radio link established | . | 🟡 | 正在连接 | Handshake in progress | . | 🔴 | 已断开连接 | No active connection | . | ⚪ | Not configured | 未选择设备 | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#bluetooth-ble", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descrición | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Desconectado | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#bluetooth-ble", - "relUrl": "/zh-rCN/user/connections.html#bluetooth-ble" + "relUrl": "/gl-rES/user/connections.html#bluetooth-ble" },"685": { - "doc": "连接数", + "doc": "Connections", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#usb-serial", + "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#usb-serial", - "relUrl": "/zh-rCN/user/connections.html#usb-serial" + "relUrl": "/gl-rES/user/connections.html#usb-serial" },"686": { - "doc": "连接数", + "doc": "Connections", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#tcpip-network", + "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#tcpip-network", - "relUrl": "/zh-rCN/user/connections.html#tcpip-network" + "relUrl": "/gl-rES/user/connections.html#tcpip-network" },"687": { - "doc": "连接数", + "doc": "Connections", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#reconnection-behavior", + "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#reconnection-behavior", - "relUrl": "/zh-rCN/user/connections.html#reconnection-behavior" + "relUrl": "/gl-rES/user/connections.html#reconnection-behavior" },"688": { - "doc": "连接数", + "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/zh-rCN/user/connections.html#desktop-connections", + "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#desktop-connections", - "relUrl": "/zh-rCN/user/connections.html#desktop-connections" + "relUrl": "/gl-rES/user/connections.html#desktop-connections" },"689": { - "doc": "连接数", + "doc": "Connections", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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", + "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#related-topics", - "relUrl": "/zh-rCN/user/connections.html#related-topics" + "relUrl": "/gl-rES/user/connections.html#related-topics" },"690": { - "doc": "Connections", - "title": "Connections", + "doc": "Bağlantılar", + "title": "Bağlantılar", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/srp/user/connections.html", + "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html", - "relUrl": "/srp/user/connections.html" + "relUrl": "/tr-rTR/user/connections.html" },"691": { - "doc": "Connections", + "doc": "Bağlantılar", "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Иконица | State | Опис | . | 🟢 | Блутут повезан | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Раскачено | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/srp/user/connections.html#bluetooth-ble", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Açıklaması | . | 🟢 | Bağlandı | Active radio link established | . | 🟡 | Bağlanıyor | Handshake in progress | . | 🔴 | Bağlantı kesildi | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#bluetooth-ble", - "relUrl": "/srp/user/connections.html#bluetooth-ble" + "relUrl": "/tr-rTR/user/connections.html#bluetooth-ble" },"692": { - "doc": "Connections", + "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 via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/srp/user/connections.html#usb-serial", + "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#usb-serial", - "relUrl": "/srp/user/connections.html#usb-serial" + "relUrl": "/tr-rTR/user/connections.html#usb-serial" },"693": { - "doc": "Connections", + "doc": "Bağlantılar", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/srp/user/connections.html#tcpip-network", + "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#tcpip-network", - "relUrl": "/srp/user/connections.html#tcpip-network" + "relUrl": "/tr-rTR/user/connections.html#tcpip-network" },"694": { - "doc": "Connections", + "doc": "Bağlantılar", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/srp/user/connections.html#reconnection-behavior", + "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#reconnection-behavior", - "relUrl": "/srp/user/connections.html#reconnection-behavior" + "relUrl": "/tr-rTR/user/connections.html#reconnection-behavior" },"695": { - "doc": "Connections", + "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/srp/user/connections.html#desktop-connections", + "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#desktop-connections", - "relUrl": "/srp/user/connections.html#desktop-connections" + "relUrl": "/tr-rTR/user/connections.html#desktop-connections" },"696": { - "doc": "Connections", + "doc": "Bağlantılar", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#related-topics", - "relUrl": "/srp/user/connections.html#related-topics" + "relUrl": "/tr-rTR/user/connections.html#related-topics" },"697": { - "doc": "Connections", - "title": "Connections", + "doc": "Conexiones", + "title": "Conexiones", "content": "Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html", + "url": "/Meshtastic-Android/main/es-rES/user/connections.html", - "relUrl": "/sq-rAL/user/connections.html" + "relUrl": "/es-rES/user/connections.html" },"698": { - "doc": "Connections", + "doc": "Conexiones", "title": "Bluetooth (BLE)", - "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Përshkrimi | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | I shkëputur | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#bluetooth-ble", + "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Device . | Ensure your Meshtastic radio is powered on and in pairing mode. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your device from the list. | Accept the Bluetooth pairing prompt if shown. | . 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 device doesn’t appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device. Connection Status . | Icon | State | Descripción | . | 🟢 | Conectado | Active radio link established | . | 🟡 | Conectando | Handshake in progress | . | 🔴 | Desconectado | No active connection | . | ⚪ | Not configured | No device selected | . When connecting, a status indicator shows the current connection state: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Device not found: Toggle Bluetooth off/on, ensure location is enabled. | Connection drops: Move closer to the radio; check for interference. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | . ", + "url": "/Meshtastic-Android/main/es-rES/user/connections.html#bluetooth-ble", - "relUrl": "/sq-rAL/user/connections.html#bluetooth-ble" + "relUrl": "/es-rES/user/connections.html#bluetooth-ble" },"699": { - "doc": "Connections", + "doc": "Conexiones", "title": "USB Serial", "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio via USB cable to your device. | The app will prompt for USB permission — tap Allow. | The connection is established automatically. | . ⚠️ Note: USB connections require OTG support on Android devices. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#usb-serial", + "url": "/Meshtastic-Android/main/es-rES/user/connections.html#usb-serial", - "relUrl": "/sq-rAL/user/connections.html#usb-serial" + "relUrl": "/es-rES/user/connections.html#usb-serial" },"700": { - "doc": "Connections", + "doc": "Conexiones", "title": "TCP/IP (Network)", "content": "Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first — using the radio’s own WiFi settings (via the firmware web interface or another connection) — then connect to it from the app. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect screen, 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 (long-press to remove one). | . 💡 Tip: Network discovery uses mDNS, which only works when both devices are on the same subnet. On Android 17+ the app needs the local-network permission for scanning; if discovery finds nothing, add the device manually by IP. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#tcpip-network", + "url": "/Meshtastic-Android/main/es-rES/user/connections.html#tcpip-network", - "relUrl": "/sq-rAL/user/connections.html#tcpip-network" + "relUrl": "/es-rES/user/connections.html#tcpip-network" },"701": { - "doc": "Connections", + "doc": "Conexiones", "title": "Reconnection Behavior", "content": "The app reconnects to the last selected device on startup. You can switch transports from the Connect screen at any time. To disconnect, tap the disconnect button on the Connect screen: . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#reconnection-behavior", + "url": "/Meshtastic-Android/main/es-rES/user/connections.html#reconnection-behavior", - "relUrl": "/sq-rAL/user/connections.html#reconnection-behavior" + "relUrl": "/es-rES/user/connections.html#reconnection-behavior" },"702": { - "doc": "Connections", + "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/sq-rAL/user/connections.html#desktop-connections", + "url": "/Meshtastic-Android/main/es-rES/user/connections.html#desktop-connections", - "relUrl": "/sq-rAL/user/connections.html#desktop-connections" + "relUrl": "/es-rES/user/connections.html#desktop-connections" },"703": { - "doc": "Connections", + "doc": "Conexiones", "title": "Related Topics", "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth and network configuration | 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", + "url": "/Meshtastic-Android/main/es-rES/user/connections.html#related-topics", - "relUrl": "/sq-rAL/user/connections.html#related-topics" + "relUrl": "/es-rES/user/connections.html#related-topics" },"704": { "doc": "Contributing", "title": "Contributing", @@ -4990,1223 +4990,1223 @@ "relUrl": "/en/developer/contributing.html#getting-help" },"713": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"714": { - "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" - },"715": { - "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 device. | 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" - },"716": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"717": { - "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" - },"718": { - "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" - },"719": { - "doc": "デバッグログ", - "title": "デバッグログ", - "content": "何か不具合が起きたとき、アプリのデバッグログは、バグ報告に添付できる最も役立つものです。 Meshtastic は、アプリ内で自動的にログをキャプチャできます。収集に adb やデスクトップのツールは不要になりました。 . 「設定 → 詳細設定 → デバッグパネル」から「デバッグパネル」を開きます。 . 📎 issue を作成しますか？ ログをエクスポートし（下記参照）、github.com/meshtastic/Meshtastic-Android/issues の報告に .txt ファイルを添付してください。 問題が起きた瞬間を含むログのキャプチャは、「動かない」という報告を、開発者が実際に追跡できるものに変えます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/debug-logs.html", - - "relUrl": "/ja-rJP/user/debug-logs.html" - },"720": { - "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-つのタブ" - },"721": { - "doc": "デバッグログ", - "title": "アプリログを表示する", - "content": "「アプリログ」タブは、このアプリのみの最新のログ行を表示します。デバイス上の他のアプリのものは表示しません。 . | 検索：検索ボックスに入力すると、一致する行に絞り込めます。 | レベルフィルター：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#アプリログを表示する" - },"722": { - "doc": "デバッグログ", - "title": "エクスポート", - "content": "ダウンロードアイコンをタップすると、現在のログをファイルに保存できます。 保存先はシステムのファイル選択画面で選び、ファイルにはタイムスタンプ付きの名前（例：meshtastic_logcat_20260701_143312.txt）が付くため、繰り返しエクスポートしても互いに上書きされることはありません。 . そのファイルを GitHub の issue に添付してください。 . 🔒 プライバシー： エクスポートは、ファイルに書き込む前に、秘密鍵・管理者鍵・セッションパスキーを自動的に秘匿化します。 チャンネルの PSK は秘匿化されません。また、ログにはノード名、位置、その他の識別情報が含まれることがあります。公開して共有する前にファイルにざっと目を通し、少しでも不安があれば非公開で共有してください。 . ", - "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#エクスポート" - },"723": { - "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#デスクトップ" - },"724": { - "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#関連トピック" - },"725": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"726": { - "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" - },"727": { - "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 device. | 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" - },"728": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"729": { - "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" - },"730": { - "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" - },"731": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"732": { - "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" - },"733": { - "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 device. | 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" - },"734": { - "doc": "Дебаг логови", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"735": { - "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" - },"736": { - "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" - },"737": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"738": { - "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" - },"739": { - "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 device. | 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" - },"740": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"741": { - "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" - },"742": { - "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" - },"743": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"744": { - "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" - },"745": { - "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 device. | 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" - },"746": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"747": { - "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" - },"748": { - "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" - },"749": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"750": { - "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" - },"751": { - "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 device. | 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" - },"752": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"753": { - "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" - },"754": { - "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" - },"755": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"756": { - "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" - },"757": { - "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 device. | 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" - },"758": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"759": { - "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" - },"760": { - "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" - },"761": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"762": { - "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" - },"763": { - "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 device. | 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" - },"764": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"765": { - "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" - },"766": { - "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" - },"767": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"768": { - "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" - },"769": { - "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 device. | 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" - },"770": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"771": { - "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" - },"772": { - "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" - },"773": { - "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 — et enää tarvitse adb:tä tai työpöytätyökaluja niiden keräämiseen. Avaa Virheenjäljityspaneeli kohdasta Asetukset → Lisäasetukset → Virheenjäljityspaneeli. 💡 Ilmoitatko ongelmasta? Vie lokitiedot (katso alla) ja liitä .txt-tiedosto raporttiisi osoitteessa github.com/meshtastic/Meshtastic-Android/issues. 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" - },"774": { - "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ä" - },"775": { - "doc": "Virheenjäljityslokitiedot", - "title": "Sovelluslokitietojen tarkastelu", - "content": "Sovelluslokitiedot-välilehti näyttää viimeisimmät lokirivit vain tästä sovelluksesta — ei koskaan muista laitteesi sovelluksista. | 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" - },"776": { - "doc": "Virheenjäljityslokitiedot", - "title": "Lokien vienti", - "content": "Napauta latauskuvaketta tallentaaksesi nykyiset lokitiedot tiedostoon. Valitset tallennuspaikan järjestelmän tiedostonvalitsimessa, ja tiedosto nimetään aikaleimalla (esimerkiksi meshtastic_logcat_20260701_143312.txt), jotta aiemmat viennit eivät ylikirjoitu. Liitä tämä tiedosto GitHub-vikaraporttiisi. 🔒 Tietosuoja: Viennit peittävät automaattisesti yksityiset avaimet, ylläpitoavaimet ja istuntoavaimet ennen tiedoston kirjoittamista. Kanavien PSK-avaimia ei peitetä, ja lokit voivat sisältää myös radioiden nimiä, sijainteja ja muita tunnistetietoja. Tarkista tiedosto ennen sen julkista jakamista, ja jos olet epävarma, jaa se yksityisesti. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/debug-logs.html#lokien-vienti", - - "relUrl": "/fi-rFI/user/debug-logs.html#lokien-vienti" - },"777": { - "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ä" - },"778": { - "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" - },"779": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"780": { - "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" - },"781": { - "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 device. | 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" - },"782": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"783": { - "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" - },"784": { - "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" - },"785": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"786": { - "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" - },"787": { - "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 device. | 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" - },"788": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"789": { - "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" - },"790": { - "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" - },"791": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Möchtest du ein Problem melden? Exportiere deine Logs (siehe unten) und hänge die .txt-Datei an deinen Bericht unter github.com/meshtastic/Meshtastic-Android/issues an. 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" - },"792": { + },"714": { "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" - },"793": { + },"715": { "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 device. | 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" - },"794": { + },"716": { "doc": "Fehlersuchprotokolle", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. Sie wählen den Speicherort über die Dateiauswahl des Systems aus, und die Datei wird mit einem Zeitstempel versehen (zum Beispiel meshtastic_logcat_20260701_143312.txt), sodass sich wiederholte Exporte nicht gegenseitig überschreiben. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"795": { + },"717": { "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" - },"796": { + },"718": { "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" - },"797": { + },"719": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html", - "relUrl": "/hr-rHR/user/debug-logs.html" - },"798": { + "relUrl": "/ca-rES/user/debug-logs.html" + },"720": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html#the-two-tabs", - "relUrl": "/hr-rHR/user/debug-logs.html#the-two-tabs" - },"799": { + "relUrl": "/ca-rES/user/debug-logs.html#the-two-tabs" + },"721": { "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 device. | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html#viewing-app-logs", - "relUrl": "/hr-rHR/user/debug-logs.html#viewing-app-logs" - },"800": { + "relUrl": "/ca-rES/user/debug-logs.html#viewing-app-logs" + },"722": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html#exporting", - "relUrl": "/hr-rHR/user/debug-logs.html#exporting" - },"801": { + "relUrl": "/ca-rES/user/debug-logs.html#exporting" + },"723": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html#desktop", - "relUrl": "/hr-rHR/user/debug-logs.html#desktop" - },"802": { + "relUrl": "/ca-rES/user/debug-logs.html#desktop" + },"724": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html#related-topics", - "relUrl": "/hr-rHR/user/debug-logs.html#related-topics" - },"803": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"804": { - "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" - },"805": { - "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 device. | 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" - },"806": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"807": { - "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" - },"808": { - "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" - },"809": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"810": { - "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" - },"811": { - "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 device. | 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" - },"812": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"813": { - "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" - },"814": { - "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" - },"815": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"816": { - "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" - },"817": { - "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 device. | 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" - },"818": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"819": { - "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" - },"820": { - "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" - },"821": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"822": { - "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" - },"823": { - "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 device. | 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" - },"824": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"825": { - "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" - },"826": { - "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" - },"827": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"828": { - "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" - },"829": { - "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 device. | 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" - },"830": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"831": { - "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" - },"832": { - "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" - },"833": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"834": { - "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" - },"835": { - "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 device. | 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" - },"836": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"837": { - "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" - },"838": { - "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" - },"839": { + "relUrl": "/ca-rES/user/debug-logs.html#related-topics" + },"725": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"840": { + },"726": { "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" - },"841": { + },"727": { "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 device. | 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" - },"842": { + },"728": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"843": { + },"729": { "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" - },"844": { + },"730": { "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" - },"845": { + },"731": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"732": { + "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" + },"733": { + "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 device. | 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" + },"734": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"735": { + "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" + },"736": { + "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" + },"737": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"738": { + "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" + },"739": { + "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 device. | 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" + },"740": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"741": { + "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" + },"742": { + "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" + },"743": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"744": { + "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" + },"745": { + "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 device. | 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" + },"746": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"747": { + "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" + },"748": { + "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" + },"749": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"750": { + "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" + },"751": { + "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 device. | 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" + },"752": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"753": { + "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#桌面版" + },"754": { + "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#相關主題" + },"755": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"756": { + "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" + },"757": { + "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 device. | 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" + },"758": { + "doc": "Дебаг логови", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"759": { + "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" + },"760": { + "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" + },"761": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"762": { + "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" + },"763": { + "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 device. | 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" + },"764": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"765": { + "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" + },"766": { + "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" + },"767": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"768": { + "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" + },"769": { + "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 device. | 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" + },"770": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"771": { + "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" + },"772": { + "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" + },"773": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"774": { + "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" + },"775": { + "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 device. | 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" + },"776": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"777": { + "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" + },"778": { + "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" + },"779": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"780": { + "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" + },"781": { + "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 device. | 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" + },"782": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"783": { + "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" + },"784": { + "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" + },"785": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"846": { + },"786": { "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" - },"847": { + },"787": { "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 device. | 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" - },"848": { + },"788": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"849": { + },"789": { "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" - },"850": { + },"790": { "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" - },"851": { + },"791": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html", - "relUrl": "/el-rGR/user/debug-logs.html" - },"852": { + "relUrl": "/is-rIS/user/debug-logs.html" + },"792": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html#the-two-tabs", - "relUrl": "/el-rGR/user/debug-logs.html#the-two-tabs" - },"853": { + "relUrl": "/is-rIS/user/debug-logs.html#the-two-tabs" + },"793": { "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 device. | 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", + "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html#viewing-app-logs", - "relUrl": "/el-rGR/user/debug-logs.html#viewing-app-logs" - },"854": { + "relUrl": "/is-rIS/user/debug-logs.html#viewing-app-logs" + },"794": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/el-rGR/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html#exporting", - "relUrl": "/el-rGR/user/debug-logs.html#exporting" - },"855": { + "relUrl": "/is-rIS/user/debug-logs.html#exporting" + },"795": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html#desktop", - "relUrl": "/el-rGR/user/debug-logs.html#desktop" - },"856": { + "relUrl": "/is-rIS/user/debug-logs.html#desktop" + },"796": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html#related-topics", - "relUrl": "/el-rGR/user/debug-logs.html#related-topics" - },"857": { + "relUrl": "/is-rIS/user/debug-logs.html#related-topics" + },"797": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html", - "relUrl": "/es-rES/user/debug-logs.html" - },"858": { + "relUrl": "/fr-rFR/user/debug-logs.html" + },"798": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#the-two-tabs", - "relUrl": "/es-rES/user/debug-logs.html#the-two-tabs" - },"859": { + "relUrl": "/fr-rFR/user/debug-logs.html#the-two-tabs" + },"799": { "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 device. | 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#viewing-app-logs", - "relUrl": "/es-rES/user/debug-logs.html#viewing-app-logs" - },"860": { + "relUrl": "/fr-rFR/user/debug-logs.html#viewing-app-logs" + },"800": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#exporting", - "relUrl": "/es-rES/user/debug-logs.html#exporting" - },"861": { + "relUrl": "/fr-rFR/user/debug-logs.html#exporting" + },"801": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#desktop", - "relUrl": "/es-rES/user/debug-logs.html#desktop" - },"862": { + "relUrl": "/fr-rFR/user/debug-logs.html#desktop" + },"802": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#related-topics", - "relUrl": "/es-rES/user/debug-logs.html#related-topics" - },"863": { + "relUrl": "/fr-rFR/user/debug-logs.html#related-topics" + },"803": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"804": { + "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" + },"805": { + "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 device. | 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" + },"806": { + "doc": "Дебаг логови", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"807": { + "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" + },"808": { + "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" + },"809": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html", - "relUrl": "/tr-rTR/user/debug-logs.html" - },"864": { + "relUrl": "/sk-rSK/user/debug-logs.html" + },"810": { "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", + "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html#the-two-tabs", - "relUrl": "/tr-rTR/user/debug-logs.html#the-two-tabs" - },"865": { + "relUrl": "/sk-rSK/user/debug-logs.html#the-two-tabs" + },"811": { "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 device. | 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", + "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html#viewing-app-logs", - "relUrl": "/tr-rTR/user/debug-logs.html#viewing-app-logs" - },"866": { + "relUrl": "/sk-rSK/user/debug-logs.html#viewing-app-logs" + },"812": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html#exporting", - "relUrl": "/tr-rTR/user/debug-logs.html#exporting" - },"867": { + "relUrl": "/sk-rSK/user/debug-logs.html#exporting" + },"813": { "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", + "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html#desktop", - "relUrl": "/tr-rTR/user/debug-logs.html#desktop" - },"868": { + "relUrl": "/sk-rSK/user/debug-logs.html#desktop" + },"814": { "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", + "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html#related-topics", - "relUrl": "/tr-rTR/user/debug-logs.html#related-topics" - },"869": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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": "/sk-rSK/user/debug-logs.html#related-topics" + },"815": { + "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 — et enää tarvitse adb:tä tai työpöytätyökaluja niiden keräämiseen. Avaa Virheenjäljityspaneeli kohdasta Asetukset → Lisäasetukset → Virheenjäljityspaneeli. 💡 Ilmoitatko ongelmasta? Vie lokitiedot (katso alla) ja liitä .txt-tiedosto raporttiisi osoitteessa github.com/meshtastic/Meshtastic-Android/issues. 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": "/no-rNO/user/debug-logs.html" - },"870": { - "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": "/fi-rFI/user/debug-logs.html" + },"816": { + "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": "/no-rNO/user/debug-logs.html#the-two-tabs" - },"871": { - "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 device. | 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": "/fi-rFI/user/debug-logs.html#kaksi-välilehteä" + },"817": { + "doc": "Virheenjäljityslokitiedot", + "title": "Sovelluslokitietojen tarkastelu", + "content": "Sovelluslokitiedot-välilehti näyttää viimeisimmät lokirivit vain tästä sovelluksesta — ei koskaan muista laitteesi sovelluksista. | 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": "/no-rNO/user/debug-logs.html#viewing-app-logs" - },"872": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/no-rNO/user/debug-logs.html#exporting", + "relUrl": "/fi-rFI/user/debug-logs.html#sovelluslokitietojen-tarkastelu" + },"818": { + "doc": "Virheenjäljityslokitiedot", + "title": "Lokien vienti", + "content": "Napauta latauskuvaketta tallentaaksesi nykyiset lokitiedot tiedostoon. Valitset tallennuspaikan järjestelmän tiedostonvalitsimessa, ja tiedosto nimetään aikaleimalla (esimerkiksi meshtastic_logcat_20260701_143312.txt), jotta aiemmat viennit eivät ylikirjoitu. Liitä tämä tiedosto GitHub-vikaraporttiisi. 🔒 Tietosuoja: Viennit peittävät automaattisesti yksityiset avaimet, ylläpitoavaimet ja istuntoavaimet ennen tiedoston kirjoittamista. Kanavien PSK-avaimia ei peitetä, ja lokit voivat sisältää myös radioiden nimiä, sijainteja ja muita tunnistetietoja. Tarkista tiedosto ennen sen julkista jakamista, ja jos olet epävarma, jaa se yksityisesti. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/debug-logs.html#lokien-vienti", - "relUrl": "/no-rNO/user/debug-logs.html#exporting" - },"873": { - "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": "/fi-rFI/user/debug-logs.html#lokien-vienti" + },"819": { + "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": "/no-rNO/user/debug-logs.html#desktop" - },"874": { - "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": "/fi-rFI/user/debug-logs.html#työpöytä" + },"820": { + "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": "/no-rNO/user/debug-logs.html#related-topics" - },"875": { + "relUrl": "/fi-rFI/user/debug-logs.html#aiheeseen-liittyvät-aiheet" + },"821": { "doc": "Отладочные журналы", "title": "Отладочные журналы", "content": "Когда что-то работает неправильно, отладочные журналы приложения — это самое полезное, что вы можете приложить к отчёту об ошибке. Meshtastic может захватить их за вас, прямо из приложения — вам больше не нужен adb или какие-либо инструменты на компьютере для их сбора. Откройте Панель отладки через Настройки → Дополнительно → Панель отладки. 📎 Создаёте задачу? Экспортируйте свои журналы (см. ниже) и прикрепите файл .txt к отчёту на [github.com/meshtastic/Meshtastic-Android/issues]. Захват журнала, охватывающий момент возникновения проблемы, превращает «это не работает» в то, что разработчик действительно может отследить. ", "url": "/Meshtastic-Android/main/ru-rRU/user/debug-logs.html", "relUrl": "/ru-rRU/user/debug-logs.html" - },"876": { + },"822": { "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#две-вкладки" - },"877": { + },"823": { "doc": "Отладочные журналы", "title": "Просмотр журналов приложения", "content": "Вкладка Журналы приложения показывает самые последние строки журнала только из этого приложения — но не из других приложений на вашем устройстве. | Поиск — введите текст в поле поиска, чтобы отфильтровать строки по совпадению. | Фильтр по уровню — кнопки 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#просмотр-журналов-приложения" - },"878": { + },"824": { "doc": "Отладочные журналы", "title": "Экспорт", "content": "Нажмите на значок загрузки, чтобы сохранить текущие журналы в файл. Вы выбираете расположение через системное окно выбора файлов, а файл получает имя с меткой времени (например, meshtastic_logcat_20260701_143312.txt), поэтому повторные экспорты никогда не перезаписывают друг друга. Прикрепите этот файл к своей задаче на GitHub. 🔒 Приватность: Экспорты автоматически удаляют приватные ключи, ключи администратора и сеансовые ключи доступа перед записью в файл. Ключи каналов (PSKs) не удаляются, а журналы также могут содержать имена узлов, координаты и другие идентифицирующие данные — бегло просмотрите файл перед публикацией и, если сомневаетесь, делитесь им конфиденциально. ", "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#экспорт" - },"879": { + },"825": { "doc": "Отладочные журналы", "title": "Desktop", "content": "У компьютерного приложения нет системного logcat, поэтому вкладка Журналы приложения вместо этого показывает собственный захваченный вывод журнала приложения. Поиск, фильтрация и экспорт работают точно так же. ", "url": "/Meshtastic-Android/main/ru-rRU/user/debug-logs.html#desktop", "relUrl": "/ru-rRU/user/debug-logs.html#desktop" - },"880": { + },"826": { "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#связанные-темы" + },"827": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"828": { + "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" + },"829": { + "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 device. | 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" + },"830": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"831": { + "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" + },"832": { + "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" + },"833": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"834": { + "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" + },"835": { + "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 device. | 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" + },"836": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"837": { + "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" + },"838": { + "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" + },"839": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"840": { + "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" + },"841": { + "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 device. | 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" + },"842": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"843": { + "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" + },"844": { + "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" + },"845": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"846": { + "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" + },"847": { + "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 device. | 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" + },"848": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"849": { + "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" + },"850": { + "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" + },"851": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"852": { + "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" + },"853": { + "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 device. | 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" + },"854": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"855": { + "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" + },"856": { + "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" + },"857": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"858": { + "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" + },"859": { + "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 device. | 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" + },"860": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"861": { + "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" + },"862": { + "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" + },"863": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"864": { + "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" + },"865": { + "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 device. | 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" + },"866": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"867": { + "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" + },"868": { + "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" + },"869": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"870": { + "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" + },"871": { + "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 device. | 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" + },"872": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"873": { + "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" + },"874": { + "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" + },"875": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"876": { + "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" + },"877": { + "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 device. | 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" + },"878": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"879": { + "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" + },"880": { + "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" },"881": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html", - "relUrl": "/nl-rNL/user/debug-logs.html" + "relUrl": "/ro-rRO/user/debug-logs.html" },"882": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html#the-two-tabs", - "relUrl": "/nl-rNL/user/debug-logs.html#the-two-tabs" + "relUrl": "/ro-rRO/user/debug-logs.html#the-two-tabs" },"883": { "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 device. | 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html#viewing-app-logs", - "relUrl": "/nl-rNL/user/debug-logs.html#viewing-app-logs" + "relUrl": "/ro-rRO/user/debug-logs.html#viewing-app-logs" },"884": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html#exporting", - "relUrl": "/nl-rNL/user/debug-logs.html#exporting" + "relUrl": "/ro-rRO/user/debug-logs.html#exporting" },"885": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html#desktop", - "relUrl": "/nl-rNL/user/debug-logs.html#desktop" + "relUrl": "/ro-rRO/user/debug-logs.html#desktop" },"886": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html#related-topics", - "relUrl": "/nl-rNL/user/debug-logs.html#related-topics" + "relUrl": "/ro-rRO/user/debug-logs.html#related-topics" },"887": { "doc": "Arendaja logid", "title": "Arendaja logid", @@ -6253,2249 +6253,2249 @@ "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html", - "relUrl": "/it-rIT/user/debug-logs.html" + "relUrl": "/ga-rIE/user/debug-logs.html" },"894": { "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html#the-two-tabs", - "relUrl": "/it-rIT/user/debug-logs.html#the-two-tabs" + "relUrl": "/ga-rIE/user/debug-logs.html#the-two-tabs" },"895": { "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 device. | 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html#viewing-app-logs", - "relUrl": "/it-rIT/user/debug-logs.html#viewing-app-logs" + "relUrl": "/ga-rIE/user/debug-logs.html#viewing-app-logs" },"896": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/it-rIT/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html#exporting", - "relUrl": "/it-rIT/user/debug-logs.html#exporting" + "relUrl": "/ga-rIE/user/debug-logs.html#exporting" },"897": { "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html#desktop", - "relUrl": "/it-rIT/user/debug-logs.html#desktop" + "relUrl": "/ga-rIE/user/debug-logs.html#desktop" },"898": { "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html#related-topics", - "relUrl": "/it-rIT/user/debug-logs.html#related-topics" + "relUrl": "/ga-rIE/user/debug-logs.html#related-topics" },"899": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"900": { - "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" - },"901": { - "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 device. | 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" - },"902": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"903": { - "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" - },"904": { - "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" - },"905": { - "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"906": { - "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" - },"907": { - "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 device. | 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" - },"908": { - "doc": "Debug Logs", - "title": "Exporting", - "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"909": { - "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" - },"910": { - "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" - },"911": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" - },"912": { + },"900": { "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" - },"913": { + },"901": { "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 device. | 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" - },"914": { + },"902": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" - },"915": { + },"903": { "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" - },"916": { + },"904": { "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" - },"917": { + },"905": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html", - "relUrl": "/zh-rTW/user/debug-logs.html" - },"918": { + "relUrl": "/nl-rNL/user/debug-logs.html" + },"906": { "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", + "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#the-two-tabs", - "relUrl": "/zh-rTW/user/debug-logs.html#the-two-tabs" - },"919": { + "relUrl": "/nl-rNL/user/debug-logs.html#the-two-tabs" + },"907": { "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 device. | 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", + "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#viewing-app-logs", - "relUrl": "/zh-rTW/user/debug-logs.html#viewing-app-logs" - },"920": { + "relUrl": "/nl-rNL/user/debug-logs.html#viewing-app-logs" + },"908": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#exporting", - "relUrl": "/zh-rTW/user/debug-logs.html#exporting" - },"921": { + "relUrl": "/nl-rNL/user/debug-logs.html#exporting" + },"909": { "doc": "Debug Logs", - "title": "桌面版", + "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-rTW/user/debug-logs.html#%E6%A1%8C%E9%9D%A2%E7%89%88", + "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#desktop", - "relUrl": "/zh-rTW/user/debug-logs.html#桌面版" - },"922": { + "relUrl": "/nl-rNL/user/debug-logs.html#desktop" + },"910": { "doc": "Debug Logs", - "title": "相關主題", + "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-rTW/user/debug-logs.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C", + "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#related-topics", - "relUrl": "/zh-rTW/user/debug-logs.html#相關主題" + "relUrl": "/nl-rNL/user/debug-logs.html#related-topics" + },"911": { + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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" + },"912": { + "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" + },"913": { + "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 device. | 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" + },"914": { + "doc": "Debug Logs", + "title": "Exporting", + "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file 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" + },"915": { + "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" + },"916": { + "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" + },"917": { + "doc": "デバッグログ", + "title": "デバッグログ", + "content": "何か不具合が起きたとき、アプリのデバッグログは、バグ報告に添付できる最も役立つものです。 Meshtastic は、アプリ内で自動的にログをキャプチャできます。収集に adb やデスクトップのツールは不要になりました。 . 「設定 → 詳細設定 → デバッグパネル」から「デバッグパネル」を開きます。 . 📎 issue を作成しますか？ ログをエクスポートし（下記参照）、github.com/meshtastic/Meshtastic-Android/issues の報告に .txt ファイルを添付してください。 問題が起きた瞬間を含むログのキャプチャは、「動かない」という報告を、開発者が実際に追跡できるものに変えます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/debug-logs.html", + + "relUrl": "/ja-rJP/user/debug-logs.html" + },"918": { + "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-つのタブ" + },"919": { + "doc": "デバッグログ", + "title": "アプリログを表示する", + "content": "「アプリログ」タブは、このアプリのみの最新のログ行を表示します。デバイス上の他のアプリのものは表示しません。 . | 検索：検索ボックスに入力すると、一致する行に絞り込めます。 | レベルフィルター：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#アプリログを表示する" + },"920": { + "doc": "デバッグログ", + "title": "エクスポート", + "content": "ダウンロードアイコンをタップすると、現在のログをファイルに保存できます。 保存先はシステムのファイル選択画面で選び、ファイルにはタイムスタンプ付きの名前（例：meshtastic_logcat_20260701_143312.txt）が付くため、繰り返しエクスポートしても互いに上書きされることはありません。 . そのファイルを GitHub の issue に添付してください。 . 🔒 プライバシー： エクスポートは、ファイルに書き込む前に、秘密鍵・管理者鍵・セッションパスキーを自動的に秘匿化します。 チャンネルの PSK は秘匿化されません。また、ログにはノード名、位置、その他の識別情報が含まれることがあります。公開して共有する前にファイルにざっと目を通し、少しでも不安があれば非公開で共有してください。 . ", + "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#エクスポート" + },"921": { + "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#デスクトップ" + },"922": { + "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#関連トピック" },"923": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html", - "relUrl": "/cs-rCZ/user/debug-logs.html" + "relUrl": "/hu-rHU/user/debug-logs.html" },"924": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html#the-two-tabs", - "relUrl": "/cs-rCZ/user/debug-logs.html#the-two-tabs" + "relUrl": "/hu-rHU/user/debug-logs.html#the-two-tabs" },"925": { "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 device. | 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html#viewing-app-logs", - "relUrl": "/cs-rCZ/user/debug-logs.html#viewing-app-logs" + "relUrl": "/hu-rHU/user/debug-logs.html#viewing-app-logs" },"926": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html#exporting", - "relUrl": "/cs-rCZ/user/debug-logs.html#exporting" + "relUrl": "/hu-rHU/user/debug-logs.html#exporting" },"927": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html#desktop", - "relUrl": "/cs-rCZ/user/debug-logs.html#desktop" + "relUrl": "/hu-rHU/user/debug-logs.html#desktop" },"928": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html#related-topics", - "relUrl": "/cs-rCZ/user/debug-logs.html#related-topics" + "relUrl": "/hu-rHU/user/debug-logs.html#related-topics" },"929": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html", - "relUrl": "/fr-rFR/user/debug-logs.html" + "relUrl": "/ht-rHT/user/debug-logs.html" },"930": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html#the-two-tabs", - "relUrl": "/fr-rFR/user/debug-logs.html#the-two-tabs" + "relUrl": "/ht-rHT/user/debug-logs.html#the-two-tabs" },"931": { "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 device. | 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html#viewing-app-logs", - "relUrl": "/fr-rFR/user/debug-logs.html#viewing-app-logs" + "relUrl": "/ht-rHT/user/debug-logs.html#viewing-app-logs" },"932": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html#exporting", - "relUrl": "/fr-rFR/user/debug-logs.html#exporting" + "relUrl": "/ht-rHT/user/debug-logs.html#exporting" },"933": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html#desktop", - "relUrl": "/fr-rFR/user/debug-logs.html#desktop" + "relUrl": "/ht-rHT/user/debug-logs.html#desktop" },"934": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html#related-topics", - "relUrl": "/fr-rFR/user/debug-logs.html#related-topics" + "relUrl": "/ht-rHT/user/debug-logs.html#related-topics" },"935": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html", - "relUrl": "/zh-rCN/user/debug-logs.html" + "relUrl": "/gl-rES/user/debug-logs.html" },"936": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html#the-two-tabs", - "relUrl": "/zh-rCN/user/debug-logs.html#the-two-tabs" + "relUrl": "/gl-rES/user/debug-logs.html#the-two-tabs" },"937": { "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 device. | 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", + "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html#viewing-app-logs", - "relUrl": "/zh-rCN/user/debug-logs.html#viewing-app-logs" + "relUrl": "/gl-rES/user/debug-logs.html#viewing-app-logs" },"938": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html#exporting", - "relUrl": "/zh-rCN/user/debug-logs.html#exporting" + "relUrl": "/gl-rES/user/debug-logs.html#exporting" },"939": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html#desktop", - "relUrl": "/zh-rCN/user/debug-logs.html#desktop" + "relUrl": "/gl-rES/user/debug-logs.html#desktop" },"940": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html#related-topics", - "relUrl": "/zh-rCN/user/debug-logs.html#related-topics" + "relUrl": "/gl-rES/user/debug-logs.html#related-topics" },"941": { - "doc": "Дебаг логови", - "title": "Дебаг логови", + "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html", - "relUrl": "/srp/user/debug-logs.html" + "relUrl": "/tr-rTR/user/debug-logs.html" },"942": { - "doc": "Дебаг логови", + "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/srp/user/debug-logs.html#the-two-tabs", + "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#the-two-tabs", - "relUrl": "/srp/user/debug-logs.html#the-two-tabs" + "relUrl": "/tr-rTR/user/debug-logs.html#the-two-tabs" },"943": { - "doc": "Дебаг логови", + "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 device. | 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#viewing-app-logs", - "relUrl": "/srp/user/debug-logs.html#viewing-app-logs" + "relUrl": "/tr-rTR/user/debug-logs.html#viewing-app-logs" },"944": { - "doc": "Дебаг логови", + "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/srp/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#exporting", - "relUrl": "/srp/user/debug-logs.html#exporting" + "relUrl": "/tr-rTR/user/debug-logs.html#exporting" },"945": { - "doc": "Дебаг логови", + "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/srp/user/debug-logs.html#desktop", + "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#desktop", - "relUrl": "/srp/user/debug-logs.html#desktop" + "relUrl": "/tr-rTR/user/debug-logs.html#desktop" },"946": { - "doc": "Дебаг логови", + "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/srp/user/debug-logs.html#related-topics", + "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#related-topics", - "relUrl": "/srp/user/debug-logs.html#related-topics" + "relUrl": "/tr-rTR/user/debug-logs.html#related-topics" },"947": { "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 no longer need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. 📎 Filing an issue? Export your logs (see below) and attach the .txt file to your report at github.com/meshtastic/Meshtastic-Android/issues. 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", + "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html", - "relUrl": "/sq-rAL/user/debug-logs.html" + "relUrl": "/es-rES/user/debug-logs.html" },"948": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#the-two-tabs", - "relUrl": "/sq-rAL/user/debug-logs.html#the-two-tabs" + "relUrl": "/es-rES/user/debug-logs.html#the-two-tabs" },"949": { "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 device. | 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", + "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#viewing-app-logs", - "relUrl": "/sq-rAL/user/debug-logs.html#viewing-app-logs" + "relUrl": "/es-rES/user/debug-logs.html#viewing-app-logs" },"950": { "doc": "Debug Logs", "title": "Exporting", "content": "Tap the download icon to save the current logs to a file. You choose where it goes through the system file picker, and the file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, and session passkeys before writing the file. Channel PSKs are not redacted, and logs can also contain node names, positions, and other identifying details — glance through the file before sharing it publicly, and share privately if you have any doubt. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/debug-logs.html#exporting", + "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#exporting", - "relUrl": "/sq-rAL/user/debug-logs.html#exporting" + "relUrl": "/es-rES/user/debug-logs.html#exporting" },"951": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#desktop", - "relUrl": "/sq-rAL/user/debug-logs.html#desktop" + "relUrl": "/es-rES/user/debug-logs.html#desktop" },"952": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#related-topics", - "relUrl": "/sq-rAL/user/debug-logs.html#related-topics" + "relUrl": "/es-rES/user/debug-logs.html#related-topics" },"953": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html", - - "relUrl": "/is-rIS/user/desktop.html" - },"954": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#installation", - - "relUrl": "/is-rIS/user/desktop.html#installation" - },"955": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"956": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"957": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#ui-differences", - - "relUrl": "/is-rIS/user/desktop.html#ui-differences" - },"958": { - "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 application. 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" - },"959": { - "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 21 | 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" - },"960": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"961": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#related-topics", - - "relUrl": "/is-rIS/user/desktop.html#related-topics" - },"962": { - "doc": "デスクトップアプリ", - "title": "デスクトップアプリ", - "content": "Meshtastic デスクトップアプリケーションは、Kotlin Multiplatform を通じて、コアのコードベースを Android と共有しています。 ほとんどの機能は、Linux、macOS、Windows で同じように動作します。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html", - - "relUrl": "/ja-rJP/user/desktop.html" - },"963": { - "doc": "デスクトップアプリ", - "title": "インストール", - "content": "Linux . | リリースページから .deb または .AppImage パッケージをダウンロードします | または、./gradlew :desktopApp:run を使ってソースからビルドします | . macOS . | リリースから .dmg パッケージをダウンロードします | または、ソースからビルドします | . Windows . | リリースから .msi インストーラーをダウンロードします | または、ソースからビルドします | . ", - "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#インストール" - },"964": { - "doc": "デスクトップアプリ", - "title": "無線機を接続する", - "content": "USB シリアル（主要） . デスクトップで最も信頼できる接続方法です： . | USB ケーブルで Meshtastic 無線機を接続します。 | アプリがシリアルポートを自動的に検出します。 | 検出されない場合は、接続メニューから正しいシリアルポートを選択します。 | . TCP/IP . ネットワーク接続された無線機の場合： . | 無線機の IP アドレスとポート（既定：4403）を入力します。 | 「接続」をクリックします。 | . Bluetooth（BLE） . Bluetooth Low Energy は、Kable ライブラリを通じてデスクトップでサポートされています： . | システムに Bluetooth アダプターがあることを確認します。 | アプリが近くの Meshtastic 無線機を自動的にスキャンします。 | 接続画面からデバイスを選択します。 | . ", - "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#無線機を接続する" - },"965": { - "doc": "デスクトップアプリ", - "title": "機能の対応状況", - "content": "| 機能 | Android | デスクトップ | 備考 | . | メッセージング | ✓ | ✓ | 完全対応 | . | ノードリスト | ✓ | ✓ | 完全対応 | . | マップ | ✓ | ◐ | マップタブはデスクトップにも存在しますが、インタラクティブなマップビューは Android のみです | . | 設定 | ✓ | ✓ | 完全対応 | . | Bluetooth（BLE） | ✓ | ✓ | デスクトップでは Kable 経由 | . | ファームウェアの更新 | ✓ | ✓ | アプリ内の USB、BLE、Wi-Fi（ESP32）更新はすべて、Android と同じように動作します | . | 通知 | ✓ | ✓ | OS ネイティブの通知 | . | ウィジェット | ✓ | ✗ | Android のみ | . | Android Auto | ✓ | ✗ | Android のみ。デスクトップや iOS では利用できません | . | 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#機能の対応状況" - },"966": { - "doc": "デスクトップアプリ", - "title": "UI の違い", - "content": "デスクトップアプリは、同じ Compose Multiplatform の UI を使用し、大きな画面とデスクトップ操作に合わせて調整されています。 . キーボードショートカット . ショートカットは、macOS では ⌘（Command）、Windows と Linux では Ctrl を使用します。 （Super／Windows キーは割り当てられていません。） . | ショートカット | 操作 | . | ⌘/Ctrl+Q | アプリケーションを終了 | . | ⌘/Ctrl+, | 設定を開く | . | ⌘/Ctrl+1 | メッセージタブに切り替え | . | ⌘/Ctrl+2 | ノードタブに切り替え | . | ⌘/Ctrl+3 | マップタブに切り替え | . | ⌘/Ctrl+4 | 接続タブに切り替え | . | ⌘/Ctrl+/ | バージョン情報を開く | . ウィンドウとシステムトレイ . | ウィンドウのサイズ変更：レスポンシブなレイアウトがウィンドウの寸法に合わせて調整されます | システムトレイ：システムトレイに最小化して、バックグラウンドでメッシュを動作させます | トレイメニュー：トレイアイコンを右クリックして、ウィンドウ表示または終了します | マウス操作：ホバー状態と標準的なデスクトップのナビゲーション | . 通知の設定 . デスクトップアプリには、どの通知を表示するか（メッセージ、新しいノード、バッテリー低下の警告）を制御するアプリ内トグルがあります。 これらには、アプリ内の「設定 → 通知」からアクセスします。 . ", - "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-の違い" - },"967": { - "doc": "デスクトップアプリ", - "title": "組み込みのドキュメントブラウザー", - "content": "デスクトップアプリには、アプリケーションを離れることなくヘルプコンテンツにすばやくアクセスできる、組み込みのドキュメントブラウザーが含まれています。 . ブラウザーは、すべてのドキュメントを対象とした全文検索に対応しています： . 個々のドキュメントページは、完全な書式で表示されます： . ", - "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#組み込みのドキュメントブラウザー" - },"968": { - "doc": "デスクトップアプリ", - "title": "ソースからビルドする", - "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . 要件： . | JDK 21 | デスクトップのみのビルドに 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#ソースからビルドする" - },"969": { - "doc": "デスクトップアプリ", - "title": "既知の制限", - "content": ". | インタラクティブなマップビューは Android のみです。マップタブは存在しますが、デスクトップではマップが表示されません。 | 一部の 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#既知の制限" - },"970": { - "doc": "デスクトップアプリ", - "title": "関連トピック", - "content": ". | コネクション：接続方法の概要 | ファームウェア更新：USB、BLE、Wi-Fi 更新はすべて、Android と同じように動作します | . ", - "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#関連トピック" - },"971": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html", - - "relUrl": "/ca-rES/user/desktop.html" - },"972": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#installation", - - "relUrl": "/ca-rES/user/desktop.html#installation" - },"973": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"974": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"975": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#ui-differences", - - "relUrl": "/ca-rES/user/desktop.html#ui-differences" - },"976": { - "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 application. 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" - },"977": { - "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 21 | 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" - },"978": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"979": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#related-topics", - - "relUrl": "/ca-rES/user/desktop.html#related-topics" - },"980": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html", - - "relUrl": "/sr-rLatn/user/desktop.html" - },"981": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#installation", - - "relUrl": "/sr-rLatn/user/desktop.html#installation" - },"982": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"983": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Белешке | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Мапа | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Подешавања | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"984": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#ui-differences", - - "relUrl": "/sr-rLatn/user/desktop.html#ui-differences" - },"985": { - "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 application. 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" - },"986": { - "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 21 | 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" - },"987": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"988": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#related-topics", - - "relUrl": "/sr-rLatn/user/desktop.html#related-topics" - },"989": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html", - - "relUrl": "/ko-rKR/user/desktop.html" - },"990": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#installation", - - "relUrl": "/ko-rKR/user/desktop.html#installation" - },"991": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"992": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | 지도 | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | 설정 | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"993": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#ui-differences", - - "relUrl": "/ko-rKR/user/desktop.html#ui-differences" - },"994": { - "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 application. 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" - },"995": { - "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 21 | 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" - },"996": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"997": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#related-topics", - - "relUrl": "/ko-rKR/user/desktop.html#related-topics" - },"998": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html", - - "relUrl": "/ro-rRO/user/desktop.html" - },"999": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#installation", - - "relUrl": "/ro-rRO/user/desktop.html#installation" - },"1000": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1001": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notițe | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Setări | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Actualizare firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1002": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#ui-differences", - - "relUrl": "/ro-rRO/user/desktop.html#ui-differences" - },"1003": { - "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 application. 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" - },"1004": { - "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 21 | 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" - },"1005": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1006": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#related-topics", - - "relUrl": "/ro-rRO/user/desktop.html#related-topics" - },"1007": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html", - - "relUrl": "/ga-rIE/user/desktop.html" - },"1008": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#installation", - - "relUrl": "/ga-rIE/user/desktop.html#installation" - },"1009": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1010": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1011": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#ui-differences", - - "relUrl": "/ga-rIE/user/desktop.html#ui-differences" - },"1012": { - "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 application. 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" - },"1013": { - "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 21 | 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" - },"1014": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1015": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#related-topics", - - "relUrl": "/ga-rIE/user/desktop.html#related-topics" - },"1016": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html", - - "relUrl": "/iw-rIL/user/desktop.html" - },"1017": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#installation", - - "relUrl": "/iw-rIL/user/desktop.html#installation" - },"1018": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1019": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | מפה | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | הגדרות | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1020": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#ui-differences", - - "relUrl": "/iw-rIL/user/desktop.html#ui-differences" - },"1021": { - "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 application. 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" - },"1022": { - "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 21 | 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" - },"1023": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1024": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#related-topics", - - "relUrl": "/iw-rIL/user/desktop.html#related-topics" - },"1025": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html", - - "relUrl": "/sv-rSE/user/desktop.html" - },"1026": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#installation", - - "relUrl": "/sv-rSE/user/desktop.html#installation" - },"1027": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1028": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Anteckningar | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Karta | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Inställningar | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Uppdatering av fast programvara | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1029": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#ui-differences", - - "relUrl": "/sv-rSE/user/desktop.html#ui-differences" - },"1030": { - "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 application. 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" - },"1031": { - "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 21 | 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" - },"1032": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1033": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#related-topics", - - "relUrl": "/sv-rSE/user/desktop.html#related-topics" - },"1034": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html", - - "relUrl": "/ht-rHT/user/desktop.html" - },"1035": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#installation", - - "relUrl": "/ht-rHT/user/desktop.html#installation" - },"1036": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1037": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1038": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#ui-differences", - - "relUrl": "/ht-rHT/user/desktop.html#ui-differences" - },"1039": { - "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 application. 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" - },"1040": { - "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 21 | 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" - },"1041": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1042": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#related-topics", - - "relUrl": "/ht-rHT/user/desktop.html#related-topics" - },"1043": { - "doc": "Työpöytäsovellus", - "title": "Työpöytäsovellus", - "content": "Meshtastic-työpöytäsovellus jakaa ydinkoodipohjan Android-version kanssa Kotlin Multiplatformin kautta. Useimmat ominaisuudet toimivat identtisesti Linuxilla, macOS:llä ja Windowsilla. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html", - - "relUrl": "/fi-rFI/user/desktop.html" - },"1044": { - "doc": "Työpöytäsovellus", - "title": "Asennus", - "content": "Linux . | Lataa .deb- tai .AppImage-paketti julkaisusivulta | Tai rakenna lähdekoodista komennolla ./gradlew :desktopApp:run | . macOS . | Lataa .dmg-paketti julkaisusivulta | Tai rakenna lähdekoodista | . Windows . | Lataa .msi-asennuspaketti julkaisusivulta | Tai rakenna lähdekoodista | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#asennus", - - "relUrl": "/fi-rFI/user/desktop.html#asennus" - },"1045": { - "doc": "Työpöytäsovellus", - "title": "Radioon yhdistäminen", - "content": "USB-sarjaportti (ensisijainen) . Luotettavin yhteystapa työpöydällä: . | Yhdistä Meshtastic-radio USB-kaapelilla. | Sovelluksen pitäisi tunnistaa sarjaportti automaattisesti. | Jos laitetta ei tunnisteta, valitse oikea sarjaportti 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 kautta: . | Varmista, että järjestelmässäsi on Bluetooth-adapteri. | Sovellus etsii lähellä olevia Meshtastic-radioita automaattisesti. | Valitse laitteesi Yhdistä-näkymästä. | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#radioon-yhdist%C3%A4minen", - - "relUrl": "/fi-rFI/user/desktop.html#radioon-yhdistäminen" - },"1046": { - "doc": "Työpöytäsovellus", - "title": "Ominaisuuksien yhtenevyys", - "content": "| Ominaisuus | Android | Työpöytä | Viestit | . | Viestit | ✓ | ✓ | Täysi yhtenevyys | . | Radiolista | ✓ | ✓ | Täysi yhtenevyys | . | Kartta | ✓ | ◐ | Kartta-välilehti on käytettävissä myös Desktop-versiossa, mutta interaktiivinen karttanäkymä on käytettävissä vain Androidissa | . | Asetukset | ✓ | ✓ | Täysi yhtenevyys | . | Bluetooth (BLE) | ✓ | ✓ | Työpöydällä Kable-kirjaston kautta | . | Laiteohjelmiston päivitys | ✓ | ✓ | Sovelluksen USB-, BLE- ja Wi-Fi-päivitykset (ESP32) toimivat samalla tavalla kuin Androidissa | . | Ilmoitukset | ✓ | ✓ | Käyttöjärjestelmän natiivit ilmoitukset | . | Widgetit | ✓ | ✗ | Vain Android | . | Vain Android | ✓ | ✗ | Vain Android — ei saatavilla työpöydällä tai iOS:llä | . | 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" - },"1047": { - "doc": "Työpöytäsovellus", - "title": "Käyttöliittymäerot", - "content": "Työpöytäsovellus käyttää samaa Compose Multiplatform -käyttöliittymää, mutta se 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 | Järjestelmätarjotin — pienennä järjestelmätarjottimeen taustalla tapahtuvaa mesh-toimintaa varten | 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 . Työpöytäsovellus tarjoaa sisäiset kytkimet ilmoitusten hallintaan — viestit, uudet radiot ja alhaisen akun varoitukset. Avaa nämä kohdasta Asetukset → Ilmoitukset sovelluksessa. ", - "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" - },"1048": { - "doc": "Työpöytäsovellus", - "title": "Sisäänrakennettu dokumentaatioselain", - "content": "Työpöytäsovellus sisältää sisäänrakennetun dokumentaatioselaimen, 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" - },"1049": { - "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 21 | 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" - },"1050": { - "doc": "Työpöytäsovellus", - "title": "Tunnetut rajoitukset", - "content": ". | Interaktiivinen karttanäkymä on käytettävissä vain Androidissa — Kartta-välilehti on työpöytä-versiossa näkyvissä, mutta karttaa ei näytetä | 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" - },"1051": { - "doc": "Työpöytäsovellus", - "title": "Aiheeseen liittyvät aiheet", - "content": ". | Yhteydet — yhteystapojen yleiskatsaus | Laiteohjelmistopäivitykset — USB-, BLE- ja Wi-Fi-päivitykset toimivat samalla tavalla kuin Androidissa | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#aiheeseen-liittyv%C3%A4t-aiheet", - - "relUrl": "/fi-rFI/user/desktop.html#aiheeseen-liittyvät-aiheet" - },"1052": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html", - - "relUrl": "/gl-rES/user/desktop.html" - },"1053": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#installation", - - "relUrl": "/gl-rES/user/desktop.html#installation" - },"1054": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1055": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1056": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#ui-differences", - - "relUrl": "/gl-rES/user/desktop.html#ui-differences" - },"1057": { - "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 application. 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" - },"1058": { - "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 21 | 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" - },"1059": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1060": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#related-topics", - - "relUrl": "/gl-rES/user/desktop.html#related-topics" - },"1061": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html", - - "relUrl": "/uk-rUA/user/desktop.html" - },"1062": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#installation", - - "relUrl": "/uk-rUA/user/desktop.html#installation" - },"1063": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1064": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Нотатки | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Мапа | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Налаштування | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Оновити прошивку | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1065": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#ui-differences", - - "relUrl": "/uk-rUA/user/desktop.html#ui-differences" - },"1066": { - "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 application. 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" - },"1067": { - "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 21 | 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" - },"1068": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1069": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#related-topics", - - "relUrl": "/uk-rUA/user/desktop.html#related-topics" - },"1070": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html", "relUrl": "/de-rDE/user/desktop.html" - },"1071": { + },"954": { "doc": "Desktop App", "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html#installation", "relUrl": "/de-rDE/user/desktop.html#installation" - },"1072": { + },"955": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1073": { + },"956": { "doc": "Desktop App", "title": "Feature Parity", "content": "| Funktion | Android | Desktop | Knoten | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Karte | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Einstellungen | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Aktualisierung | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Benachrichtigungen | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1074": { + },"957": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html#ui-differences", "relUrl": "/de-rDE/user/desktop.html#ui-differences" - },"1075": { + },"958": { "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 application. 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" - },"1076": { + },"959": { "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 21 | 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" - },"1077": { + },"960": { "doc": "Desktop App", "title": "Bekannte Einschränkungen", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1078": { + },"961": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html#related-topics", "relUrl": "/de-rDE/user/desktop.html#related-topics" - },"1079": { + },"962": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html", + "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html", - "relUrl": "/hr-rHR/user/desktop.html" - },"1080": { + "relUrl": "/ca-rES/user/desktop.html" + },"963": { "doc": "Desktop App", "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#installation", + "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#installation", - "relUrl": "/hr-rHR/user/desktop.html#installation" - },"1081": { + "relUrl": "/ca-rES/user/desktop.html#installation" + },"964": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#connecting-your-radio", + "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#connecting-your-radio", - "relUrl": "/hr-rHR/user/desktop.html#connecting-your-radio" - },"1082": { + "relUrl": "/ca-rES/user/desktop.html#connecting-your-radio" + },"965": { "doc": "Desktop App", "title": "Feature Parity", "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#feature-parity", - "relUrl": "/hr-rHR/user/desktop.html#feature-parity" - },"1083": { + "relUrl": "/ca-rES/user/desktop.html#feature-parity" + },"966": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#ui-differences", + "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#ui-differences", - "relUrl": "/hr-rHR/user/desktop.html#ui-differences" - },"1084": { + "relUrl": "/ca-rES/user/desktop.html#ui-differences" + },"967": { "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 application. 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", + "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#built-in-documentation-browser", - "relUrl": "/hr-rHR/user/desktop.html#built-in-documentation-browser" - },"1085": { + "relUrl": "/ca-rES/user/desktop.html#built-in-documentation-browser" + },"968": { "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 21 | No Android SDK required for desktop-only builds | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#building-from-source", + "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#building-from-source", - "relUrl": "/hr-rHR/user/desktop.html#building-from-source" - },"1086": { + "relUrl": "/ca-rES/user/desktop.html#building-from-source" + },"969": { "doc": "Desktop App", "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#known-limitations", - "relUrl": "/hr-rHR/user/desktop.html#known-limitations" - },"1087": { + "relUrl": "/ca-rES/user/desktop.html#known-limitations" + },"970": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#related-topics", + "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#related-topics", - "relUrl": "/hr-rHR/user/desktop.html#related-topics" - },"1088": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html", - - "relUrl": "/lt-rLT/user/desktop.html" - },"1089": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#installation", - - "relUrl": "/lt-rLT/user/desktop.html#installation" - },"1090": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1091": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1092": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#ui-differences", - - "relUrl": "/lt-rLT/user/desktop.html#ui-differences" - },"1093": { - "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 application. 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" - },"1094": { - "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 21 | 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" - },"1095": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1096": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#related-topics", - - "relUrl": "/lt-rLT/user/desktop.html#related-topics" - },"1097": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/en/user/desktop.html", - - "relUrl": "/en/user/desktop.html" - },"1098": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/en/user/desktop.html#installation", - - "relUrl": "/en/user/desktop.html#installation" - },"1099": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", - "url": "/Meshtastic-Android/main/en/user/desktop.html#connecting-your-radio", - - "relUrl": "/en/user/desktop.html#connecting-your-radio" - },"1100": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1101": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/en/user/desktop.html#ui-differences", - - "relUrl": "/en/user/desktop.html#ui-differences" - },"1102": { - "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 application. 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" - },"1103": { - "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 21 | 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" - },"1104": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1105": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/en/user/desktop.html#related-topics", - - "relUrl": "/en/user/desktop.html#related-topics" - },"1106": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html", - - "relUrl": "/hu-rHU/user/desktop.html" - },"1107": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#installation", - - "relUrl": "/hu-rHU/user/desktop.html#installation" - },"1108": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1109": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Jegyzetek | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Térkép | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Beállítások | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1110": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#ui-differences", - - "relUrl": "/hu-rHU/user/desktop.html#ui-differences" - },"1111": { - "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 application. 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" - },"1112": { - "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 21 | 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" - },"1113": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1114": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#related-topics", - - "relUrl": "/hu-rHU/user/desktop.html#related-topics" - },"1115": { - "doc": "Настолно приложение", - "title": "Настолно приложение", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html", - - "relUrl": "/bg-rBG/user/desktop.html" - },"1116": { - "doc": "Настолно приложение", - "title": "Инсталация", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Или изградете от изходния код | . Windows . | Download the .msi installer from releases | Или изградете от изходния код | . ", - "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#инсталация" - },"1117": { - "doc": "Настолно приложение", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1118": { - "doc": "Настолно приложение", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Бележки | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Карта | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Настройки | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Актуализация на фърмуера | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Известия | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1119": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html#ui-differences", - - "relUrl": "/bg-rBG/user/desktop.html#ui-differences" - },"1120": { - "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 application. 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" - },"1121": { - "doc": "Настолно приложение", - "title": "Building from Source", - "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Изисквания: . | JDK 21 | 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" - },"1122": { - "doc": "Настолно приложение", - "title": "Известни ограничения", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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#известни-ограничения" - },"1123": { - "doc": "Настолно приложение", - "title": "Свързани теми", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "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#свързани-теми" - },"1124": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html", - - "relUrl": "/sl-rSI/user/desktop.html" - },"1125": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#installation", - - "relUrl": "/sl-rSI/user/desktop.html#installation" - },"1126": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1127": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1128": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#ui-differences", - - "relUrl": "/sl-rSI/user/desktop.html#ui-differences" - },"1129": { - "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 application. 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" - },"1130": { - "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 21 | 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" - },"1131": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1132": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#related-topics", - - "relUrl": "/sl-rSI/user/desktop.html#related-topics" - },"1133": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html", - - "relUrl": "/pt-rPT/user/desktop.html" - },"1134": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#installation", - - "relUrl": "/pt-rPT/user/desktop.html#installation" - },"1135": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1136": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Definições | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1137": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#ui-differences", - - "relUrl": "/pt-rPT/user/desktop.html#ui-differences" - },"1138": { - "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 application. 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" - },"1139": { - "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 21 | 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" - },"1140": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1141": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#related-topics", - - "relUrl": "/pt-rPT/user/desktop.html#related-topics" - },"1142": { + "relUrl": "/ca-rES/user/desktop.html#related-topics" + },"971": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html", "relUrl": "/be-rBY/user/desktop.html" - },"1143": { + },"972": { "doc": "Desktop App", "title": "Установка", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", "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#установка" - },"1144": { + },"973": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1145": { + },"974": { "doc": "Desktop App", "title": "Feature Parity", "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Налады | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1146": { + },"975": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html#ui-differences", "relUrl": "/be-rBY/user/desktop.html#ui-differences" - },"1147": { + },"976": { "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 application. 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" - },"1148": { + },"977": { "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 21 | 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" - },"1149": { + },"978": { "doc": "Desktop App", "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1150": { + },"979": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html#related-topics", "relUrl": "/be-rBY/user/desktop.html#related-topics" - },"1151": { + },"980": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html", + + "relUrl": "/uk-rUA/user/desktop.html" + },"981": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#installation", + + "relUrl": "/uk-rUA/user/desktop.html#installation" + },"982": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"983": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Нотатки | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Мапа | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Налаштування | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Оновити прошивку | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"984": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#ui-differences", + + "relUrl": "/uk-rUA/user/desktop.html#ui-differences" + },"985": { + "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 application. 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" + },"986": { + "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 21 | 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" + },"987": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"988": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#related-topics", + + "relUrl": "/uk-rUA/user/desktop.html#related-topics" + },"989": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html", + + "relUrl": "/zh-rCN/user/desktop.html" + },"990": { + "doc": "Desktop App", + "title": "安装", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#%E5%AE%89%E8%A3%85", + + "relUrl": "/zh-rCN/user/desktop.html#安装" + },"991": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"992": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | 注 | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | 地图 | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | 设置 | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | 固件更新 | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"993": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#ui-differences", + + "relUrl": "/zh-rCN/user/desktop.html#ui-differences" + },"994": { + "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 application. 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" + },"995": { + "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 21 | 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" + },"996": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"997": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#related-topics", + + "relUrl": "/zh-rCN/user/desktop.html#related-topics" + },"998": { + "doc": "Настолно приложение", + "title": "Настолно приложение", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html", + + "relUrl": "/bg-rBG/user/desktop.html" + },"999": { + "doc": "Настолно приложение", + "title": "Инсталация", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Или изградете от изходния код | . Windows . | Download the .msi installer from releases | Или изградете от изходния код | . ", + "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#инсталация" + },"1000": { + "doc": "Настолно приложение", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1001": { + "doc": "Настолно приложение", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Бележки | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Карта | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Настройки | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Актуализация на фърмуера | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Известия | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1002": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html#ui-differences", + + "relUrl": "/bg-rBG/user/desktop.html#ui-differences" + },"1003": { + "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 application. 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" + },"1004": { + "doc": "Настолно приложение", + "title": "Building from Source", + "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Изисквания: . | JDK 21 | 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" + },"1005": { + "doc": "Настолно приложение", + "title": "Известни ограничения", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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#известни-ограничения" + },"1006": { + "doc": "Настолно приложение", + "title": "Свързани теми", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "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#свързани-теми" + },"1007": { + "doc": "桌面版應用程式", + "title": "桌面版應用程式", + "content": "Meshtastic 桌面版應用程式透過 Kotlin Multiplatform 與 Android 版共用核心程式碼庫。 大多數功能在 Linux、macOS 及 Windows 上的運作方式完全相同。 . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html", + + "relUrl": "/zh-rTW/user/desktop.html" + },"1008": { + "doc": "桌面版應用程式", + "title": "安裝", + "content": "Linux . | 從發布頁面下載.deb 或.AppImage 安裝套件 | 或使用 ./gradlew :desktopApp:run 從原始碼自行建置 | . macOS . | 從發布頁面下載.dmg 安裝套件 | 或從原始碼自行建置 | . Windows . | 從發布頁面下載.msi 安裝程式 | 或從原始碼自行建置 | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E5%AE%89%E8%A3%9D", + + "relUrl": "/zh-rTW/user/desktop.html#安裝" + },"1009": { + "doc": "桌面版應用程式", + "title": "連接您的無線電裝置", + "content": "USB 序列埠（主要方式） . 桌面版上最穩定可靠的連線方式： . | 請使用 USB 傳輸線連接您的 Meshtastic 無線電裝置。 | 應用程式應會自動偵測序列埠。 | 若未自動偵測到，請從連線選單中手動選取正確的序列埠。 | . TCP/IP . 若使用網路連線的無線電裝置： . | 輸入無線電裝置的 IP 位址與連接埠（預設：4403）。 | 點選「連線」。 | . 藍牙（BLE） . 桌面版透過 Kable 函式庫支援藍牙低功耗： . | 請確認您的系統配備藍牙介面卡。 | 應用程式將自動掃描附近的 Meshtastic 無線電裝置。 | 從連線畫面中選取您的裝置。 | . ", + "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#連接您的無線電裝置" + },"1010": { + "doc": "桌面版應用程式", + "title": "功能對等性", + "content": "| 功能 | Android | 桌面版 | 備註 | . | 訊息傳送 | ✓ | ✓ | 完全對等 | . | 節點清單 | ✓ | ✓ | 完全對等 | . | 地圖 | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | 設定 | ✓ | ✓ | 完全對等 | . | 藍牙（BLE） | ✓ | ✓ | 桌面版透過 Kable 支援 | . | 韌體更新 | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | 通知 | ✓ | ✓ | 原生作業系統通知 | . | 小工具 | ✓ | ✗ | 僅限 Android | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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#功能對等性" + },"1011": { + "doc": "桌面版應用程式", + "title": "介面差異", + "content": "桌面版應用程式採用相同的 Compose Multiplatform 介面，並針對較大螢幕與桌面操作方式進行調整。 . 鍵盤快速鍵 . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | 快速鍵 | 動作 | . | ⌘/Ctrl+Q | 結束應用程式 | . | ⌘/Ctrl+, | 開啟設定 | . | ⌘/Ctrl+1 | 切換至訊息頁籤 | . | ⌘/Ctrl+2 | 切換至節點頁籤 | . | ⌘/Ctrl+3 | 切換至地圖頁籤 | . | ⌘/Ctrl+4 | 切換至連線頁籤 | . | ⌘/Ctrl+/ | Open About | . 視窗與系統匣 . | 調整視窗大小 — 響應式版面配置可依視窗尺寸自動調整 | 系統匣 — 可最小化至系統匣，於背景持續進行 mesh 網路操作 | 匣列選單 — 在系統匣圖示上按右鍵，可顯示視窗或結束程式 | 滑鼠互動 — 支援停駐狀態與標準桌面導覽操作 | . 通知偏好設定 . 桌面版應用程式提供應用程式內的切換開關，可控制顯示哪些通知 — 包含訊息、新節點及低電量警示。 請在應用程式中前往「設定 → 通知」進行設定。 . ", + "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#介面差異" + },"1012": { + "doc": "桌面版應用程式", + "title": "內建文件瀏覽器", + "content": "桌面版應用程式內建文件瀏覽器，無需離開應用程式即可快速存取說明內容。 . 瀏覽器支援跨所有文件的全文搜尋： . 各文件頁面以完整格式呈現： . ", + "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#內建文件瀏覽器" + },"1013": { + "doc": "桌面版應用程式", + "title": "從原始碼建置", + "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . 需求： . | JDK 21 | 純桌面版建置不需要 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#從原始碼建置" + },"1014": { + "doc": "桌面版應用程式", + "title": "已知限制", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 部分 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#已知限制" + },"1015": { + "doc": "桌面版應用程式", + "title": "相關主題", + "content": ". | 〔連線〕(connections) — 連線方式概覽 | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "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#相關主題" + },"1016": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html", + + "relUrl": "/sr-rLatn/user/desktop.html" + },"1017": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#installation", + + "relUrl": "/sr-rLatn/user/desktop.html#installation" + },"1018": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1019": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Белешке | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Мапа | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Подешавања | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1020": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#ui-differences", + + "relUrl": "/sr-rLatn/user/desktop.html#ui-differences" + },"1021": { + "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 application. 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" + },"1022": { + "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 21 | 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" + },"1023": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1024": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#related-topics", + + "relUrl": "/sr-rLatn/user/desktop.html#related-topics" + },"1025": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html", + + "relUrl": "/cs-rCZ/user/desktop.html" + },"1026": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#installation", + + "relUrl": "/cs-rCZ/user/desktop.html#installation" + },"1027": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1028": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Poznámka | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Nastavení | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Aktualizace firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1029": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#ui-differences", + + "relUrl": "/cs-rCZ/user/desktop.html#ui-differences" + },"1030": { + "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 application. 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" + },"1031": { + "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 21 | 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" + },"1032": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1033": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#related-topics", + + "relUrl": "/cs-rCZ/user/desktop.html#related-topics" + },"1034": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/en/user/desktop.html", + + "relUrl": "/en/user/desktop.html" + },"1035": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/en/user/desktop.html#installation", + + "relUrl": "/en/user/desktop.html#installation" + },"1036": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", + "url": "/Meshtastic-Android/main/en/user/desktop.html#connecting-your-radio", + + "relUrl": "/en/user/desktop.html#connecting-your-radio" + },"1037": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1038": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/en/user/desktop.html#ui-differences", + + "relUrl": "/en/user/desktop.html#ui-differences" + },"1039": { + "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 application. 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" + },"1040": { + "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 21 | 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" + },"1041": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1042": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/en/user/desktop.html#related-topics", + + "relUrl": "/en/user/desktop.html#related-topics" + },"1043": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html", + + "relUrl": "/sl-rSI/user/desktop.html" + },"1044": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#installation", + + "relUrl": "/sl-rSI/user/desktop.html#installation" + },"1045": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1046": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1047": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#ui-differences", + + "relUrl": "/sl-rSI/user/desktop.html#ui-differences" + },"1048": { + "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 application. 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" + },"1049": { + "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 21 | 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" + },"1050": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1051": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#related-topics", + + "relUrl": "/sl-rSI/user/desktop.html#related-topics" + },"1052": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html", + + "relUrl": "/it-rIT/user/desktop.html" + },"1053": { + "doc": "Desktop App", + "title": "Installazione", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#installazione", + + "relUrl": "/it-rIT/user/desktop.html#installazione" + },"1054": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1055": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Note | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mappa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Impostazioni | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Aggiornamento Firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1056": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#ui-differences", + + "relUrl": "/it-rIT/user/desktop.html#ui-differences" + },"1057": { + "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 application. 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" + },"1058": { + "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 21 | 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" + },"1059": { + "doc": "Desktop App", + "title": "Limitazioni conosciute", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1060": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#related-topics", + + "relUrl": "/it-rIT/user/desktop.html#related-topics" + },"1061": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html", "relUrl": "/pt-rBR/user/desktop.html" - },"1152": { + },"1062": { "doc": "Desktop App", "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html#installation", "relUrl": "/pt-rBR/user/desktop.html#installation" - },"1153": { + },"1063": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1154": { + },"1064": { "doc": "Desktop App", "title": "Feature Parity", "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Configurações | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1155": { + },"1065": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html#ui-differences", "relUrl": "/pt-rBR/user/desktop.html#ui-differences" - },"1156": { + },"1066": { "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 application. 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" - },"1157": { + },"1067": { "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 21 | 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" - },"1158": { + },"1068": { "doc": "Desktop App", "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1159": { + },"1069": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html#related-topics", "relUrl": "/pt-rBR/user/desktop.html#related-topics" - },"1160": { + },"1070": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html", + "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html", - "relUrl": "/el-rGR/user/desktop.html" - },"1161": { + "relUrl": "/is-rIS/user/desktop.html" + },"1071": { "doc": "Desktop App", "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#installation", + "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#installation", - "relUrl": "/el-rGR/user/desktop.html#installation" - },"1162": { + "relUrl": "/is-rIS/user/desktop.html#installation" + },"1072": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#connecting-your-radio", + "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#connecting-your-radio", - "relUrl": "/el-rGR/user/desktop.html#connecting-your-radio" - },"1163": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Χάρτης | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Ρυθμίσεις | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1164": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#ui-differences", - - "relUrl": "/el-rGR/user/desktop.html#ui-differences" - },"1165": { - "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 application. 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" - },"1166": { - "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 21 | 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" - },"1167": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1168": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#related-topics", - - "relUrl": "/el-rGR/user/desktop.html#related-topics" - },"1169": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/es-rES/user/desktop.html", - - "relUrl": "/es-rES/user/desktop.html" - },"1170": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#installation", - - "relUrl": "/es-rES/user/desktop.html#installation" - },"1171": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1172": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notas | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Ajustes | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Actualización de firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1173": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#ui-differences", - - "relUrl": "/es-rES/user/desktop.html#ui-differences" - },"1174": { - "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 application. 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" - },"1175": { - "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 21 | 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" - },"1176": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1177": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#related-topics", - - "relUrl": "/es-rES/user/desktop.html#related-topics" - },"1178": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html", - - "relUrl": "/tr-rTR/user/desktop.html" - },"1179": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#installation", - - "relUrl": "/tr-rTR/user/desktop.html#installation" - },"1180": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1181": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Harita | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Ayarlar | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1182": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#ui-differences", - - "relUrl": "/tr-rTR/user/desktop.html#ui-differences" - },"1183": { - "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 application. 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" - },"1184": { - "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 21 | 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" - },"1185": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1186": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#related-topics", - - "relUrl": "/tr-rTR/user/desktop.html#related-topics" - },"1187": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html", - - "relUrl": "/no-rNO/user/desktop.html" - },"1188": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#installation", - - "relUrl": "/no-rNO/user/desktop.html#installation" - },"1189": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1190": { + "relUrl": "/is-rIS/user/desktop.html#connecting-your-radio" + },"1073": { "doc": "Desktop App", "title": "Feature Parity", "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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", + "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#feature-parity", - "relUrl": "/no-rNO/user/desktop.html#feature-parity" - },"1191": { + "relUrl": "/is-rIS/user/desktop.html#feature-parity" + },"1074": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#ui-differences", + "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#ui-differences", - "relUrl": "/no-rNO/user/desktop.html#ui-differences" - },"1192": { + "relUrl": "/is-rIS/user/desktop.html#ui-differences" + },"1075": { "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 application. 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", + "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#built-in-documentation-browser", - "relUrl": "/no-rNO/user/desktop.html#built-in-documentation-browser" - },"1193": { + "relUrl": "/is-rIS/user/desktop.html#built-in-documentation-browser" + },"1076": { "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 21 | No Android SDK required for desktop-only builds | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#building-from-source", + "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#building-from-source", - "relUrl": "/no-rNO/user/desktop.html#building-from-source" - },"1194": { + "relUrl": "/is-rIS/user/desktop.html#building-from-source" + },"1077": { "doc": "Desktop App", "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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", + "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#known-limitations", - "relUrl": "/no-rNO/user/desktop.html#known-limitations" - },"1195": { + "relUrl": "/is-rIS/user/desktop.html#known-limitations" + },"1078": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#related-topics", + "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#related-topics", - "relUrl": "/no-rNO/user/desktop.html#related-topics" - },"1196": { + "relUrl": "/is-rIS/user/desktop.html#related-topics" + },"1079": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html", + + "relUrl": "/fr-rFR/user/desktop.html" + },"1080": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#installation", + + "relUrl": "/fr-rFR/user/desktop.html#installation" + },"1081": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1082": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Carte | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Réglages | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Mise à jour du firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1083": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#ui-differences", + + "relUrl": "/fr-rFR/user/desktop.html#ui-differences" + },"1084": { + "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 application. 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" + },"1085": { + "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 21 | 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" + },"1086": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1087": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#related-topics", + + "relUrl": "/fr-rFR/user/desktop.html#related-topics" + },"1088": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/srp/user/desktop.html", + + "relUrl": "/srp/user/desktop.html" + },"1089": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/srp/user/desktop.html#installation", + + "relUrl": "/srp/user/desktop.html#installation" + },"1090": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", + "url": "/Meshtastic-Android/main/srp/user/desktop.html#connecting-your-radio", + + "relUrl": "/srp/user/desktop.html#connecting-your-radio" + },"1091": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Белешке | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Мапа | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Подешавања | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1092": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/srp/user/desktop.html#ui-differences", + + "relUrl": "/srp/user/desktop.html#ui-differences" + },"1093": { + "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 application. 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" + },"1094": { + "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 21 | 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" + },"1095": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1096": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/srp/user/desktop.html#related-topics", + + "relUrl": "/srp/user/desktop.html#related-topics" + },"1097": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html", + + "relUrl": "/sk-rSK/user/desktop.html" + },"1098": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#installation", + + "relUrl": "/sk-rSK/user/desktop.html#installation" + },"1099": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1100": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Nastavenia | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1101": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#ui-differences", + + "relUrl": "/sk-rSK/user/desktop.html#ui-differences" + },"1102": { + "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 application. 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" + },"1103": { + "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 21 | 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" + },"1104": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1105": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#related-topics", + + "relUrl": "/sk-rSK/user/desktop.html#related-topics" + },"1106": { + "doc": "Työpöytäsovellus", + "title": "Työpöytäsovellus", + "content": "Meshtastic-työpöytäsovellus jakaa ydinkoodipohjan Android-version kanssa Kotlin Multiplatformin kautta. Useimmat ominaisuudet toimivat identtisesti Linuxilla, macOS:llä ja Windowsilla. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html", + + "relUrl": "/fi-rFI/user/desktop.html" + },"1107": { + "doc": "Työpöytäsovellus", + "title": "Asennus", + "content": "Linux . | Lataa .deb- tai .AppImage-paketti julkaisusivulta | Tai rakenna lähdekoodista komennolla ./gradlew :desktopApp:run | . macOS . | Lataa .dmg-paketti julkaisusivulta | Tai rakenna lähdekoodista | . Windows . | Lataa .msi-asennuspaketti julkaisusivulta | Tai rakenna lähdekoodista | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#asennus", + + "relUrl": "/fi-rFI/user/desktop.html#asennus" + },"1108": { + "doc": "Työpöytäsovellus", + "title": "Radioon yhdistäminen", + "content": "USB-sarjaportti (ensisijainen) . Luotettavin yhteystapa työpöydällä: . | Yhdistä Meshtastic-radio USB-kaapelilla. | Sovelluksen pitäisi tunnistaa sarjaportti automaattisesti. | Jos laitetta ei tunnisteta, valitse oikea sarjaportti 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 kautta: . | Varmista, että järjestelmässäsi on Bluetooth-adapteri. | Sovellus etsii lähellä olevia Meshtastic-radioita automaattisesti. | Valitse laitteesi Yhdistä-näkymästä. | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#radioon-yhdist%C3%A4minen", + + "relUrl": "/fi-rFI/user/desktop.html#radioon-yhdistäminen" + },"1109": { + "doc": "Työpöytäsovellus", + "title": "Ominaisuuksien yhtenevyys", + "content": "| Ominaisuus | Android | Työpöytä | Viestit | . | Viestit | ✓ | ✓ | Täysi yhtenevyys | . | Radiolista | ✓ | ✓ | Täysi yhtenevyys | . | Kartta | ✓ | ◐ | Kartta-välilehti on käytettävissä myös Desktop-versiossa, mutta interaktiivinen karttanäkymä on käytettävissä vain Androidissa | . | Asetukset | ✓ | ✓ | Täysi yhtenevyys | . | Bluetooth (BLE) | ✓ | ✓ | Työpöydällä Kable-kirjaston kautta | . | Laiteohjelmiston päivitys | ✓ | ✓ | Sovelluksen USB-, BLE- ja Wi-Fi-päivitykset (ESP32) toimivat samalla tavalla kuin Androidissa | . | Ilmoitukset | ✓ | ✓ | Käyttöjärjestelmän natiivit ilmoitukset | . | Widgetit | ✓ | ✗ | Vain Android | . | Vain Android | ✓ | ✗ | Vain Android — ei saatavilla työpöydällä tai iOS:llä | . | 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" + },"1110": { + "doc": "Työpöytäsovellus", + "title": "Käyttöliittymäerot", + "content": "Työpöytäsovellus käyttää samaa Compose Multiplatform -käyttöliittymää, mutta se 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 | Järjestelmätarjotin — pienennä järjestelmätarjottimeen taustalla tapahtuvaa mesh-toimintaa varten | 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 . Työpöytäsovellus tarjoaa sisäiset kytkimet ilmoitusten hallintaan — viestit, uudet radiot ja alhaisen akun varoitukset. Avaa nämä kohdasta Asetukset → Ilmoitukset sovelluksessa. ", + "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" + },"1111": { + "doc": "Työpöytäsovellus", + "title": "Sisäänrakennettu dokumentaatioselain", + "content": "Työpöytäsovellus sisältää sisäänrakennetun dokumentaatioselaimen, 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" + },"1112": { + "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 21 | 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" + },"1113": { + "doc": "Työpöytäsovellus", + "title": "Tunnetut rajoitukset", + "content": ". | Interaktiivinen karttanäkymä on käytettävissä vain Androidissa — Kartta-välilehti on työpöytä-versiossa näkyvissä, mutta karttaa ei näytetä | 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" + },"1114": { + "doc": "Työpöytäsovellus", + "title": "Aiheeseen liittyvät aiheet", + "content": ". | Yhteydet — yhteystapojen yleiskatsaus | Laiteohjelmistopäivitykset — USB-, BLE- ja Wi-Fi-päivitykset toimivat samalla tavalla kuin Androidissa | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#aiheeseen-liittyv%C3%A4t-aiheet", + + "relUrl": "/fi-rFI/user/desktop.html#aiheeseen-liittyvät-aiheet" + },"1115": { "doc": "Настольное приложение", "title": "Настольное приложение", "content": "Настольное приложение Meshtastic использует общий код с Android через Kotlin Multiplatform. Большинство функций работают одинаково на Linux, macOS и Windows. ", "url": "/Meshtastic-Android/main/ru-rRU/user/desktop.html", "relUrl": "/ru-rRU/user/desktop.html" - },"1197": { + },"1116": { "doc": "Настольное приложение", "title": "Установка", "content": "Linux . | Скачайте пакет .deb или .AppImage со страницы релизов | Или соберите из исходного кода с помощью ./gradlew :desktopApp:run | . macOS . | Скачайте пакет .dmg из релизов | Или соберите из исходных кодов | . Windows . | Загрузите установщик .msi со страницы релизов | Или соберите из исходных кодов | . ", "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#установка" - },"1198": { + },"1117": { "doc": "Настольное приложение", "title": "Подключение твоей радиостанции", "content": "Последовательная USB (Основной) . Наиболее надежный способ подключения к компьютеру: . | Подключите свою радиостанцию Meshtastic через USB-кабель. | Приложение должно автоматически определить последовательный порт. | Если порт не определён, выберите правильный последовательный порт в меню “Подключение”. | . TCP/IP . Для радиостанций, подключённых по сети: . | Введите IP-адрес и порт радиостанции (по умолчанию: 4403). | Нажмите “Подключиться”. | . Bluetooth (BLE) . Bluetooth Low Energy поддерживается в настольном приложении с помощью библиотеки Kable: . | Убедитесь, что ваша система оснащена Bluetooth-адаптером. | Приложение автоматически сканирует находящиеся поблизости радиостанции Meshtastic. | Выберите своё устройство на экране «Подключение». | . ", "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#подключение-твоей-радиостанции" - },"1199": { + },"1118": { "doc": "Настольное приложение", "title": "Паритет функций", "content": "| Функция | Android | Desktop | Заметки | . | Обмен сообщениями | ✓ | ✓ | Полное равенство | . | Список узлов | ✓ | ✓ | Полное равенство | . | Карта | ✓ | ◐ | Вкладка карты присутствует в настольном приложении, но интерактивный просмотр карты доступен только на Android | . | Настройки | ✓ | ✓ | Полное равенство | . | Bluetooth (BLE) | ✓ | ✓ | Через Kable в настольном приложении | . | Обновление прошивки | ✓ | ✓ | Внутри приложенное обновление по USB, BLE и Wi-Fi (ESP32) работает так же, как на Android | . | Уведомления | ✓ | ✓ | Системные уведомления | . | Виджеты | ✓ | ✗ | Только Android | . | Android Auto | ✓ | ✗ | Только Android — недоступно в настольном приложении или iOS | . | 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#паритет-функций" - },"1200": { + },"1119": { "doc": "Настольное приложение", "title": "Различия интерфейса", "content": "Настольное приложение использует тот же интерфейс на Compose Multiplatform с адаптациями для больших экранов и настольного взаимодействия. Сочетания клавиш . Сочетания клавиш используют ⌘ (Command) на macOS и Ctrl на Windows и Linux. (Клавиша Super / Windows не используется.) . | Сочетание | Действие | . | ⌘/Ctrl+Q | Выйти из приложения | . | ⌘/Ctrl+, | Открыть настройки | . | ⌘/Ctrl+1 | Перейти во вкладку “Сообщения” | . | ⌘/Ctrl+2 | Перейти во вкладку “Узлы” | . | ⌘/Ctrl+3 | Перейти во вкладку “Карта” | . | ⌘/Ctrl+4 | Перейти во вкладку “Подключение” | . | ⌘/Ctrl+/ | Открыть “О программе” | . Окно и системный трей . | Изменение размера окна — адаптивный макет подстраивается под размеры окна | Системный трей — сверните в системный трей для фоновой работы mesh-сети | Меню трея — щёлкните правой кнопкой мыши по значку в трее, чтобы показать окно или выйти | Взаимодействие с мышью — состояния при наведении и стандартная настольная навигация | . Настройки уведомлений . Настольное приложение предоставляет встроенные переключатели для управления отображением уведомлений: сообщения, новые узлы и предупреждения о низком заряде батареи. Доступ к ним осуществляется через Настройки → Уведомления в самом приложении. ", "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#различия-интерфейса" - },"1201": { + },"1120": { "doc": "Настольное приложение", "title": "Встроенный браузер документации", "content": "Настольное приложение включает встроенный браузер документации для быстрого доступа к справочным материалам без выхода из приложения. Браузер поддерживает полнотекстовый поиск по всей документации: . Отдельные страницы документации отображаются с полным форматированием: . ", "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#встроенный-браузер-документации" - },"1202": { + },"1121": { "doc": "Настольное приложение", "title": "Сборка из исходного кода", "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Требования: . | JDK 21 | Для сборки только настольной версии 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#сборка-из-исходного-кода" - },"1203": { + },"1122": { "doc": "Настольное приложение", "title": "Известные ограничения", "content": ". | Интерактивный просмотр карты доступен только на Android — вкладка «Карта» присутствует в настольном приложении, но не отображает карту | Некоторые специфичные для 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#известные-ограничения" - },"1204": { + },"1123": { "doc": "Настольное приложение", "title": "Связанные темы", "content": ". | Подключения — обзор методов подключения | Обновление прошивки — обновление по USB, BLE и Wi-Fi работает так же, как на Android | . ", "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#связанные-темы" + },"1124": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html", + + "relUrl": "/ko-rKR/user/desktop.html" + },"1125": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#installation", + + "relUrl": "/ko-rKR/user/desktop.html#installation" + },"1126": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1127": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | 지도 | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | 설정 | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1128": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#ui-differences", + + "relUrl": "/ko-rKR/user/desktop.html#ui-differences" + },"1129": { + "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 application. 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" + },"1130": { + "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 21 | 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" + },"1131": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1132": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#related-topics", + + "relUrl": "/ko-rKR/user/desktop.html#related-topics" + },"1133": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html", + + "relUrl": "/hr-rHR/user/desktop.html" + },"1134": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#installation", + + "relUrl": "/hr-rHR/user/desktop.html#installation" + },"1135": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1136": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1137": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#ui-differences", + + "relUrl": "/hr-rHR/user/desktop.html#ui-differences" + },"1138": { + "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 application. 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" + },"1139": { + "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 21 | 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" + },"1140": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1141": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#related-topics", + + "relUrl": "/hr-rHR/user/desktop.html#related-topics" + },"1142": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html", + + "relUrl": "/sq-rAL/user/desktop.html" + },"1143": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#installation", + + "relUrl": "/sq-rAL/user/desktop.html#installation" + },"1144": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1145": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1146": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#ui-differences", + + "relUrl": "/sq-rAL/user/desktop.html#ui-differences" + },"1147": { + "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 application. 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" + },"1148": { + "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 21 | 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" + },"1149": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1150": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#related-topics", + + "relUrl": "/sq-rAL/user/desktop.html#related-topics" + },"1151": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html", + + "relUrl": "/no-rNO/user/desktop.html" + },"1152": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#installation", + + "relUrl": "/no-rNO/user/desktop.html#installation" + },"1153": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1154": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1155": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#ui-differences", + + "relUrl": "/no-rNO/user/desktop.html#ui-differences" + },"1156": { + "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 application. 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" + },"1157": { + "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 21 | 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" + },"1158": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1159": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#related-topics", + + "relUrl": "/no-rNO/user/desktop.html#related-topics" + },"1160": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html", + + "relUrl": "/lt-rLT/user/desktop.html" + },"1161": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#installation", + + "relUrl": "/lt-rLT/user/desktop.html#installation" + },"1162": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1163": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1164": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#ui-differences", + + "relUrl": "/lt-rLT/user/desktop.html#ui-differences" + },"1165": { + "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 application. 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" + },"1166": { + "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 21 | 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" + },"1167": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1168": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#related-topics", + + "relUrl": "/lt-rLT/user/desktop.html#related-topics" + },"1169": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html", + + "relUrl": "/ar-rSA/user/desktop.html" + },"1170": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#installation", + + "relUrl": "/ar-rSA/user/desktop.html#installation" + },"1171": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1172": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | الخريطة | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | الإعدادات | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1173": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#ui-differences", + + "relUrl": "/ar-rSA/user/desktop.html#ui-differences" + },"1174": { + "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 application. 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" + },"1175": { + "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 21 | 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" + },"1176": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1177": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#related-topics", + + "relUrl": "/ar-rSA/user/desktop.html#related-topics" + },"1178": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html", + + "relUrl": "/pt-rPT/user/desktop.html" + },"1179": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#installation", + + "relUrl": "/pt-rPT/user/desktop.html#installation" + },"1180": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1181": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Definições | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1182": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#ui-differences", + + "relUrl": "/pt-rPT/user/desktop.html#ui-differences" + },"1183": { + "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 application. 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" + },"1184": { + "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 21 | 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" + },"1185": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1186": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#related-topics", + + "relUrl": "/pt-rPT/user/desktop.html#related-topics" + },"1187": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html", + + "relUrl": "/iw-rIL/user/desktop.html" + },"1188": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#installation", + + "relUrl": "/iw-rIL/user/desktop.html#installation" + },"1189": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1190": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | מפה | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | הגדרות | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1191": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#ui-differences", + + "relUrl": "/iw-rIL/user/desktop.html#ui-differences" + },"1192": { + "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 application. 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" + },"1193": { + "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 21 | 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" + },"1194": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1195": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#related-topics", + + "relUrl": "/iw-rIL/user/desktop.html#related-topics" + },"1196": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html", + + "relUrl": "/el-rGR/user/desktop.html" + },"1197": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#installation", + + "relUrl": "/el-rGR/user/desktop.html#installation" + },"1198": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1199": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Χάρτης | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Ρυθμίσεις | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1200": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#ui-differences", + + "relUrl": "/el-rGR/user/desktop.html#ui-differences" + },"1201": { + "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 application. 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" + },"1202": { + "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 21 | 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" + },"1203": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1204": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#related-topics", + + "relUrl": "/el-rGR/user/desktop.html#related-topics" },"1205": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html", + "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html", - "relUrl": "/nl-rNL/user/desktop.html" + "relUrl": "/ro-rRO/user/desktop.html" },"1206": { "doc": "Desktop App", "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#installation", + "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#installation", - "relUrl": "/nl-rNL/user/desktop.html#installation" + "relUrl": "/ro-rRO/user/desktop.html#installation" },"1207": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#connecting-your-radio", + "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#connecting-your-radio", - "relUrl": "/nl-rNL/user/desktop.html#connecting-your-radio" + "relUrl": "/ro-rRO/user/desktop.html#connecting-your-radio" },"1208": { "doc": "Desktop App", "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Kaart | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Instellingen | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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", + "content": "| Feature | Android | Desktop | Notițe | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Setări | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Actualizare firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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": "/nl-rNL/user/desktop.html#feature-parity" + "relUrl": "/ro-rRO/user/desktop.html#feature-parity" },"1209": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#ui-differences", + "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#ui-differences", - "relUrl": "/nl-rNL/user/desktop.html#ui-differences" + "relUrl": "/ro-rRO/user/desktop.html#ui-differences" },"1210": { "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 application. 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#built-in-documentation-browser", - "relUrl": "/nl-rNL/user/desktop.html#built-in-documentation-browser" + "relUrl": "/ro-rRO/user/desktop.html#built-in-documentation-browser" },"1211": { "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 21 | No Android SDK required for desktop-only builds | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#building-from-source", + "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#building-from-source", - "relUrl": "/nl-rNL/user/desktop.html#building-from-source" + "relUrl": "/ro-rRO/user/desktop.html#building-from-source" },"1212": { "doc": "Desktop App", "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#known-limitations", - "relUrl": "/nl-rNL/user/desktop.html#known-limitations" + "relUrl": "/ro-rRO/user/desktop.html#known-limitations" },"1213": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#related-topics", + "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#related-topics", - "relUrl": "/nl-rNL/user/desktop.html#related-topics" + "relUrl": "/ro-rRO/user/desktop.html#related-topics" },"1214": { "doc": "Desktop App", "title": "Desktop App", @@ -8563,632 +8563,632 @@ "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html", + "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html", - "relUrl": "/it-rIT/user/desktop.html" + "relUrl": "/ga-rIE/user/desktop.html" },"1224": { "doc": "Desktop App", - "title": "Installazione", + "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#installazione", + "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#installation", - "relUrl": "/it-rIT/user/desktop.html#installazione" + "relUrl": "/ga-rIE/user/desktop.html#installation" },"1225": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#connecting-your-radio", + "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#connecting-your-radio", - "relUrl": "/it-rIT/user/desktop.html#connecting-your-radio" + "relUrl": "/ga-rIE/user/desktop.html#connecting-your-radio" },"1226": { "doc": "Desktop App", "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Note | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mappa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Impostazioni | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Aggiornamento Firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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": "/it-rIT/user/desktop.html#feature-parity" + "relUrl": "/ga-rIE/user/desktop.html#feature-parity" },"1227": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#ui-differences", + "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#ui-differences", - "relUrl": "/it-rIT/user/desktop.html#ui-differences" + "relUrl": "/ga-rIE/user/desktop.html#ui-differences" },"1228": { "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 application. 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#built-in-documentation-browser", - "relUrl": "/it-rIT/user/desktop.html#built-in-documentation-browser" + "relUrl": "/ga-rIE/user/desktop.html#built-in-documentation-browser" },"1229": { "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 21 | No Android SDK required for desktop-only builds | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#building-from-source", + "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 21 | No Android SDK required for desktop-only builds | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#building-from-source", - "relUrl": "/it-rIT/user/desktop.html#building-from-source" + "relUrl": "/ga-rIE/user/desktop.html#building-from-source" },"1230": { "doc": "Desktop App", - "title": "Limitazioni conosciute", + "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#known-limitations", - "relUrl": "/it-rIT/user/desktop.html#limitazioni-conosciute" + "relUrl": "/ga-rIE/user/desktop.html#known-limitations" },"1231": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#related-topics", + "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#related-topics", - "relUrl": "/it-rIT/user/desktop.html#related-topics" + "relUrl": "/ga-rIE/user/desktop.html#related-topics" },"1232": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html", - - "relUrl": "/ar-rSA/user/desktop.html" - },"1233": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#installation", - - "relUrl": "/ar-rSA/user/desktop.html#installation" - },"1234": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1235": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | الخريطة | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | الإعدادات | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1236": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#ui-differences", - - "relUrl": "/ar-rSA/user/desktop.html#ui-differences" - },"1237": { - "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 application. 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" - },"1238": { - "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 21 | 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" - },"1239": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1240": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#related-topics", - - "relUrl": "/ar-rSA/user/desktop.html#related-topics" - },"1241": { - "doc": "Desktop App", - "title": "Desktop App", - "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html", - - "relUrl": "/sk-rSK/user/desktop.html" - },"1242": { - "doc": "Desktop App", - "title": "Installation", - "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#installation", - - "relUrl": "/sk-rSK/user/desktop.html#installation" - },"1243": { - "doc": "Desktop App", - "title": "Connecting Your Radio", - "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1244": { - "doc": "Desktop App", - "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Nastavenia | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1245": { - "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#ui-differences", - - "relUrl": "/sk-rSK/user/desktop.html#ui-differences" - },"1246": { - "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 application. 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" - },"1247": { - "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 21 | 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" - },"1248": { - "doc": "Desktop App", - "title": "Known Limitations", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1249": { - "doc": "Desktop App", - "title": "Related Topics", - "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#related-topics", - - "relUrl": "/sk-rSK/user/desktop.html#related-topics" - },"1250": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html", "relUrl": "/pl-rPL/user/desktop.html" - },"1251": { + },"1233": { "doc": "Desktop App", "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html#installation", "relUrl": "/pl-rPL/user/desktop.html#installation" - },"1252": { + },"1234": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" - },"1253": { + },"1235": { "doc": "Desktop App", "title": "Feature Parity", "content": "| Feature | Android | Desktop | Notatki | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Ustawienia | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Aktualizacja oprogramowania | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" - },"1254": { + },"1236": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html#ui-differences", "relUrl": "/pl-rPL/user/desktop.html#ui-differences" - },"1255": { + },"1237": { "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 application. 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" - },"1256": { + },"1238": { "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 21 | 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" - },"1257": { + },"1239": { "doc": "Desktop App", "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" - },"1258": { + },"1240": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html#related-topics", "relUrl": "/pl-rPL/user/desktop.html#related-topics" + },"1241": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html", + + "relUrl": "/nl-rNL/user/desktop.html" + },"1242": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#installation", + + "relUrl": "/nl-rNL/user/desktop.html#installation" + },"1243": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1244": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Kaart | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Instellingen | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1245": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#ui-differences", + + "relUrl": "/nl-rNL/user/desktop.html#ui-differences" + },"1246": { + "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 application. 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" + },"1247": { + "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 21 | 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" + },"1248": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1249": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#related-topics", + + "relUrl": "/nl-rNL/user/desktop.html#related-topics" + },"1250": { + "doc": "Desktop App", + "title": "Desktop App", + "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html", + + "relUrl": "/sv-rSE/user/desktop.html" + },"1251": { + "doc": "Desktop App", + "title": "Installation", + "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#installation", + + "relUrl": "/sv-rSE/user/desktop.html#installation" + },"1252": { + "doc": "Desktop App", + "title": "Connecting Your Radio", + "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device 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" + },"1253": { + "doc": "Desktop App", + "title": "Feature Parity", + "content": "| Feature | Android | Desktop | Anteckningar | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Karta | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Inställningar | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Uppdatering av fast programvara | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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" + },"1254": { + "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#ui-differences", + + "relUrl": "/sv-rSE/user/desktop.html#ui-differences" + },"1255": { + "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 application. 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" + },"1256": { + "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 21 | 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" + },"1257": { + "doc": "Desktop App", + "title": "Known Limitations", + "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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" + },"1258": { + "doc": "Desktop App", + "title": "Related Topics", + "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#related-topics", + + "relUrl": "/sv-rSE/user/desktop.html#related-topics" },"1259": { - "doc": "桌面版應用程式", - "title": "桌面版應用程式", - "content": "Meshtastic 桌面版應用程式透過 Kotlin Multiplatform 與 Android 版共用核心程式碼庫。 大多數功能在 Linux、macOS 及 Windows 上的運作方式完全相同。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html", + "doc": "デスクトップアプリ", + "title": "デスクトップアプリ", + "content": "Meshtastic デスクトップアプリケーションは、Kotlin Multiplatform を通じて、コアのコードベースを Android と共有しています。 ほとんどの機能は、Linux、macOS、Windows で同じように動作します。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html", - "relUrl": "/zh-rTW/user/desktop.html" + "relUrl": "/ja-rJP/user/desktop.html" },"1260": { - "doc": "桌面版應用程式", - "title": "安裝", - "content": "Linux . | 從發布頁面下載.deb 或.AppImage 安裝套件 | 或使用 ./gradlew :desktopApp:run 從原始碼自行建置 | . macOS . | 從發布頁面下載.dmg 安裝套件 | 或從原始碼自行建置 | . Windows . | 從發布頁面下載.msi 安裝程式 | 或從原始碼自行建置 | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E5%AE%89%E8%A3%9D", + "doc": "デスクトップアプリ", + "title": "インストール", + "content": "Linux . | リリースページから .deb または .AppImage パッケージをダウンロードします | または、./gradlew :desktopApp:run を使ってソースからビルドします | . macOS . | リリースから .dmg パッケージをダウンロードします | または、ソースからビルドします | . Windows . | リリースから .msi インストーラーをダウンロードします | または、ソースからビルドします | . ", + "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": "/zh-rTW/user/desktop.html#安裝" + "relUrl": "/ja-rJP/user/desktop.html#インストール" },"1261": { - "doc": "桌面版應用程式", - "title": "連接您的無線電裝置", - "content": "USB 序列埠（主要方式） . 桌面版上最穩定可靠的連線方式： . | 請使用 USB 傳輸線連接您的 Meshtastic 無線電裝置。 | 應用程式應會自動偵測序列埠。 | 若未自動偵測到，請從連線選單中手動選取正確的序列埠。 | . TCP/IP . 若使用網路連線的無線電裝置： . | 輸入無線電裝置的 IP 位址與連接埠（預設：4403）。 | 點選「連線」。 | . 藍牙（BLE） . 桌面版透過 Kable 函式庫支援藍牙低功耗： . | 請確認您的系統配備藍牙介面卡。 | 應用程式將自動掃描附近的 Meshtastic 無線電裝置。 | 從連線畫面中選取您的裝置。 | . ", - "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", + "doc": "デスクトップアプリ", + "title": "無線機を接続する", + "content": "USB シリアル（主要） . デスクトップで最も信頼できる接続方法です： . | USB ケーブルで Meshtastic 無線機を接続します。 | アプリがシリアルポートを自動的に検出します。 | 検出されない場合は、接続メニューから正しいシリアルポートを選択します。 | . TCP/IP . ネットワーク接続された無線機の場合： . | 無線機の IP アドレスとポート（既定：4403）を入力します。 | 「接続」をクリックします。 | . Bluetooth（BLE） . Bluetooth Low Energy は、Kable ライブラリを通じてデスクトップでサポートされています： . | システムに Bluetooth アダプターがあることを確認します。 | アプリが近くの Meshtastic 無線機を自動的にスキャンします。 | 接続画面からデバイスを選択します。 | . ", + "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": "/zh-rTW/user/desktop.html#連接您的無線電裝置" + "relUrl": "/ja-rJP/user/desktop.html#無線機を接続する" },"1262": { - "doc": "桌面版應用程式", - "title": "功能對等性", - "content": "| 功能 | Android | 桌面版 | 備註 | . | 訊息傳送 | ✓ | ✓ | 完全對等 | . | 節點清單 | ✓ | ✓ | 完全對等 | . | 地圖 | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | 設定 | ✓ | ✓ | 完全對等 | . | 藍牙（BLE） | ✓ | ✓ | 桌面版透過 Kable 支援 | . | 韌體更新 | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | 通知 | ✓ | ✓ | 原生作業系統通知 | . | 小工具 | ✓ | ✗ | 僅限 Android | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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", + "doc": "デスクトップアプリ", + "title": "機能の対応状況", + "content": "| 機能 | Android | デスクトップ | 備考 | . | メッセージング | ✓ | ✓ | 完全対応 | . | ノードリスト | ✓ | ✓ | 完全対応 | . | マップ | ✓ | ◐ | マップタブはデスクトップにも存在しますが、インタラクティブなマップビューは Android のみです | . | 設定 | ✓ | ✓ | 完全対応 | . | Bluetooth（BLE） | ✓ | ✓ | デスクトップでは Kable 経由 | . | ファームウェアの更新 | ✓ | ✓ | アプリ内の USB、BLE、Wi-Fi（ESP32）更新はすべて、Android と同じように動作します | . | 通知 | ✓ | ✓ | OS ネイティブの通知 | . | ウィジェット | ✓ | ✗ | Android のみ | . | Android Auto | ✓ | ✗ | Android のみ。デスクトップや iOS では利用できません | . | 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": "/zh-rTW/user/desktop.html#功能對等性" + "relUrl": "/ja-rJP/user/desktop.html#機能の対応状況" },"1263": { - "doc": "桌面版應用程式", - "title": "介面差異", - "content": "桌面版應用程式採用相同的 Compose Multiplatform 介面，並針對較大螢幕與桌面操作方式進行調整。 . 鍵盤快速鍵 . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | 快速鍵 | 動作 | . | ⌘/Ctrl+Q | 結束應用程式 | . | ⌘/Ctrl+, | 開啟設定 | . | ⌘/Ctrl+1 | 切換至訊息頁籤 | . | ⌘/Ctrl+2 | 切換至節點頁籤 | . | ⌘/Ctrl+3 | 切換至地圖頁籤 | . | ⌘/Ctrl+4 | 切換至連線頁籤 | . | ⌘/Ctrl+/ | Open About | . 視窗與系統匣 . | 調整視窗大小 — 響應式版面配置可依視窗尺寸自動調整 | 系統匣 — 可最小化至系統匣，於背景持續進行 mesh 網路操作 | 匣列選單 — 在系統匣圖示上按右鍵，可顯示視窗或結束程式 | 滑鼠互動 — 支援停駐狀態與標準桌面導覽操作 | . 通知偏好設定 . 桌面版應用程式提供應用程式內的切換開關，可控制顯示哪些通知 — 包含訊息、新節點及低電量警示。 請在應用程式中前往「設定 → 通知」進行設定。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E4%BB%8B%E9%9D%A2%E5%B7%AE%E7%95%B0", + "doc": "デスクトップアプリ", + "title": "UI の違い", + "content": "デスクトップアプリは、同じ Compose Multiplatform の UI を使用し、大きな画面とデスクトップ操作に合わせて調整されています。 . キーボードショートカット . ショートカットは、macOS では ⌘（Command）、Windows と Linux では Ctrl を使用します。 （Super／Windows キーは割り当てられていません。） . | ショートカット | 操作 | . | ⌘/Ctrl+Q | アプリケーションを終了 | . | ⌘/Ctrl+, | 設定を開く | . | ⌘/Ctrl+1 | メッセージタブに切り替え | . | ⌘/Ctrl+2 | ノードタブに切り替え | . | ⌘/Ctrl+3 | マップタブに切り替え | . | ⌘/Ctrl+4 | 接続タブに切り替え | . | ⌘/Ctrl+/ | バージョン情報を開く | . ウィンドウとシステムトレイ . | ウィンドウのサイズ変更：レスポンシブなレイアウトがウィンドウの寸法に合わせて調整されます | システムトレイ：システムトレイに最小化して、バックグラウンドでメッシュを動作させます | トレイメニュー：トレイアイコンを右クリックして、ウィンドウ表示または終了します | マウス操作：ホバー状態と標準的なデスクトップのナビゲーション | . 通知の設定 . デスクトップアプリには、どの通知を表示するか（メッセージ、新しいノード、バッテリー低下の警告）を制御するアプリ内トグルがあります。 これらには、アプリ内の「設定 → 通知」からアクセスします。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html#ui-%E3%81%AE%E9%81%95%E3%81%84", - "relUrl": "/zh-rTW/user/desktop.html#介面差異" + "relUrl": "/ja-rJP/user/desktop.html#ui-の違い" },"1264": { - "doc": "桌面版應用程式", - "title": "內建文件瀏覽器", - "content": "桌面版應用程式內建文件瀏覽器，無需離開應用程式即可快速存取說明內容。 . 瀏覽器支援跨所有文件的全文搜尋： . 各文件頁面以完整格式呈現： . ", - "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", + "doc": "デスクトップアプリ", + "title": "組み込みのドキュメントブラウザー", + "content": "デスクトップアプリには、アプリケーションを離れることなくヘルプコンテンツにすばやくアクセスできる、組み込みのドキュメントブラウザーが含まれています。 . ブラウザーは、すべてのドキュメントを対象とした全文検索に対応しています： . 個々のドキュメントページは、完全な書式で表示されます： . ", + "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": "/zh-rTW/user/desktop.html#內建文件瀏覽器" + "relUrl": "/ja-rJP/user/desktop.html#組み込みのドキュメントブラウザー" },"1265": { - "doc": "桌面版應用程式", - "title": "從原始碼建置", - "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . 需求： . | JDK 21 | 純桌面版建置不需要 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", + "doc": "デスクトップアプリ", + "title": "ソースからビルドする", + "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . 要件： . | JDK 21 | デスクトップのみのビルドに 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": "/zh-rTW/user/desktop.html#從原始碼建置" + "relUrl": "/ja-rJP/user/desktop.html#ソースからビルドする" },"1266": { - "doc": "桌面版應用程式", - "title": "已知限制", - "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 部分 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", + "doc": "デスクトップアプリ", + "title": "既知の制限", + "content": ". | インタラクティブなマップビューは Android のみです。マップタブは存在しますが、デスクトップではマップが表示されません。 | 一部の 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": "/zh-rTW/user/desktop.html#已知限制" + "relUrl": "/ja-rJP/user/desktop.html#既知の制限" },"1267": { - "doc": "桌面版應用程式", - "title": "相關主題", - "content": ". | 〔連線〕(connections) — 連線方式概覽 | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C", + "doc": "デスクトップアプリ", + "title": "関連トピック", + "content": ". | コネクション：接続方法の概要 | ファームウェア更新：USB、BLE、Wi-Fi 更新はすべて、Android と同じように動作します | . ", + "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": "/zh-rTW/user/desktop.html#相關主題" + "relUrl": "/ja-rJP/user/desktop.html#関連トピック" },"1268": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html", + "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html", - "relUrl": "/cs-rCZ/user/desktop.html" + "relUrl": "/hu-rHU/user/desktop.html" },"1269": { "doc": "Desktop App", "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#installation", + "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#installation", - "relUrl": "/cs-rCZ/user/desktop.html#installation" + "relUrl": "/hu-rHU/user/desktop.html#installation" },"1270": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#connecting-your-radio", + "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#connecting-your-radio", - "relUrl": "/cs-rCZ/user/desktop.html#connecting-your-radio" + "relUrl": "/hu-rHU/user/desktop.html#connecting-your-radio" },"1271": { "doc": "Desktop App", "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Poznámka | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Nastavení | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Aktualizace firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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", + "content": "| Feature | Android | Desktop | Jegyzetek | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Térkép | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Beállítások | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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": "/cs-rCZ/user/desktop.html#feature-parity" + "relUrl": "/hu-rHU/user/desktop.html#feature-parity" },"1272": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#ui-differences", + "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#ui-differences", - "relUrl": "/cs-rCZ/user/desktop.html#ui-differences" + "relUrl": "/hu-rHU/user/desktop.html#ui-differences" },"1273": { "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 application. 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#built-in-documentation-browser", - "relUrl": "/cs-rCZ/user/desktop.html#built-in-documentation-browser" + "relUrl": "/hu-rHU/user/desktop.html#built-in-documentation-browser" },"1274": { "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 21 | No Android SDK required for desktop-only builds | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#building-from-source", + "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 21 | No Android SDK required for desktop-only builds | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#building-from-source", - "relUrl": "/cs-rCZ/user/desktop.html#building-from-source" + "relUrl": "/hu-rHU/user/desktop.html#building-from-source" },"1275": { "doc": "Desktop App", "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#known-limitations", - "relUrl": "/cs-rCZ/user/desktop.html#known-limitations" + "relUrl": "/hu-rHU/user/desktop.html#known-limitations" },"1276": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#related-topics", + "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#related-topics", - "relUrl": "/cs-rCZ/user/desktop.html#related-topics" + "relUrl": "/hu-rHU/user/desktop.html#related-topics" },"1277": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html", + "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html", - "relUrl": "/fr-rFR/user/desktop.html" + "relUrl": "/ht-rHT/user/desktop.html" },"1278": { "doc": "Desktop App", "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#installation", + "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#installation", - "relUrl": "/fr-rFR/user/desktop.html#installation" + "relUrl": "/ht-rHT/user/desktop.html#installation" },"1279": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#connecting-your-radio", + "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#connecting-your-radio", - "relUrl": "/fr-rFR/user/desktop.html#connecting-your-radio" + "relUrl": "/ht-rHT/user/desktop.html#connecting-your-radio" },"1280": { "doc": "Desktop App", "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Carte | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Réglages | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Mise à jour du firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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": "/fr-rFR/user/desktop.html#feature-parity" + "relUrl": "/ht-rHT/user/desktop.html#feature-parity" },"1281": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#ui-differences", + "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#ui-differences", - "relUrl": "/fr-rFR/user/desktop.html#ui-differences" + "relUrl": "/ht-rHT/user/desktop.html#ui-differences" },"1282": { "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 application. 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#built-in-documentation-browser", - "relUrl": "/fr-rFR/user/desktop.html#built-in-documentation-browser" + "relUrl": "/ht-rHT/user/desktop.html#built-in-documentation-browser" },"1283": { "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 21 | No Android SDK required for desktop-only builds | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#building-from-source", + "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#building-from-source", - "relUrl": "/fr-rFR/user/desktop.html#building-from-source" + "relUrl": "/ht-rHT/user/desktop.html#building-from-source" },"1284": { "doc": "Desktop App", "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#known-limitations", - "relUrl": "/fr-rFR/user/desktop.html#known-limitations" + "relUrl": "/ht-rHT/user/desktop.html#known-limitations" },"1285": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#related-topics", + "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#related-topics", - "relUrl": "/fr-rFR/user/desktop.html#related-topics" + "relUrl": "/ht-rHT/user/desktop.html#related-topics" },"1286": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html", + "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html", - "relUrl": "/zh-rCN/user/desktop.html" + "relUrl": "/gl-rES/user/desktop.html" },"1287": { "doc": "Desktop App", - "title": "安装", + "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#%E5%AE%89%E8%A3%85", + "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#installation", - "relUrl": "/zh-rCN/user/desktop.html#安装" + "relUrl": "/gl-rES/user/desktop.html#installation" },"1288": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#connecting-your-radio", + "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#connecting-your-radio", - "relUrl": "/zh-rCN/user/desktop.html#connecting-your-radio" + "relUrl": "/gl-rES/user/desktop.html#connecting-your-radio" },"1289": { "doc": "Desktop App", "title": "Feature Parity", - "content": "| Feature | Android | Desktop | 注 | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | 地图 | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | 设置 | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | 固件更新 | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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": "/zh-rCN/user/desktop.html#feature-parity" + "relUrl": "/gl-rES/user/desktop.html#feature-parity" },"1290": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#ui-differences", - "relUrl": "/zh-rCN/user/desktop.html#ui-differences" + "relUrl": "/gl-rES/user/desktop.html#ui-differences" },"1291": { "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 application. 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", + "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#built-in-documentation-browser", - "relUrl": "/zh-rCN/user/desktop.html#built-in-documentation-browser" + "relUrl": "/gl-rES/user/desktop.html#built-in-documentation-browser" },"1292": { "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 21 | No Android SDK required for desktop-only builds | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#building-from-source", + "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#building-from-source", - "relUrl": "/zh-rCN/user/desktop.html#building-from-source" + "relUrl": "/gl-rES/user/desktop.html#building-from-source" },"1293": { "doc": "Desktop App", "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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", + "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#known-limitations", - "relUrl": "/zh-rCN/user/desktop.html#known-limitations" + "relUrl": "/gl-rES/user/desktop.html#known-limitations" },"1294": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#related-topics", + "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#related-topics", - "relUrl": "/zh-rCN/user/desktop.html#related-topics" + "relUrl": "/gl-rES/user/desktop.html#related-topics" },"1295": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/srp/user/desktop.html", + "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html", - "relUrl": "/srp/user/desktop.html" + "relUrl": "/tr-rTR/user/desktop.html" },"1296": { "doc": "Desktop App", "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/srp/user/desktop.html#installation", + "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#installation", - "relUrl": "/srp/user/desktop.html#installation" + "relUrl": "/tr-rTR/user/desktop.html#installation" },"1297": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", - "url": "/Meshtastic-Android/main/srp/user/desktop.html#connecting-your-radio", + "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#connecting-your-radio", - "relUrl": "/srp/user/desktop.html#connecting-your-radio" + "relUrl": "/tr-rTR/user/desktop.html#connecting-your-radio" },"1298": { "doc": "Desktop App", "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Белешке | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Мапа | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Подешавања | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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", + "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Harita | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Ayarlar | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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": "/srp/user/desktop.html#feature-parity" + "relUrl": "/tr-rTR/user/desktop.html#feature-parity" },"1299": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/srp/user/desktop.html#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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#ui-differences", - "relUrl": "/srp/user/desktop.html#ui-differences" + "relUrl": "/tr-rTR/user/desktop.html#ui-differences" },"1300": { "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 application. 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#built-in-documentation-browser", - "relUrl": "/srp/user/desktop.html#built-in-documentation-browser" + "relUrl": "/tr-rTR/user/desktop.html#built-in-documentation-browser" },"1301": { "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 21 | No Android SDK required for desktop-only builds | . ", - "url": "/Meshtastic-Android/main/srp/user/desktop.html#building-from-source", + "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#building-from-source", - "relUrl": "/srp/user/desktop.html#building-from-source" + "relUrl": "/tr-rTR/user/desktop.html#building-from-source" },"1302": { "doc": "Desktop App", "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#known-limitations", - "relUrl": "/srp/user/desktop.html#known-limitations" + "relUrl": "/tr-rTR/user/desktop.html#known-limitations" },"1303": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/srp/user/desktop.html#related-topics", + "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#related-topics", - "relUrl": "/srp/user/desktop.html#related-topics" + "relUrl": "/tr-rTR/user/desktop.html#related-topics" },"1304": { "doc": "Desktop App", "title": "Desktop App", "content": "The Meshtastic Desktop application shares its core codebase with Android via Kotlin Multiplatform. Most features work identically on Linux, macOS, and Windows. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html", + "url": "/Meshtastic-Android/main/es-rES/user/desktop.html", - "relUrl": "/sq-rAL/user/desktop.html" + "relUrl": "/es-rES/user/desktop.html" },"1305": { "doc": "Desktop App", "title": "Installation", "content": "Linux . | Download the .deb or .AppImage package from the releases page | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from releases | Or build from source | . Windows . | Download the .msi installer from releases | Or build from source | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#installation", + "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#installation", - "relUrl": "/sq-rAL/user/desktop.html#installation" + "relUrl": "/es-rES/user/desktop.html#installation" },"1306": { "doc": "Desktop App", "title": "Connecting Your Radio", "content": "USB Serial (Primary) . The most reliable connection method on Desktop: . | Connect your Meshtastic radio via USB cable. | The app should detect the serial port automatically. | If not detected, select the correct serial 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 device from the Connect screen. | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#connecting-your-radio", + "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#connecting-your-radio", - "relUrl": "/sq-rAL/user/desktop.html#connecting-your-radio" + "relUrl": "/es-rES/user/desktop.html#connecting-your-radio" },"1307": { "doc": "Desktop App", "title": "Feature Parity", - "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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", + "content": "| Feature | Android | Desktop | Notas | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ◐ | Map tab exists on desktop, but the interactive map view is Android-only | . | Ajustes | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Actualización de firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update all work the same as Android | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | Android Auto | ✓ | ✗ | Android-only — not available on Desktop or iOS | . | 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": "/sq-rAL/user/desktop.html#feature-parity" + "relUrl": "/es-rES/user/desktop.html#feature-parity" },"1308": { "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 application | . | ⌘/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 — minimize to system tray for background mesh operation | Tray menu — right-click the tray icon to show window or quit | Mouse interaction — hover states and standard desktop navigation | . Notification Preferences . The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from Settings → Notifications within the app. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#ui-differences", + "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#ui-differences", - "relUrl": "/sq-rAL/user/desktop.html#ui-differences" + "relUrl": "/es-rES/user/desktop.html#ui-differences" },"1309": { "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 application. 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", + "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#built-in-documentation-browser", - "relUrl": "/sq-rAL/user/desktop.html#built-in-documentation-browser" + "relUrl": "/es-rES/user/desktop.html#built-in-documentation-browser" },"1310": { "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 21 | No Android SDK required for desktop-only builds | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#building-from-source", + "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#building-from-source", - "relUrl": "/sq-rAL/user/desktop.html#building-from-source" + "relUrl": "/es-rES/user/desktop.html#building-from-source" },"1311": { "doc": "Desktop App", "title": "Known Limitations", "content": ". | The interactive map view is Android-only — the Map tab is present but does not render a map on desktop | 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", + "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#known-limitations", - "relUrl": "/sq-rAL/user/desktop.html#known-limitations" + "relUrl": "/es-rES/user/desktop.html#known-limitations" },"1312": { "doc": "Desktop App", "title": "Related Topics", "content": ". | Connections — connection methods overview | Firmware Updates — USB, BLE, and Wi-Fi update all work the same as on Android | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#related-topics", + "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#related-topics", - "relUrl": "/sq-rAL/user/desktop.html#related-topics" + "relUrl": "/es-rES/user/desktop.html#related-topics" },"1313": { "doc": "Developer Guide", "title": "Developer Guide", @@ -9211,1629 +9211,1629 @@ "relUrl": "/en/developer.html#whats-new-for-developers" },"1316": { - "doc": "Discovery", - "title": "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 radio 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" - },"1317": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/is-rIS/user/discovery.html#local-mesh-discovery-scanner" - },"1318": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#mesh-beacon", - - "relUrl": "/is-rIS/user/discovery.html#mesh-beacon" - },"1319": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#manual-exploration", - - "relUrl": "/is-rIS/user/discovery.html#manual-exploration" - },"1320": { - "doc": "Discovery", - "title": "Ferilkönnun", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#ferilk%C3%B6nnun", - - "relUrl": "/is-rIS/user/discovery.html#ferilkönnun" - },"1321": { - "doc": "Discovery", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#neighbor-info", - - "relUrl": "/is-rIS/user/discovery.html#neighbor-info" - },"1322": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/is-rIS/user/discovery.html#node-list-as-a-discovery-tool" - },"1323": { - "doc": "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" - },"1324": { - "doc": "探索", - "title": "探索", - "content": "探索ツールは、メッシュネットワークがどのようにつながっているか（どのノードが互いに受信できるか、メッセージがどの経路を通るか、ボトルネックや弱いリンクがどこにあるか）を把握するのに役立ちます。 . アプリは、互いを補完する 2 つの方法を提供します： . | ローカルメッシュ探索（スキャナー）：接続中の無線機をさまざまな LoRa プリセットで順に切り替え、それぞれで受信し、あなたの場所でどのプリセットが最も性能が良いかをランク付けする自動モードです。 | 手動での探索：ルート追跡、隣接ノード情報、ノードリスト。特定の経路やトポロジーを調べるために、いつでも使えます。 | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html", - - "relUrl": "/ja-rJP/user/discovery.html" - },"1325": { - "doc": "探索", - "title": "ローカルメッシュ探索（スキャナー）", - "content": "ローカルメッシュ探索は、あなたの場所に最適な LoRa モデムプリセットを見つけ、各プリセットでどのノードがアクティブかを確認できる、専用のスキャンモードです。 接続中の無線機を、選択した 1 つ以上のプリセットで順に切り替え、パケットを収集するために各プリセットで一定時間受信（「滞在」）し、その後、結果を分析してランク付けします。 . 「設定 → 詳細設定 → ローカルメッシュ探索」から開きます。 デスクトップでは、独自の「設定 → ローカルメッシュ探索」の項目があります。 . ⚠️ 注意： 探索は、スキャン中に無線機の LoRa 設定を一時的に変更し、完了時に元の構成に戻します。 スキャンを実行するには、デバイスが接続されている必要があります。 . スキャンを設定する . 開始する前に、次のコントロールを設定します： . | コントロール | 説明 | . | LoRa プリセットの選択 | スキャンするプリセットを 1 つ以上選択します。 探索は、選択した各プリセットに順番に滞在します。 | . | 滞在時間 | 各プリセットで受信する時間。 1、5、15、30、45、60、90、120、180 分から選択します。 滞在時間を長くすると、より多くのパケットを収集してより明確な状況が分かりますが、時間もかかります。 | . | 画面をスリープさせない | 長いスキャン中に画面がスリープするのを防ぐ、任意のトグルです。 | . 「開始」ボタンは、スキャンを実行できるようになるまで（理由の説明とともに）無効のままです。 無効になる主な理由： . | デバイスが接続されていない。 | スキャンするプリセットが選択されていない。 | 選択したプリセットが、ハードウェアが対応していない 2.4 GHz を使用している。 | . リアルタイムの進行状況 . スキャンの実行中、探索は現在の段階を表示します： . | 段階 | 実行中の内容 | . | 準備中 | 現在の構成を保存し、スキャンの準備をしています。 | . | <preset> に切り替え中 | テストする次のプリセットに無線機を切り替えています。 | . | 再接続中 | プリセット変更後に接続を再確立しています。 | . | 滞在 | 現在のプリセットで受信してパケットを収集しており、次のステップまでのカウントダウンが表示されます。 | . | 分析 | 収集したパケットを処理し、プリセットをランク付けしています。 | . | 復元中 | 元の LoRa 構成に戻しています。 | . 結果の見方 . スキャンが完了すると、探索はテストした各プリセットのプリセット別の結果カードと、全体の概要を表示します。 . メトリクスには次が含まれます： . | メトリクス | 分かること | . | RF の健全性 | そのプリセットにおける無線環境の総合的な品質。 | . | チャンネル利用率 | 滞在中に電波がどれだけ混雑していたか。 | . | 電波利用時間 | 観測された送信時間。 | . | 直接受信と中継ノード | 直接受信できたメッシュノードと、中継経由のノードの数。 | . | 不良／重複パケット | 破損したパケットと繰り返されたパケットの数で、輻輳や干渉を示します。 | . 結果から利用できる追加機能： . | スキャン履歴：後で見直せる保存済みのセッション。過去のスキャンを表示または削除できます。 | 探索マップ：スキャン中に見つかったノードのマップ。 | レポートのエクスポート：Android では PDF として、他のプラットフォームではテキストとしてレポートをエクスポートします。 | . 💡 ヒント： Android では、探索が結果のオンデバイス AI 要約（Gemini Nano）を生成できます。 オンデバイスのモデルが利用できない場合は、代わりにアルゴリズムによる要約が使われるため、常にスキャンの読みやすい解釈が得られます。 . ", - "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#ローカルメッシュ探索スキャナー" - },"1326": { - "doc": "探索", - "title": "メッシュビーコン", - "content": "メッシュビーコンを使うと、ノードが他のノードを自分のメッシュに招待できます。 ビーコンを発信するノードは、招待を定期的にブロードキャストします（任意でチャンネル、リージョン、モデムプリセットを告知）。近くのデバイスは、設定を共有する前でもこれを受信できます。 . 「設定 → モジュール設定 → メッシュビーコン」で設定します： . | ビーコンを受信：他のノードがブロードキャストする招待を受け取ります。 | ビーコンを発信：一定間隔で自分の招待を送信します。任意でメッセージと提示するチャンネルを設定できます。 | . 受信した招待は、探索画面に「メッシュへの招待」カードとして表示されます。 各カードには、送信者のメッセージと、提示されたチャンネル・リージョン・プリセット・信号品質が表示され、次の操作ができます： . | 参加：提示されたチャンネルとプリセットに切り替えます（無線機を再調整して再起動します）。 提示内容が現在の周波数スロットと一致する場合は、再起動なしで追加できる「チャンネルを追加」の操作が表示されます。 | 探索：提示されたプリセットで探索スキャンを開始し、参加する前にそのメッシュを調べられます（ビーコンがプリセットを提示している場合のみ表示）。 | 閉じる：招待を無視します。 | . ビーコンが告知したチャンネルは、スキャン設定にも「ビーコンのチャンネル」として表示されます。選択すると、スキャン対象に含められます。 . ", - "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#メッシュビーコン" - },"1327": { - "doc": "探索", - "title": "手動での探索", - "content": "以下のツールは、ノードリストとノードの詳細画面からいつでも利用できます。 完全なスキャンと併用して、またはその代わりに、特定の経路を調べてトポロジーの全体像を組み立てるのに使えます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E6%89%8B%E5%8B%95%E3%81%A7%E3%81%AE%E6%8E%A2%E7%B4%A2", - - "relUrl": "/ja-rJP/user/discovery.html#手動での探索" - },"1328": { - "doc": "探索", - "title": "ルート追跡", - "content": "ルート追跡は、メッセージが自分のノードから、メッシュ上の他の任意のノードへ通る正確な経路を明らかにします。 接続の問題をデバッグするのに、最も役立つツールです。 . ルート追跡を実行する . | 「ノード」に移動し、追跡したいノードをタップします。 | ノードの詳細画面で、「ルート追跡」をタップします。 | アプリがルート追跡の要求を送信し、応答を待ちます。 | 結果には、各ホップが順番に、各段階の信号品質とともに表示されます。 | . 結果の見方 . ルート追跡の結果は次のように表示されます： . 自分 → ノード A (SNR: 8.5, RSSI: -95) → ノード B (SNR: 5.2, RSSI: -108) → ターゲット . 各ホップは、メッセージを転送した中継ノードを表します。 各ホップの SNR と RSSI の値から、その特定の区間のリンク品質が分かります。 . | 確認すべき点 | 意味 | . | すべてのホップが良い SNR（−7 dB 以上、緑）を示す | 健全な経路。メッセージが確実に流れます | . | 1 つのホップが悪い SNR（−15 dB 未満、赤）を示す | 弱いリンク。この中継区間は脆弱です | . | ホップ数が多い（4 以上） | 長い経路。短くするためにノードの再配置を検討してください | . | 再試行で経路が変わる | メッシュが適応しています。複数の経路が存在します（これは良いことです！） | . 💡 ヒント： ルート追跡を数分間かけて何度か実行してください。 経路が変わる場合、メッシュには冗長な経路があり、よくつながったネットワークの兆候です。 . ルート追跡によるトラブルシューティング . | 「経路が見つかりません」：対象のノードがオフラインか、圏外か、別のチャンネルにいる可能性があります。 両方のノードが、同じ暗号化鍵を持つチャンネルを少なくとも 1 つ共有しているか確認してください。 | ルート追跡がタイムアウトする：経路が長すぎる（ホップ数上限を超える）か、中継ノードが混雑している可能性があります。 「設定 → LoRa 設定」でホップ数上限を増やしてみてください。 | 非対称な経路：A→B のルート追跡は、B→A とは異なる経路を通ることがあります。 これは正常です。電波の伝搬は常に対称とは限りません。 | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E3%83%AB%E3%83%BC%E3%83%88%E8%BF%BD%E8%B7%A1", - - "relUrl": "/ja-rJP/user/discovery.html#ルート追跡" - },"1329": { - "doc": "探索", - "title": "隣接ノード情報", - "content": "隣接ノード情報モジュールを使うと、各ノードが直接受信できる（シングルホップの）ノードのリストをブロードキャストできます。 複数のノードが隣接ノードのリストを共有すると、メッシュ全体のトポロジーマップを組み立てられます。 . 隣接ノード情報を有効にする . | 「設定 → モジュール設定 → 隣接ノード情報」に移動します。 | モジュールを有効にします。 | ブロードキャスト間隔を設定します（デフォルト：900 秒／15 分）。 | . 有効にすると、ノードは隣接ノードのテーブルを定期的にブロードキャストします。 隣接ノード情報を有効にしている他のノードも、同じことを行います。 . 隣接ノードのデータを表示する . | 任意のノードの詳細画面を開き、「隣接ノード」セクションを探します。 | 各隣接ノードの項目には、直接受信したノードとその信号品質が表示されます。 | 複数のノードの隣接ノードデータを組み合わせて、メッシュ全体のトポロジーを把握します。 | . ⚠️ 注意： 隣接ノード情報は、有効にした各ノードが隣接ノードのリストを定期的にブロードキャストするため、電波利用時間の消費が増えます。 ノードの多い混雑したメッシュでは、輻輳を避けるために、より長いブロードキャスト間隔（3600 秒以上）を検討してください。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.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/discovery.html#隣接ノード情報" - },"1330": { - "doc": "探索", - "title": "探索ツールとしてのノードリスト", - "content": "ノードリスト自体も、絞り込みと並べ替えの機能を効果的に使えば、強力な探索ツールになります。 . 新しいノードを見つける . | 「最後の通信」で並べ替えると、最近アクティブだったノードが先頭に表示されます。 | 「不明なノードを含む」を有効にすると、メッシュに現れたもののまだユーザー情報を送信していないノードが表示されます。これらは、電源を入れたばかりのデバイスであることがよくあります。 | . 接続性を評価する . | 「ホップ数」で並べ替えると、直接到達できるノード（0 ホップ）と中継されるノードが分かります。 | 「距離」で並べ替えると、近くのノードを見つけて、到達できるか確認できます。 | 「MQTT を除外」を使うと、（インターネットブリッジ経由ではなく）無線で到達できるノードに絞り込めます。 | . インフラの監査 . | 「インフラを除外」を無効にすると、ルーター、ルーター・レイト、クライアント・ベースのノードが表示されます。 | 信号品質と最後の通信時刻を確認して、インフラのノードが健全であることを確かめます。 | . 絞り込みと並べ替えのオプションの詳細については、ノード を参照してください。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E6%8E%A2%E7%B4%A2%E3%83%84%E3%83%BC%E3%83%AB%E3%81%A8%E3%81%97%E3%81%A6%E3%81%AE%E3%83%8E%E3%83%BC%E3%83%89%E3%83%AA%E3%82%B9%E3%83%88", - - "relUrl": "/ja-rJP/user/discovery.html#探索ツールとしてのノードリスト" - },"1331": { - "doc": "探索", - "title": "メッシュ探索のヒント", - "content": ". | まずルート追跡から：特定の経路について、すぐに役立つ情報が得られます。 | 主要なノードで隣接ノード情報を有効に：特にルーターやリピーターで有効にして、バックボーンの全体像を組み立てます。 | マップを確認：マップ 上のノードの位置と信号データを組み合わせると、なぜあるリンクは強く、別のリンクは弱いのかが分かります。 | 信号を時系列で比較：信号メーター のガイドを使って、SNR と RSSI の値を正しく解釈します。 | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E3%83%A1%E3%83%83%E3%82%B7%E3%83%A5%E6%8E%A2%E7%B4%A2%E3%81%AE%E3%83%92%E3%83%B3%E3%83%88", - - "relUrl": "/ja-rJP/user/discovery.html#メッシュ探索のヒント" - },"1332": { - "doc": "Discovery", - "title": "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 radio 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" - },"1333": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/ca-rES/user/discovery.html#local-mesh-discovery-scanner" - },"1334": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#mesh-beacon", - - "relUrl": "/ca-rES/user/discovery.html#mesh-beacon" - },"1335": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#manual-exploration", - - "relUrl": "/ca-rES/user/discovery.html#manual-exploration" - },"1336": { - "doc": "Discovery", - "title": "Traçar ruta", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#tra%C3%A7ar-ruta", - - "relUrl": "/ca-rES/user/discovery.html#traçar-ruta" - },"1337": { - "doc": "Discovery", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#neighbor-info", - - "relUrl": "/ca-rES/user/discovery.html#neighbor-info" - },"1338": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/ca-rES/user/discovery.html#node-list-as-a-discovery-tool" - },"1339": { - "doc": "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" - },"1340": { - "doc": "Discovery", - "title": "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 radio 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" - },"1341": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/sr-rLatn/user/discovery.html#local-mesh-discovery-scanner" - },"1342": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#mesh-beacon", - - "relUrl": "/sr-rLatn/user/discovery.html#mesh-beacon" - },"1343": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#manual-exploration", - - "relUrl": "/sr-rLatn/user/discovery.html#manual-exploration" - },"1344": { - "doc": "Discovery", - "title": "Праћење руте", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.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/discovery.html#праћење-руте" - },"1345": { - "doc": "Discovery", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#neighbor-info", - - "relUrl": "/sr-rLatn/user/discovery.html#neighbor-info" - },"1346": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/sr-rLatn/user/discovery.html#node-list-as-a-discovery-tool" - },"1347": { - "doc": "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" - },"1348": { - "doc": "Discovery", - "title": "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 radio 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" - },"1349": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/ko-rKR/user/discovery.html#local-mesh-discovery-scanner" - },"1350": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#mesh-beacon", - - "relUrl": "/ko-rKR/user/discovery.html#mesh-beacon" - },"1351": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#manual-exploration", - - "relUrl": "/ko-rKR/user/discovery.html#manual-exploration" - },"1352": { - "doc": "Discovery", - "title": "추적 루트", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#%EC%B6%94%EC%A0%81-%EB%A3%A8%ED%8A%B8", - - "relUrl": "/ko-rKR/user/discovery.html#추적-루트" - },"1353": { - "doc": "Discovery", - "title": "이웃 정보", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#%EC%9D%B4%EC%9B%83-%EC%A0%95%EB%B3%B4", - - "relUrl": "/ko-rKR/user/discovery.html#이웃-정보" - },"1354": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/ko-rKR/user/discovery.html#node-list-as-a-discovery-tool" - },"1355": { - "doc": "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" - },"1356": { - "doc": "Descoperiți", - "title": "Descoperiți", - "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 radio 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" - },"1357": { - "doc": "Descoperiți", - "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/ro-rRO/user/discovery.html#local-mesh-discovery-scanner" - },"1358": { - "doc": "Descoperiți", - "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#mesh-beacon", - - "relUrl": "/ro-rRO/user/discovery.html#mesh-beacon" - },"1359": { - "doc": "Descoperiți", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#manual-exploration", - - "relUrl": "/ro-rRO/user/discovery.html#manual-exploration" - },"1360": { - "doc": "Descoperiți", - "title": "Trasare traseu", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#trasare-traseu", - - "relUrl": "/ro-rRO/user/discovery.html#trasare-traseu" - },"1361": { - "doc": "Descoperiți", - "title": "Informații vecin", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#informa%C8%9Bii-vecin", - - "relUrl": "/ro-rRO/user/discovery.html#informații-vecin" - },"1362": { - "doc": "Descoperiți", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/ro-rRO/user/discovery.html#node-list-as-a-discovery-tool" - },"1363": { - "doc": "Descoperiți", - "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" - },"1364": { - "doc": "Discovery", - "title": "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 radio 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" - },"1365": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/ga-rIE/user/discovery.html#local-mesh-discovery-scanner" - },"1366": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#mesh-beacon", - - "relUrl": "/ga-rIE/user/discovery.html#mesh-beacon" - },"1367": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#manual-exploration", - - "relUrl": "/ga-rIE/user/discovery.html#manual-exploration" - },"1368": { - "doc": "Discovery", - "title": "Céim rianadóireachta", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#c%C3%A9im-rianad%C3%B3ireachta", - - "relUrl": "/ga-rIE/user/discovery.html#céim-rianadóireachta" - },"1369": { - "doc": "Discovery", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#neighbor-info", - - "relUrl": "/ga-rIE/user/discovery.html#neighbor-info" - },"1370": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/ga-rIE/user/discovery.html#node-list-as-a-discovery-tool" - },"1371": { - "doc": "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" - },"1372": { - "doc": "Discovery", - "title": "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 radio 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" - },"1373": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/iw-rIL/user/discovery.html#local-mesh-discovery-scanner" - },"1374": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#mesh-beacon", - - "relUrl": "/iw-rIL/user/discovery.html#mesh-beacon" - },"1375": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#manual-exploration", - - "relUrl": "/iw-rIL/user/discovery.html#manual-exploration" - },"1376": { - "doc": "Discovery", - "title": "בדיקת מסלול", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.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/discovery.html#בדיקת-מסלול" - },"1377": { - "doc": "Discovery", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#neighbor-info", - - "relUrl": "/iw-rIL/user/discovery.html#neighbor-info" - },"1378": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/iw-rIL/user/discovery.html#node-list-as-a-discovery-tool" - },"1379": { - "doc": "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" - },"1380": { - "doc": "Upptäckt", - "title": "Upptäckt", - "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 radio 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" - },"1381": { - "doc": "Upptäckt", - "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/sv-rSE/user/discovery.html#local-mesh-discovery-scanner" - },"1382": { - "doc": "Upptäckt", - "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#mesh-beacon", - - "relUrl": "/sv-rSE/user/discovery.html#mesh-beacon" - },"1383": { - "doc": "Upptäckt", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#manual-exploration", - - "relUrl": "/sv-rSE/user/discovery.html#manual-exploration" - },"1384": { - "doc": "Upptäckt", - "title": "Traceroute (spåra rutt)", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#traceroute-sp%C3%A5ra-rutt", - - "relUrl": "/sv-rSE/user/discovery.html#traceroute-spåra-rutt" - },"1385": { - "doc": "Upptäckt", - "title": "Granninformation", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#granninformation", - - "relUrl": "/sv-rSE/user/discovery.html#granninformation" - },"1386": { - "doc": "Upptäckt", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/sv-rSE/user/discovery.html#node-list-as-a-discovery-tool" - },"1387": { - "doc": "Upptäckt", - "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" - },"1388": { - "doc": "Discovery", - "title": "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 radio 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" - },"1389": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/ht-rHT/user/discovery.html#local-mesh-discovery-scanner" - },"1390": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#mesh-beacon", - - "relUrl": "/ht-rHT/user/discovery.html#mesh-beacon" - },"1391": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#manual-exploration", - - "relUrl": "/ht-rHT/user/discovery.html#manual-exploration" - },"1392": { - "doc": "Discovery", - "title": "Traceroute", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#traceroute", - - "relUrl": "/ht-rHT/user/discovery.html#traceroute" - },"1393": { - "doc": "Discovery", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#neighbor-info", - - "relUrl": "/ht-rHT/user/discovery.html#neighbor-info" - },"1394": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/ht-rHT/user/discovery.html#node-list-as-a-discovery-tool" - },"1395": { - "doc": "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" - },"1396": { - "doc": "Haku", - "title": "Haku", - "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: . | Paikallinen verkon haku (Scanner) — automaattinen tila, joka kierrättää yhdistettyä radiota eri LoRa-esiasetusten läpi, kuuntelee jokaisella ja arvioi, mikä esiasetus toimii parhaiten sijainnissasi. | 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" - },"1397": { - "doc": "Haku", - "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. Se kierrättää yhdistettyä radiota valitsemiesi esiasetusten läpi, kuuntelee jokaisella asetuksella määrätyn ajan kerätäkseen paketteja ja analysoi sekä pisteyttää tulokset. Avaa se kohdasta Asetukset → Lisäasetukset → Paikallinen mesh-haku. Työpöytäversiossa sille on oma kohta kohdassa Asetukset → Paikallinen mesh-haku. ⚠️ Huom: Haku muuttaa radiosi LoRa-asetuksia väliaikaisesti skannauksen ajaksi ja palauttaa alkuperäisen konfiguraation sen päätyttyä. Laitteen täytyy olla yhdistettynä, jotta skannaus voidaan suorittaa. Skannauksen asetukset . Ennen aloittamista määritä nämä asetukset: . | Hallinta | 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ä | Valinnainen kytkin, joka estää näytön siirtymisen lepotilaan pitkän skannauksen aikana. | . Käynnistä-painike ei ole käytettävissä ja näyttää syyn, kunnes skannaus voidaan suorittaa. Yleisiä syitä, miksi se on pois käytöstä: . | Laite ei ole yhdistetty | Esiasetuksia ei ole valittu skannattavaksi. | Valittu esiasetus käyttää 2,4 GHz -taajuutta, jota laitteistosi ei tue. | . Reaaliaikainen edistyminen . Skannauksen aikana haku näyttää sen nykyisen vaiheen: . | Tila | Mitä tapahtuu | . | Valmistelee | Tallennetaan nykyinen kokoonpano ja valmistaudutaan skannaukseen. | . | Vaihdetaan kohteeseen <preset> | Vaihdetaan radio seuraavaan esiasetukseen testausta varten. | . | Yhdistetään uudelleen | Yhteys muodostetaan uudelleen esiasetuksen vaihdon jälkeen. | . | Kuuntelu | Nykyisen esiasetuksen kuuntelu pakettien keräämiseksi, seuraavaan vaiheeseen siirtymisen laskuri käynnissä. | . | Analyysi | Kerättyjen pakettien käsittely ja esiasetusten vertailu ja pisteytys. | . | Palautetaan asetuksia | Palautetaan alkuperäinen LoRa-konfiguraatio takaisin. | . Tulosten lukeminen . 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: Androidilla haku voi luoda laitteessa toimivan tekoälyyhteenvedon (Gemini Nano) tuloksistasi. Jos laitteessa toimivaa mallia ei ole käytettävissä, käytetään algoritmista yhteenvetoa — näin saat aina luettavan tulkinnan skannauksesta. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#paikallinen-verkon-haku-scanner", - - "relUrl": "/fi-rFI/user/discovery.html#paikallinen-verkon-haku-scanner" - },"1398": { - "doc": "Haku", - "title": "Verkkokutsu", - "content": "Mesh Beacon antaa radioille mahdollisuuden kutsua muita liittymään mesh-verkkoon. Majakkatilassa oleva radio lähettää määräajoin kutsun, jossa voidaan ilmoittaa kanava, alue ja modeemiasetus. Näin lähistöllä olevat laitteet voivat havaita verkon jo ennen kuin niillä on yhteinen määritys. Määritä se kohdassa Asetukset → Moduuliasetukset → Mesh Beacon: . | Kuuntele majakoita – vastaanota muiden radioiden lähettämiä liittymiskutsuja. | Lähetä majakka – lähetä oma liittymiskutsusi määritetyin väliajoin. Voit liittää mukaan viestin ja tarjotun kanavan. | . 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: . | Liity – vaihda tarjottuun kanavaan ja esiasetukseen (radio palautetaan alkutilaan ja käynnistyy uudelleen). 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. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#verkkokutsu", - - "relUrl": "/fi-rFI/user/discovery.html#verkkokutsu" - },"1399": { - "doc": "Haku", - "title": "Manuaalinen haku", - "content": "Alla olevat työkalut ovat käytettävissä milloin tahansa radiolistasta ja radion tietonäkymistä. Käytä niitä yksittäisten reittien tutkimiseen ja topologian muodostamiseen, joko osana skannausta tai sen sijaan. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#manuaalinen-haku", - - "relUrl": "/fi-rFI/user/discovery.html#manuaalinen-haku" - },"1400": { - "doc": "Haku", - "title": "Reitinselvitys", - "content": "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ää. | Radion tietonäkymässä napauta Reitinselvitys. | Sovellus lähettää reitinselvityspyynnön ja odottaa vastausta. | Tulokset näyttävät jokaisen hypyn järjestyksessä sekä signaalin laadun jokaisessa vaiheessa. | . Tulosten lukeminen . Reitinselvityksen tulos näyttää tältä: . Sinä → Radio A (SNR: 8.5, RSSI: -95) → Radio B (SNR: 5.2, RSSI: -108) → Kohde . Jokainen hyppy on välittäjä-radio, joka lähetti viestin eteenpäin. Jokaisen hypyn SNR- ja RSSI-arvot kertovat kyseisen yhteysvälin laadusta. | Mitä kannattaa tarkkailla | Mitä se tarkoittaa | . | Kaikki hypyt näyttävät hyvän SNR:n (≥ −7 dB, vihreä) | Hyvä reitti — viestit kulkevat luotettavasti | . | Yksi hyppy näyttää huonon SNR:n (< −15 dB, punainen) | 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 . | Reittiä ei löytynyt — kohderadio voi olla kiinni, kantaman ulkopuolella tai eri kanavalla. 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. Kokeile nostaa hyppymäärärajaa kohdassa Asetukset → LoRa-asetukset. | Epäsymmetriset reitit — reitinselvitys A→B voi kulkea eri reittiä kuin B→A. Tämä on normaalia — radiosignaalin eteneminen ei aina ole symmetristä. | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#reitinselvitys", - - "relUrl": "/fi-rFI/user/discovery.html#reitinselvitys" - },"1401": { - "doc": "Haku", - "title": "Naapuritieto", - "content": "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 . | Siirry kohtaan Asetukset → Moduuliasetukset → Naapuritieto. | Ota moduuli käyttöön. | Aseta lähetysväli (oletus: 900 sekuntia / 15 minuuttia). | . Kun toiminto on käytössä, radio lähettää säännöllisesti naapuritiedot. Myös muut radiot, joissa naapuritieto on käytössä, toimivat samalla tavalla. Naapuritiedon katselu . | Avaa minkä tahansa radion tietonäkymä ja etsi Naapurit-osio. | Jokainen naapurimerkintä näyttää radion, joka on kuultu suoraan, sekä sen signaalilaadun. | Yhdistä naapuritiedot useista radioista ymmärtääksesi koko mesh-verkon topologian. | . ⚠️ Huom: Naapuritieto lisää lähetysajan käyttöä, koska jokainen käytössä oleva radio lähettää säännöllisesti naapurilistansa. Vilkkaissa verkoissa, joissa on paljon radioita, harkitse pidempiä lähetysvälejä (3600 sekuntia tai enemmän) ruuhkautumisen välttämiseksi. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#naapuritieto", - - "relUrl": "/fi-rFI/user/discovery.html#naapuritieto" - },"1402": { - "doc": "Haku", - "title": "Radiolista hakutyökaluna", - "content": "Radiolista on itsessään tehokas hakutyökalu, kun käytät sen suodatus- ja lajitteluominaisuuksia oikein. Uusien radioiden löytäminen . | Lajittele Viimeksi kuultu nähdäksesi viimeksi aktiiviset radiot ylimpänä. | Ota käyttöön Näytä tuntemattomat nähdäksesi radiot, jotka ovat ilmestyneet verkkoon, mutta eivät ole vielä lähettäneet käyttäjätietoja — usein juuri käyttöönotettuja laitteita. | . Yhteyksien arviointi . | 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. | Käytä Rajaa MQTT pois keskittyäksesi radioyhteyksillä tavoitettaviin radioihin (ei internet-sillan kautta). | . Infrastruktuurin tarkistus . | 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#radiolista-hakuty%C3%B6kaluna", - - "relUrl": "/fi-rFI/user/discovery.html#radiolista-hakutyökaluna" - },"1403": { - "doc": "Haku", - "title": "Vinkkejä mesh-verkon tutkimiseen", - "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#vinkkej%C3%A4-mesh-verkon-tutkimiseen", - - "relUrl": "/fi-rFI/user/discovery.html#vinkkejä-mesh-verkon-tutkimiseen" - },"1404": { - "doc": "Discovery", - "title": "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 radio 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" - },"1405": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/gl-rES/user/discovery.html#local-mesh-discovery-scanner" - },"1406": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#mesh-beacon", - - "relUrl": "/gl-rES/user/discovery.html#mesh-beacon" - },"1407": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#manual-exploration", - - "relUrl": "/gl-rES/user/discovery.html#manual-exploration" - },"1408": { - "doc": "Discovery", - "title": "Traza-ruta", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#traza-ruta", - - "relUrl": "/gl-rES/user/discovery.html#traza-ruta" - },"1409": { - "doc": "Discovery", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#neighbor-info", - - "relUrl": "/gl-rES/user/discovery.html#neighbor-info" - },"1410": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/gl-rES/user/discovery.html#node-list-as-a-discovery-tool" - },"1411": { - "doc": "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" - },"1412": { - "doc": "Discovery", - "title": "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 radio 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" - },"1413": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/uk-rUA/user/discovery.html#local-mesh-discovery-scanner" - },"1414": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#mesh-beacon", - - "relUrl": "/uk-rUA/user/discovery.html#mesh-beacon" - },"1415": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#manual-exploration", - - "relUrl": "/uk-rUA/user/discovery.html#manual-exploration" - },"1416": { - "doc": "Discovery", - "title": "Маршрут", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#%D0%BC%D0%B0%D1%80%D1%88%D1%80%D1%83%D1%82", - - "relUrl": "/uk-rUA/user/discovery.html#маршрут" - },"1417": { - "doc": "Discovery", - "title": "Інформація про сусідів", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.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/discovery.html#інформація-про-сусідів" - },"1418": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/uk-rUA/user/discovery.html#node-list-as-a-discovery-tool" - },"1419": { - "doc": "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" - },"1420": { "doc": "Entdecken", "title": "Entdecken", "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: . | Lokale Netzwerk Erkennung (Scanner) – ein automatischer Modus, der das angeschlossene Funkmodul nacheinander auf verschiedene LoRa Voreinstellungen umschaltet, auf jeder dieser Einstellungen lauscht und bewertet, welche davon an Ihrem Standort die beste Leistung erbringt. | 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" - },"1421": { + },"1317": { "doc": "Entdecken", "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. Es schaltet das angeschlossene Funkgerät nacheinander auf eine oder mehrere von Ihnen gewählte Voreinstellungen, verweilt jeweils für eine festgelegte Zeit auf dem Kanal, um Datenpakete zu erfassen, und analysiert sowie bewertet anschließend die Ergebnisse. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html#local-mesh-discovery-scanner", "relUrl": "/de-rDE/user/discovery.html#local-mesh-discovery-scanner" - },"1422": { + },"1318": { "doc": "Entdecken", "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html#mesh-beacon", "relUrl": "/de-rDE/user/discovery.html#mesh-beacon" - },"1423": { + },"1319": { "doc": "Entdecken", "title": "Manual Exploration", "content": "The tools below 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. ", "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html#manual-exploration", "relUrl": "/de-rDE/user/discovery.html#manual-exploration" - },"1424": { + },"1320": { "doc": "Entdecken", "title": "Traceroute", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html#traceroute", "relUrl": "/de-rDE/user/discovery.html#traceroute" - },"1425": { + },"1321": { "doc": "Entdecken", "title": "Nachbarinformation", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html#nachbarinformation", "relUrl": "/de-rDE/user/discovery.html#nachbarinformation" - },"1426": { + },"1322": { "doc": "Entdecken", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", "relUrl": "/de-rDE/user/discovery.html#node-list-as-a-discovery-tool" - },"1427": { + },"1323": { "doc": "Entdecken", "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" - },"1428": { + },"1324": { "doc": "Discovery", "title": "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 radio 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", + "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html", - "relUrl": "/hr-rHR/user/discovery.html" - },"1429": { + "relUrl": "/ca-rES/user/discovery.html" + },"1325": { "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#local-mesh-discovery-scanner", - "relUrl": "/hr-rHR/user/discovery.html#local-mesh-discovery-scanner" - },"1430": { + "relUrl": "/ca-rES/user/discovery.html#local-mesh-discovery-scanner" + },"1326": { "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#mesh-beacon", + "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#mesh-beacon", - "relUrl": "/hr-rHR/user/discovery.html#mesh-beacon" - },"1431": { + "relUrl": "/ca-rES/user/discovery.html#mesh-beacon" + },"1327": { "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#manual-exploration", + "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#manual-exploration", - "relUrl": "/hr-rHR/user/discovery.html#manual-exploration" - },"1432": { + "relUrl": "/ca-rES/user/discovery.html#manual-exploration" + },"1328": { "doc": "Discovery", - "title": "Traceroute", + "title": "Traçar ruta", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#traceroute", + "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#tra%C3%A7ar-ruta", - "relUrl": "/hr-rHR/user/discovery.html#traceroute" - },"1433": { + "relUrl": "/ca-rES/user/discovery.html#traçar-ruta" + },"1329": { "doc": "Discovery", "title": "Neighbor Info", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#neighbor-info", + "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#neighbor-info", - "relUrl": "/hr-rHR/user/discovery.html#neighbor-info" - },"1434": { + "relUrl": "/ca-rES/user/discovery.html#neighbor-info" + },"1330": { "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#node-list-as-a-discovery-tool", - "relUrl": "/hr-rHR/user/discovery.html#node-list-as-a-discovery-tool" - },"1435": { + "relUrl": "/ca-rES/user/discovery.html#node-list-as-a-discovery-tool" + },"1331": { "doc": "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", + "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#tips-for-mesh-exploration", - "relUrl": "/hr-rHR/user/discovery.html#tips-for-mesh-exploration" - },"1436": { - "doc": "Discovery", - "title": "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 radio 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" - },"1437": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/lt-rLT/user/discovery.html#local-mesh-discovery-scanner" - },"1438": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#mesh-beacon", - - "relUrl": "/lt-rLT/user/discovery.html#mesh-beacon" - },"1439": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#manual-exploration", - - "relUrl": "/lt-rLT/user/discovery.html#manual-exploration" - },"1440": { - "doc": "Discovery", - "title": "Žinutės kelias", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#%C5%BEinut%C4%97s-kelias", - - "relUrl": "/lt-rLT/user/discovery.html#žinutės-kelias" - },"1441": { - "doc": "Discovery", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#neighbor-info", - - "relUrl": "/lt-rLT/user/discovery.html#neighbor-info" - },"1442": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/lt-rLT/user/discovery.html#node-list-as-a-discovery-tool" - },"1443": { - "doc": "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" - },"1444": { - "doc": "Discovery", - "title": "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 radio 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" - },"1445": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/en/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/en/user/discovery.html#local-mesh-discovery-scanner" - },"1446": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/en/user/discovery.html#mesh-beacon", - - "relUrl": "/en/user/discovery.html#mesh-beacon" - },"1447": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/en/user/discovery.html#manual-exploration", - - "relUrl": "/en/user/discovery.html#manual-exploration" - },"1448": { - "doc": "Discovery", - "title": "Traceroute", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/en/user/discovery.html#traceroute", - - "relUrl": "/en/user/discovery.html#traceroute" - },"1449": { - "doc": "Discovery", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/en/user/discovery.html#neighbor-info", - - "relUrl": "/en/user/discovery.html#neighbor-info" - },"1450": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/en/user/discovery.html#node-list-as-a-discovery-tool" - },"1451": { - "doc": "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" - },"1452": { - "doc": "Discovery", - "title": "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 radio 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" - },"1453": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/hu-rHU/user/discovery.html#local-mesh-discovery-scanner" - },"1454": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#mesh-beacon", - - "relUrl": "/hu-rHU/user/discovery.html#mesh-beacon" - },"1455": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#manual-exploration", - - "relUrl": "/hu-rHU/user/discovery.html#manual-exploration" - },"1456": { - "doc": "Discovery", - "title": "Traceroute", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#traceroute", - - "relUrl": "/hu-rHU/user/discovery.html#traceroute" - },"1457": { - "doc": "Discovery", - "title": "Szomszéd-információ", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#szomsz%C3%A9d-inform%C3%A1ci%C3%B3", - - "relUrl": "/hu-rHU/user/discovery.html#szomszéd-információ" - },"1458": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/hu-rHU/user/discovery.html#node-list-as-a-discovery-tool" - },"1459": { - "doc": "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" - },"1460": { - "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 radio 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" - },"1461": { - "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/bg-rBG/user/discovery.html#local-mesh-discovery-scanner" - },"1462": { - "doc": "Откриване", - "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#mesh-beacon", - - "relUrl": "/bg-rBG/user/discovery.html#mesh-beacon" - },"1463": { - "doc": "Откриване", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#manual-exploration", - - "relUrl": "/bg-rBG/user/discovery.html#manual-exploration" - },"1464": { - "doc": "Откриване", - "title": "Трасиране на маршрут", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.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/discovery.html#трасиране-на-маршрут" - },"1465": { - "doc": "Откриване", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#neighbor-info", - - "relUrl": "/bg-rBG/user/discovery.html#neighbor-info" - },"1466": { - "doc": "Откриване", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/bg-rBG/user/discovery.html#node-list-as-a-discovery-tool" - },"1467": { - "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/bg-rBG/user/discovery.html#tips-for-mesh-exploration", - - "relUrl": "/bg-rBG/user/discovery.html#tips-for-mesh-exploration" - },"1468": { - "doc": "Discovery", - "title": "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 radio 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" - },"1469": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/sl-rSI/user/discovery.html#local-mesh-discovery-scanner" - },"1470": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#mesh-beacon", - - "relUrl": "/sl-rSI/user/discovery.html#mesh-beacon" - },"1471": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#manual-exploration", - - "relUrl": "/sl-rSI/user/discovery.html#manual-exploration" - },"1472": { - "doc": "Discovery", - "title": "Pot", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#pot", - - "relUrl": "/sl-rSI/user/discovery.html#pot" - },"1473": { - "doc": "Discovery", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#neighbor-info", - - "relUrl": "/sl-rSI/user/discovery.html#neighbor-info" - },"1474": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/sl-rSI/user/discovery.html#node-list-as-a-discovery-tool" - },"1475": { - "doc": "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" - },"1476": { - "doc": "Discovery", - "title": "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 radio 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" - },"1477": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/pt-rPT/user/discovery.html#local-mesh-discovery-scanner" - },"1478": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#mesh-beacon", - - "relUrl": "/pt-rPT/user/discovery.html#mesh-beacon" - },"1479": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#manual-exploration", - - "relUrl": "/pt-rPT/user/discovery.html#manual-exploration" - },"1480": { - "doc": "Discovery", - "title": "Traçar rota", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#tra%C3%A7ar-rota", - - "relUrl": "/pt-rPT/user/discovery.html#traçar-rota" - },"1481": { - "doc": "Discovery", - "title": "Informações da vizinhança", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#informa%C3%A7%C3%B5es-da-vizinhan%C3%A7a", - - "relUrl": "/pt-rPT/user/discovery.html#informações-da-vizinhança" - },"1482": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/pt-rPT/user/discovery.html#node-list-as-a-discovery-tool" - },"1483": { - "doc": "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" - },"1484": { + "relUrl": "/ca-rES/user/discovery.html#tips-for-mesh-exploration" + },"1332": { "doc": "Discovery", "title": "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 radio 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" - },"1485": { + },"1333": { "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html#local-mesh-discovery-scanner", "relUrl": "/be-rBY/user/discovery.html#local-mesh-discovery-scanner" - },"1486": { + },"1334": { "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html#mesh-beacon", "relUrl": "/be-rBY/user/discovery.html#mesh-beacon" - },"1487": { + },"1335": { "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html#manual-exploration", "relUrl": "/be-rBY/user/discovery.html#manual-exploration" - },"1488": { + },"1336": { "doc": "Discovery", "title": "Traceroute", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html#traceroute", "relUrl": "/be-rBY/user/discovery.html#traceroute" - },"1489": { + },"1337": { "doc": "Discovery", "title": "Neighbor Info", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html#neighbor-info", "relUrl": "/be-rBY/user/discovery.html#neighbor-info" - },"1490": { + },"1338": { "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", "relUrl": "/be-rBY/user/discovery.html#node-list-as-a-discovery-tool" - },"1491": { + },"1339": { "doc": "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" - },"1492": { + },"1340": { + "doc": "Discovery", + "title": "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 radio 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" + },"1341": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/uk-rUA/user/discovery.html#local-mesh-discovery-scanner" + },"1342": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#mesh-beacon", + + "relUrl": "/uk-rUA/user/discovery.html#mesh-beacon" + },"1343": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#manual-exploration", + + "relUrl": "/uk-rUA/user/discovery.html#manual-exploration" + },"1344": { + "doc": "Discovery", + "title": "Маршрут", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#%D0%BC%D0%B0%D1%80%D1%88%D1%80%D1%83%D1%82", + + "relUrl": "/uk-rUA/user/discovery.html#маршрут" + },"1345": { + "doc": "Discovery", + "title": "Інформація про сусідів", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.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/discovery.html#інформація-про-сусідів" + },"1346": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/uk-rUA/user/discovery.html#node-list-as-a-discovery-tool" + },"1347": { + "doc": "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" + },"1348": { + "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 radio 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" + },"1349": { + "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/zh-rCN/user/discovery.html#local-mesh-discovery-scanner" + },"1350": { + "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#mesh-%E4%BF%A1%E6%A0%87", + + "relUrl": "/zh-rCN/user/discovery.html#mesh-信标" + },"1351": { + "doc": "发现", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#manual-exploration", + + "relUrl": "/zh-rCN/user/discovery.html#manual-exploration" + },"1352": { + "doc": "发现", + "title": "追踪器", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#%E8%BF%BD%E8%B8%AA%E5%99%A8", + + "relUrl": "/zh-rCN/user/discovery.html#追踪器" + },"1353": { + "doc": "发现", + "title": "邻居信息", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#%E9%82%BB%E5%B1%85%E4%BF%A1%E6%81%AF", + + "relUrl": "/zh-rCN/user/discovery.html#邻居信息" + },"1354": { + "doc": "发现", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/zh-rCN/user/discovery.html#node-list-as-a-discovery-tool" + },"1355": { + "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" + },"1356": { + "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 radio 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" + },"1357": { + "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/bg-rBG/user/discovery.html#local-mesh-discovery-scanner" + },"1358": { + "doc": "Откриване", + "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#mesh-beacon", + + "relUrl": "/bg-rBG/user/discovery.html#mesh-beacon" + },"1359": { + "doc": "Откриване", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#manual-exploration", + + "relUrl": "/bg-rBG/user/discovery.html#manual-exploration" + },"1360": { + "doc": "Откриване", + "title": "Трасиране на маршрут", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.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/discovery.html#трасиране-на-маршрут" + },"1361": { + "doc": "Откриване", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#neighbor-info", + + "relUrl": "/bg-rBG/user/discovery.html#neighbor-info" + },"1362": { + "doc": "Откриване", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/bg-rBG/user/discovery.html#node-list-as-a-discovery-tool" + },"1363": { + "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/bg-rBG/user/discovery.html#tips-for-mesh-exploration", + + "relUrl": "/bg-rBG/user/discovery.html#tips-for-mesh-exploration" + },"1364": { + "doc": "尋找", + "title": "尋找", + "content": "探索工具可協助您了解 mesh 網路的連線方式——哪些節點彼此可以收到訊號、訊息所經過的路徑，以及哪裡存在瓶頸或訊號薄弱的連結。 . The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected radio 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" + },"1365": { + "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 解讀結果 . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/zh-rTW/user/discovery.html#local-mesh-discovery-scanner" + },"1366": { + "doc": "尋找", + "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#mesh-beacon", + + "relUrl": "/zh-rTW/user/discovery.html#mesh-beacon" + },"1367": { + "doc": "尋找", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#manual-exploration", + + "relUrl": "/zh-rTW/user/discovery.html#manual-exploration" + },"1368": { + "doc": "尋找", + "title": "路由追蹤", + "content": "路由追蹤可顯示訊息從您的節點到 mesh 網路上任一節點所經過的確切路徑。 這是診斷連線問題最有效的工具。 . 執行路由追蹤 . | 前往「節點」，並點選您要追蹤的節點。 | 在節點詳細資訊畫面上，點選「路由追蹤」。 | 應用程式將發送路由追蹤請求並等待回應。 | 結果將依序顯示每一個跳躍點，並呈現每個步驟的訊號品質。 | . 解讀結果 . 路由追蹤結果的顯示方式如下： . 你 → 裝置 A (SNR: 8.5, RSSI: -95) → 裝置 B (SNR: 5.2, RSSI: -108) → 目標 . 每個跳躍點代表一個轉送該訊息的中繼節點。 每個跳躍點的 SNR 與 RSSI 數值可反映該路段的連線品質。 . | 判讀重點 | 代表意義 | . | All hops show Good SNR (≥ −7 dB, green) | 路徑狀況良好 — 訊息可穩定傳送 | . | One hop shows Bad SNR (< −15 dB, red) | 訊號薄弱 — 此中繼路段不穩定 | . | 跳躍點過多（4 個以上） | 路徑過長 — 建議調整節點位置以縮短路徑 | . | 重試時走不同路徑 | Mesh 網路正在自動調整 — 存在多條路由（這是好現象！） | . 💡 提示：請在幾分鐘內多次執行路由追蹤。 若路徑發生變化，代表您的 mesh 網路具備備援路由 — 這是網路連線良好的象徵。 . 使用路由追蹤進行疑難排解 . | 「找不到路由」— 目標節點可能已離線、超出範圍，或使用不同的頻道。 請確認兩個節點至少共用一個使用相同加密金鑰的頻道。 | 「路由追蹤逾時」— 路徑可能過長（超過跳躍限制），或某中繼節點發生壅塞。 請嘗試在「設定 → LoRa 設定」中提高跳躍限制。 | 非對稱路徑 — 從 A → B 的路由追蹤路徑，可能與 B → A 不同。 這屬於正常現象 — 無線電訊號的傳播並不總是對稱的。 | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#%E8%B7%AF%E7%94%B1%E8%BF%BD%E8%B9%A4", + + "relUrl": "/zh-rTW/user/discovery.html#路由追蹤" + },"1369": { + "doc": "尋找", + "title": "鄰近節點資訊", + "content": "鄰近節點資訊模組可讓每個節點廣播其可直接收到訊號的節點清單（單跳躍）。 當多個節點共享各自的鄰近節點清單時，您便可拼湊出整個 mesh 網路的拓撲圖。 . 啟用鄰近節點資訊 . | 前往「設定 → 模組設定 → 鄰近節點資訊」。 | 啟用此模組。 | 設定廣播間隔（預設：900 秒 / 15 分鐘）。 | . 啟用後，您的節點將定期廣播其鄰近節點列表。 其他已啟用鄰近節點資訊的節點也會執行相同動作。 . 檢視鄰近節點資料 . | 開啟任一節點的詳細資訊畫面，並尋找「鄰近節點」區段。 | 每筆鄰近節點記錄會顯示可直接收到訊號的節點及其訊號品質。 | 結合多個節點的鄰近節點資料，以了解完整的 mesh 網路拓撲。 | . ⚠️ 注意：鄰近節點資訊會增加無線電佔用時間，因為每個已啟用的節點會定期廣播其鄰近節點清單。 在節點眾多的繁忙 mesh 網路中，建議設定較長的廣播間隔（3600 秒以上）以避免壅塞。 . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#%E9%84%B0%E8%BF%91%E7%AF%80%E9%BB%9E%E8%B3%87%E8%A8%8A", + + "relUrl": "/zh-rTW/user/discovery.html#鄰近節點資訊" + },"1370": { + "doc": "尋找", + "title": "將節點清單作為探索工具", + "content": "善用節點清單的篩選與排序功能，即可將其作為強大的探索工具。 . 尋找新節點 . | 依「最後收到訊號」排序，可將最近有活動的節點顯示於頂部。 | 啟用「包含未知節點」，可顯示已出現於 mesh 網路但尚未傳送使用者資訊的節點 — 這些通常是剛開機的裝置。 | . 評估連線狀況 . | 依「跳躍距離」排序，可區分可直接到達的節點（0 個跳躍點）與需中繼轉送的節點。 | 依「距離」排序，可找出附近的節點並確認是否可到達。 | 使用「排除 MQTT」，可專注於透過無線電（而非網際網路橋接）可到達的節點。 | . 基礎架構稽核 . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | 檢查其訊號品質與最後收到訊號的時間，以確認基礎架構節點運作正常。 | . 請參閱〔節點〕(nodes) 以了解完整的篩選與排序選項說明。 . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#%E5%B0%87%E7%AF%80%E9%BB%9E%E6%B8%85%E5%96%AE%E4%BD%9C%E7%82%BA%E6%8E%A2%E7%B4%A2%E5%B7%A5%E5%85%B7", + + "relUrl": "/zh-rTW/user/discovery.html#將節點清單作為探索工具" + },"1371": { + "doc": "尋找", + "title": "Mesh 網路探索技巧", + "content": ". | 從路由追蹤開始 — 可立即取得特定路徑的具體可行資訊。 | 在關鍵節點上啟用鄰近節點資訊 — 尤其是路由器與中繼器，以建立骨幹網路的整體概況。 | 查看地圖 —〔地圖〕(map-and-waypoints) 上的節點位置結合訊號資料，有助於了解為何某些連結訊號強，而其他連結訊號弱。 | 比較訊號變化趨勢 — 請參閱〔訊號儀表〕(signal-meter) 指南，以正確解讀 SNR 與 RSSI 數值。 | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#mesh-%E7%B6%B2%E8%B7%AF%E6%8E%A2%E7%B4%A2%E6%8A%80%E5%B7%A7", + + "relUrl": "/zh-rTW/user/discovery.html#mesh-網路探索技巧" + },"1372": { + "doc": "Discovery", + "title": "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 radio 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" + },"1373": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/sr-rLatn/user/discovery.html#local-mesh-discovery-scanner" + },"1374": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#mesh-beacon", + + "relUrl": "/sr-rLatn/user/discovery.html#mesh-beacon" + },"1375": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#manual-exploration", + + "relUrl": "/sr-rLatn/user/discovery.html#manual-exploration" + },"1376": { + "doc": "Discovery", + "title": "Праћење руте", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.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/discovery.html#праћење-руте" + },"1377": { + "doc": "Discovery", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#neighbor-info", + + "relUrl": "/sr-rLatn/user/discovery.html#neighbor-info" + },"1378": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/sr-rLatn/user/discovery.html#node-list-as-a-discovery-tool" + },"1379": { + "doc": "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" + },"1380": { + "doc": "Objevujte", + "title": "Objevujte", + "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 radio 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" + },"1381": { + "doc": "Objevujte", + "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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. | . | 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/cs-rCZ/user/discovery.html#local-mesh-discovery-scanner" + },"1382": { + "doc": "Objevujte", + "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#mesh-beacon", + + "relUrl": "/cs-rCZ/user/discovery.html#mesh-beacon" + },"1383": { + "doc": "Objevujte", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#manual-exploration", + + "relUrl": "/cs-rCZ/user/discovery.html#manual-exploration" + },"1384": { + "doc": "Objevujte", + "title": "Traceroute", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#traceroute", + + "relUrl": "/cs-rCZ/user/discovery.html#traceroute" + },"1385": { + "doc": "Objevujte", + "title": "Informace o sousedech", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#informace-o-sousedech", + + "relUrl": "/cs-rCZ/user/discovery.html#informace-o-sousedech" + },"1386": { + "doc": "Objevujte", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/cs-rCZ/user/discovery.html#node-list-as-a-discovery-tool" + },"1387": { + "doc": "Objevujte", + "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" + },"1388": { + "doc": "Discovery", + "title": "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 radio 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" + },"1389": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/en/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/en/user/discovery.html#local-mesh-discovery-scanner" + },"1390": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/en/user/discovery.html#mesh-beacon", + + "relUrl": "/en/user/discovery.html#mesh-beacon" + },"1391": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/en/user/discovery.html#manual-exploration", + + "relUrl": "/en/user/discovery.html#manual-exploration" + },"1392": { + "doc": "Discovery", + "title": "Traceroute", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/en/user/discovery.html#traceroute", + + "relUrl": "/en/user/discovery.html#traceroute" + },"1393": { + "doc": "Discovery", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/en/user/discovery.html#neighbor-info", + + "relUrl": "/en/user/discovery.html#neighbor-info" + },"1394": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/en/user/discovery.html#node-list-as-a-discovery-tool" + },"1395": { + "doc": "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" + },"1396": { + "doc": "Discovery", + "title": "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 radio 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" + },"1397": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/sl-rSI/user/discovery.html#local-mesh-discovery-scanner" + },"1398": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#mesh-beacon", + + "relUrl": "/sl-rSI/user/discovery.html#mesh-beacon" + },"1399": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#manual-exploration", + + "relUrl": "/sl-rSI/user/discovery.html#manual-exploration" + },"1400": { + "doc": "Discovery", + "title": "Pot", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#pot", + + "relUrl": "/sl-rSI/user/discovery.html#pot" + },"1401": { + "doc": "Discovery", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#neighbor-info", + + "relUrl": "/sl-rSI/user/discovery.html#neighbor-info" + },"1402": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/sl-rSI/user/discovery.html#node-list-as-a-discovery-tool" + },"1403": { + "doc": "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" + },"1404": { + "doc": "Discovery", + "title": "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 radio 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" + },"1405": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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. | . | Utilizzo 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/it-rIT/user/discovery.html#local-mesh-discovery-scanner" + },"1406": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#mesh-beacon", + + "relUrl": "/it-rIT/user/discovery.html#mesh-beacon" + },"1407": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#manual-exploration", + + "relUrl": "/it-rIT/user/discovery.html#manual-exploration" + },"1408": { + "doc": "Discovery", + "title": "Traceroute", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#traceroute", + + "relUrl": "/it-rIT/user/discovery.html#traceroute" + },"1409": { + "doc": "Discovery", + "title": "Informazioni Vicinato", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#informazioni-vicinato", + + "relUrl": "/it-rIT/user/discovery.html#informazioni-vicinato" + },"1410": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/it-rIT/user/discovery.html#node-list-as-a-discovery-tool" + },"1411": { + "doc": "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/it-rIT/user/discovery.html#tips-for-mesh-exploration", + + "relUrl": "/it-rIT/user/discovery.html#tips-for-mesh-exploration" + },"1412": { "doc": "Discovery", "title": "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 radio 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" - },"1493": { + },"1413": { "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html#local-mesh-discovery-scanner", "relUrl": "/pt-rBR/user/discovery.html#local-mesh-discovery-scanner" - },"1494": { + },"1414": { "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html#mesh-beacon", "relUrl": "/pt-rBR/user/discovery.html#mesh-beacon" - },"1495": { + },"1415": { "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html#manual-exploration", "relUrl": "/pt-rBR/user/discovery.html#manual-exploration" - },"1496": { + },"1416": { "doc": "Discovery", "title": "Traçar rota", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html#tra%C3%A7ar-rota", "relUrl": "/pt-rBR/user/discovery.html#traçar-rota" - },"1497": { + },"1417": { "doc": "Discovery", "title": "Informações do Vizinho", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html#informa%C3%A7%C3%B5es-do-vizinho", "relUrl": "/pt-rBR/user/discovery.html#informações-do-vizinho" - },"1498": { + },"1418": { "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", "relUrl": "/pt-rBR/user/discovery.html#node-list-as-a-discovery-tool" - },"1499": { + },"1419": { "doc": "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" - },"1500": { + },"1420": { "doc": "Discovery", "title": "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 radio 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", + "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html", - "relUrl": "/el-rGR/user/discovery.html" - },"1501": { + "relUrl": "/is-rIS/user/discovery.html" + },"1421": { "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#local-mesh-discovery-scanner", - "relUrl": "/el-rGR/user/discovery.html#local-mesh-discovery-scanner" - },"1502": { + "relUrl": "/is-rIS/user/discovery.html#local-mesh-discovery-scanner" + },"1422": { "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#mesh-beacon", + "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#mesh-beacon", - "relUrl": "/el-rGR/user/discovery.html#mesh-beacon" - },"1503": { + "relUrl": "/is-rIS/user/discovery.html#mesh-beacon" + },"1423": { "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#manual-exploration", + "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#manual-exploration", - "relUrl": "/el-rGR/user/discovery.html#manual-exploration" - },"1504": { + "relUrl": "/is-rIS/user/discovery.html#manual-exploration" + },"1424": { "doc": "Discovery", - "title": "Traceroute", + "title": "Ferilkönnun", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#traceroute", + "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#ferilk%C3%B6nnun", - "relUrl": "/el-rGR/user/discovery.html#traceroute" - },"1505": { + "relUrl": "/is-rIS/user/discovery.html#ferilkönnun" + },"1425": { "doc": "Discovery", "title": "Neighbor Info", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#neighbor-info", + "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#neighbor-info", - "relUrl": "/el-rGR/user/discovery.html#neighbor-info" - },"1506": { + "relUrl": "/is-rIS/user/discovery.html#neighbor-info" + },"1426": { "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#node-list-as-a-discovery-tool", - "relUrl": "/el-rGR/user/discovery.html#node-list-as-a-discovery-tool" - },"1507": { + "relUrl": "/is-rIS/user/discovery.html#node-list-as-a-discovery-tool" + },"1427": { "doc": "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", + "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#tips-for-mesh-exploration", - "relUrl": "/el-rGR/user/discovery.html#tips-for-mesh-exploration" - },"1508": { - "doc": "Discovery", - "title": "Discovery", + "relUrl": "/is-rIS/user/discovery.html#tips-for-mesh-exploration" + },"1428": { + "doc": "Découverte", + "title": "Découverte", "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 radio 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html", - "relUrl": "/es-rES/user/discovery.html" - },"1509": { - "doc": "Discovery", + "relUrl": "/fr-rFR/user/discovery.html" + },"1429": { + "doc": "Découverte", "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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. | . | 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#local-mesh-discovery-scanner", - "relUrl": "/es-rES/user/discovery.html#local-mesh-discovery-scanner" - },"1510": { - "doc": "Discovery", + "relUrl": "/fr-rFR/user/discovery.html#local-mesh-discovery-scanner" + },"1430": { + "doc": "Découverte", "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#mesh-beacon", + "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#mesh-beacon", - "relUrl": "/es-rES/user/discovery.html#mesh-beacon" - },"1511": { - "doc": "Discovery", + "relUrl": "/fr-rFR/user/discovery.html#mesh-beacon" + },"1431": { + "doc": "Découverte", "title": "Manual Exploration", "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#manual-exploration", + "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#manual-exploration", - "relUrl": "/es-rES/user/discovery.html#manual-exploration" - },"1512": { - "doc": "Discovery", + "relUrl": "/fr-rFR/user/discovery.html#manual-exploration" + },"1432": { + "doc": "Découverte", "title": "Traceroute", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#traceroute", + "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#traceroute", - "relUrl": "/es-rES/user/discovery.html#traceroute" - },"1513": { - "doc": "Discovery", - "title": "Información de Vecinos", + "relUrl": "/fr-rFR/user/discovery.html#traceroute" + },"1433": { + "doc": "Découverte", + "title": "Informations sur les voisins", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#informaci%C3%B3n-de-vecinos", + "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#informations-sur-les-voisins", - "relUrl": "/es-rES/user/discovery.html#información-de-vecinos" - },"1514": { - "doc": "Discovery", + "relUrl": "/fr-rFR/user/discovery.html#informations-sur-les-voisins" + },"1434": { + "doc": "Découverte", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#node-list-as-a-discovery-tool", - "relUrl": "/es-rES/user/discovery.html#node-list-as-a-discovery-tool" - },"1515": { - "doc": "Discovery", + "relUrl": "/fr-rFR/user/discovery.html#node-list-as-a-discovery-tool" + },"1435": { + "doc": "Découverte", "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#tips-for-mesh-exploration", - "relUrl": "/es-rES/user/discovery.html#tips-for-mesh-exploration" - },"1516": { + "relUrl": "/fr-rFR/user/discovery.html#tips-for-mesh-exploration" + },"1436": { "doc": "Discovery", "title": "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 radio 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", + "url": "/Meshtastic-Android/main/srp/user/discovery.html", - "relUrl": "/tr-rTR/user/discovery.html" - },"1517": { + "relUrl": "/srp/user/discovery.html" + },"1437": { "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/srp/user/discovery.html#local-mesh-discovery-scanner", - "relUrl": "/tr-rTR/user/discovery.html#local-mesh-discovery-scanner" - },"1518": { + "relUrl": "/srp/user/discovery.html#local-mesh-discovery-scanner" + },"1438": { "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#mesh-beacon", + "url": "/Meshtastic-Android/main/srp/user/discovery.html#mesh-beacon", - "relUrl": "/tr-rTR/user/discovery.html#mesh-beacon" - },"1519": { + "relUrl": "/srp/user/discovery.html#mesh-beacon" + },"1439": { "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#manual-exploration", + "url": "/Meshtastic-Android/main/srp/user/discovery.html#manual-exploration", - "relUrl": "/tr-rTR/user/discovery.html#manual-exploration" - },"1520": { + "relUrl": "/srp/user/discovery.html#manual-exploration" + },"1440": { "doc": "Discovery", - "title": "Yol izle", + "title": "Праћење руте", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#yol-izle", + "url": "/Meshtastic-Android/main/srp/user/discovery.html#%D0%BF%D1%80%D0%B0%D1%9B%D0%B5%D1%9A%D0%B5-%D1%80%D1%83%D1%82%D0%B5", - "relUrl": "/tr-rTR/user/discovery.html#yol-izle" - },"1521": { - "doc": "Discovery", - "title": "Komşu Bilgisi", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#kom%C5%9Fu-bilgisi", - - "relUrl": "/tr-rTR/user/discovery.html#komşu-bilgisi" - },"1522": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/tr-rTR/user/discovery.html#node-list-as-a-discovery-tool" - },"1523": { - "doc": "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" - },"1524": { - "doc": "Discovery", - "title": "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 radio 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" - },"1525": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/no-rNO/user/discovery.html#local-mesh-discovery-scanner" - },"1526": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#mesh-beacon", - - "relUrl": "/no-rNO/user/discovery.html#mesh-beacon" - },"1527": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#manual-exploration", - - "relUrl": "/no-rNO/user/discovery.html#manual-exploration" - },"1528": { - "doc": "Discovery", - "title": "Traceroute", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#traceroute", - - "relUrl": "/no-rNO/user/discovery.html#traceroute" - },"1529": { + "relUrl": "/srp/user/discovery.html#праћење-руте" + },"1441": { "doc": "Discovery", "title": "Neighbor Info", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#neighbor-info", + "url": "/Meshtastic-Android/main/srp/user/discovery.html#neighbor-info", - "relUrl": "/no-rNO/user/discovery.html#neighbor-info" - },"1530": { + "relUrl": "/srp/user/discovery.html#neighbor-info" + },"1442": { "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + "url": "/Meshtastic-Android/main/srp/user/discovery.html#node-list-as-a-discovery-tool", - "relUrl": "/no-rNO/user/discovery.html#node-list-as-a-discovery-tool" - },"1531": { + "relUrl": "/srp/user/discovery.html#node-list-as-a-discovery-tool" + },"1443": { "doc": "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", + "url": "/Meshtastic-Android/main/srp/user/discovery.html#tips-for-mesh-exploration", - "relUrl": "/no-rNO/user/discovery.html#tips-for-mesh-exploration" - },"1532": { + "relUrl": "/srp/user/discovery.html#tips-for-mesh-exploration" + },"1444": { + "doc": "Discovery", + "title": "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 radio 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" + },"1445": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/sk-rSK/user/discovery.html#local-mesh-discovery-scanner" + },"1446": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#mesh-beacon", + + "relUrl": "/sk-rSK/user/discovery.html#mesh-beacon" + },"1447": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#manual-exploration", + + "relUrl": "/sk-rSK/user/discovery.html#manual-exploration" + },"1448": { + "doc": "Discovery", + "title": "Trasovanie", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#trasovanie", + + "relUrl": "/sk-rSK/user/discovery.html#trasovanie" + },"1449": { + "doc": "Discovery", + "title": "Informácia o susedoch", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#inform%C3%A1cia-o-susedoch", + + "relUrl": "/sk-rSK/user/discovery.html#informácia-o-susedoch" + },"1450": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/sk-rSK/user/discovery.html#node-list-as-a-discovery-tool" + },"1451": { + "doc": "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" + },"1452": { + "doc": "Haku", + "title": "Haku", + "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: . | Paikallinen verkon haku (Scanner) — automaattinen tila, joka kierrättää yhdistettyä radiota eri LoRa-esiasetusten läpi, kuuntelee jokaisella ja arvioi, mikä esiasetus toimii parhaiten sijainnissasi. | 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" + },"1453": { + "doc": "Haku", + "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. Se kierrättää yhdistettyä radiota valitsemiesi esiasetusten läpi, kuuntelee jokaisella asetuksella määrätyn ajan kerätäkseen paketteja ja analysoi sekä pisteyttää tulokset. Avaa se kohdasta Asetukset → Lisäasetukset → Paikallinen mesh-haku. Työpöytäversiossa sille on oma kohta kohdassa Asetukset → Paikallinen mesh-haku. ⚠️ Huom: Haku muuttaa radiosi LoRa-asetuksia väliaikaisesti skannauksen ajaksi ja palauttaa alkuperäisen konfiguraation sen päätyttyä. Laitteen täytyy olla yhdistettynä, jotta skannaus voidaan suorittaa. Skannauksen asetukset . Ennen aloittamista määritä nämä asetukset: . | Hallinta | 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ä | Valinnainen kytkin, joka estää näytön siirtymisen lepotilaan pitkän skannauksen aikana. | . Käynnistä-painike ei ole käytettävissä ja näyttää syyn, kunnes skannaus voidaan suorittaa. Yleisiä syitä, miksi se on pois käytöstä: . | Laite ei ole yhdistetty | Esiasetuksia ei ole valittu skannattavaksi. | Valittu esiasetus käyttää 2,4 GHz -taajuutta, jota laitteistosi ei tue. | . Reaaliaikainen edistyminen . Skannauksen aikana haku näyttää sen nykyisen vaiheen: . | Tila | Mitä tapahtuu | . | Valmistelee | Tallennetaan nykyinen kokoonpano ja valmistaudutaan skannaukseen. | . | Vaihdetaan kohteeseen <preset> | Vaihdetaan radio seuraavaan esiasetukseen testausta varten. | . | Yhdistetään uudelleen | Yhteys muodostetaan uudelleen esiasetuksen vaihdon jälkeen. | . | Kuuntelu | Nykyisen esiasetuksen kuuntelu pakettien keräämiseksi, seuraavaan vaiheeseen siirtymisen laskuri käynnissä. | . | Analyysi | Kerättyjen pakettien käsittely ja esiasetusten vertailu ja pisteytys. | . | Palautetaan asetuksia | Palautetaan alkuperäinen LoRa-konfiguraatio takaisin. | . Tulosten lukeminen . 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: Androidilla haku voi luoda laitteessa toimivan tekoälyyhteenvedon (Gemini Nano) tuloksistasi. Jos laitteessa toimivaa mallia ei ole käytettävissä, käytetään algoritmista yhteenvetoa — näin saat aina luettavan tulkinnan skannauksesta. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#paikallinen-verkon-haku-scanner", + + "relUrl": "/fi-rFI/user/discovery.html#paikallinen-verkon-haku-scanner" + },"1454": { + "doc": "Haku", + "title": "Verkkokutsu", + "content": "Mesh Beacon antaa radioille mahdollisuuden kutsua muita liittymään mesh-verkkoon. Majakkatilassa oleva radio lähettää määräajoin kutsun, jossa voidaan ilmoittaa kanava, alue ja modeemiasetus. Näin lähistöllä olevat laitteet voivat havaita verkon jo ennen kuin niillä on yhteinen määritys. Määritä se kohdassa Asetukset → Moduuliasetukset → Mesh Beacon: . | Kuuntele majakoita – vastaanota muiden radioiden lähettämiä liittymiskutsuja. | Lähetä majakka – lähetä oma liittymiskutsusi määritetyin väliajoin. Voit liittää mukaan viestin ja tarjotun kanavan. | . 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: . | Liity – vaihda tarjottuun kanavaan ja esiasetukseen (radio palautetaan alkutilaan ja käynnistyy uudelleen). 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. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#verkkokutsu", + + "relUrl": "/fi-rFI/user/discovery.html#verkkokutsu" + },"1455": { + "doc": "Haku", + "title": "Manuaalinen haku", + "content": "Alla olevat työkalut ovat käytettävissä milloin tahansa radiolistasta ja radion tietonäkymistä. Käytä niitä yksittäisten reittien tutkimiseen ja topologian muodostamiseen, joko osana skannausta tai sen sijaan. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#manuaalinen-haku", + + "relUrl": "/fi-rFI/user/discovery.html#manuaalinen-haku" + },"1456": { + "doc": "Haku", + "title": "Reitinselvitys", + "content": "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ää. | Radion tietonäkymässä napauta Reitinselvitys. | Sovellus lähettää reitinselvityspyynnön ja odottaa vastausta. | Tulokset näyttävät jokaisen hypyn järjestyksessä sekä signaalin laadun jokaisessa vaiheessa. | . Tulosten lukeminen . Reitinselvityksen tulos näyttää tältä: . Sinä → Radio A (SNR: 8.5, RSSI: -95) → Radio B (SNR: 5.2, RSSI: -108) → Kohde . Jokainen hyppy on välittäjä-radio, joka lähetti viestin eteenpäin. Jokaisen hypyn SNR- ja RSSI-arvot kertovat kyseisen yhteysvälin laadusta. | Mitä kannattaa tarkkailla | Mitä se tarkoittaa | . | Kaikki hypyt näyttävät hyvän SNR:n (≥ −7 dB, vihreä) | Hyvä reitti — viestit kulkevat luotettavasti | . | Yksi hyppy näyttää huonon SNR:n (< −15 dB, punainen) | 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 . | Reittiä ei löytynyt — kohderadio voi olla kiinni, kantaman ulkopuolella tai eri kanavalla. 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. Kokeile nostaa hyppymäärärajaa kohdassa Asetukset → LoRa-asetukset. | Epäsymmetriset reitit — reitinselvitys A→B voi kulkea eri reittiä kuin B→A. Tämä on normaalia — radiosignaalin eteneminen ei aina ole symmetristä. | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#reitinselvitys", + + "relUrl": "/fi-rFI/user/discovery.html#reitinselvitys" + },"1457": { + "doc": "Haku", + "title": "Naapuritieto", + "content": "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 . | Siirry kohtaan Asetukset → Moduuliasetukset → Naapuritieto. | Ota moduuli käyttöön. | Aseta lähetysväli (oletus: 900 sekuntia / 15 minuuttia). | . Kun toiminto on käytössä, radio lähettää säännöllisesti naapuritiedot. Myös muut radiot, joissa naapuritieto on käytössä, toimivat samalla tavalla. Naapuritiedon katselu . | Avaa minkä tahansa radion tietonäkymä ja etsi Naapurit-osio. | Jokainen naapurimerkintä näyttää radion, joka on kuultu suoraan, sekä sen signaalilaadun. | Yhdistä naapuritiedot useista radioista ymmärtääksesi koko mesh-verkon topologian. | . ⚠️ Huom: Naapuritieto lisää lähetysajan käyttöä, koska jokainen käytössä oleva radio lähettää säännöllisesti naapurilistansa. Vilkkaissa verkoissa, joissa on paljon radioita, harkitse pidempiä lähetysvälejä (3600 sekuntia tai enemmän) ruuhkautumisen välttämiseksi. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#naapuritieto", + + "relUrl": "/fi-rFI/user/discovery.html#naapuritieto" + },"1458": { + "doc": "Haku", + "title": "Radiolista hakutyökaluna", + "content": "Radiolista on itsessään tehokas hakutyökalu, kun käytät sen suodatus- ja lajitteluominaisuuksia oikein. Uusien radioiden löytäminen . | Lajittele Viimeksi kuultu nähdäksesi viimeksi aktiiviset radiot ylimpänä. | Ota käyttöön Näytä tuntemattomat nähdäksesi radiot, jotka ovat ilmestyneet verkkoon, mutta eivät ole vielä lähettäneet käyttäjätietoja — usein juuri käyttöönotettuja laitteita. | . Yhteyksien arviointi . | 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. | Käytä Rajaa MQTT pois keskittyäksesi radioyhteyksillä tavoitettaviin radioihin (ei internet-sillan kautta). | . Infrastruktuurin tarkistus . | 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#radiolista-hakuty%C3%B6kaluna", + + "relUrl": "/fi-rFI/user/discovery.html#radiolista-hakutyökaluna" + },"1459": { + "doc": "Haku", + "title": "Vinkkejä mesh-verkon tutkimiseen", + "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#vinkkej%C3%A4-mesh-verkon-tutkimiseen", + + "relUrl": "/fi-rFI/user/discovery.html#vinkkejä-mesh-verkon-tutkimiseen" + },"1460": { "doc": "Обнаружение", "title": "Обнаружение", "content": "Инструменты обнаружения помогают понять, как твоя mesh-сетевая структура соединена — какие ноды могут слышать друг друга, по каким путям проходят сообщения и где существуют узкие места или слабые звенья. Приложение предлагает два дополнительных подхода: . | Локальное обнаружение mesh-сети (сканер) — автоматический режим, который по очереди перебирает на твоём подключённом радио разные пресеты LoRa, слушает каждый и определяет, какой пресет лучше всего работает в твоём местоположении. | Ручное исследование — трассировка, информация о соседях и список нод, которые ты можешь использовать в любое время для изучения конкретных путей и топологии. | . ", "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.html", "relUrl": "/ru-rRU/user/discovery.html" - },"1533": { + },"1461": { "doc": "Обнаружение", "title": "Обнаружение локальной сети (Сканер)", "content": "Локальное обнаружение mesh-сети — это специализированный режим сканирования, который помогает найти лучший пресет LoRa-модема для твоего местоположения и увидеть, какие ноды активны на каждом пресете. Он циклически переключает твоё подключённое радио между одним или несколькими выбранными тобою пресетами, слушает (или “задерживается”) на каждом заданное время для сбора пакетов, затем анализирует и ранжирует результаты. Открой это через Настройки → Дополнительно → Локальное обнаружение сети. В приложении для ПК у него есть собственный пункт Настройки → Локальное обнаружение сети. ⚠️ Примечание: Обнаружение временно изменяет настройки LoRa твоего радио во время сканирования, а затем восстанавливает исходную конфигурацию после завершения. Твоё устройство должно быть подключено для запуска сканирования. Настройка сканирования . Перед началом, настройте эти параметры: . | Управление | Описание | . | Выбор пресета LoRa | Выберите один или несколько пресетов для сканирования. Обнаружение по очереди задерживается на каждом выбранном пресете. | . | Время задержки | Время прослушки каждого пресета. Выбери один из вариантов: 1, 5, 15, 30, 45, 60, 90, 120 или 180 минут. Более долгое время задержки собирает больше пакетов и даёт более чёткую картину, но занимает больше времени. | . | Не выключать экран | Дополнительный переключатель, который не даёт экрану гаснуть во время длительного сканирования. | . Кнопка Старт остаётся неактивной — с объяснением причины — пока сканирование не может быть запущено. Распространённые причины, почему она отключена: . | Устройство не подключено. | Не выбраны пресеты для сканирования. | Выбранный пресет использует частоту 2,4 ГГц, которую ваше оборудование не поддерживает. | . Текущий прогресс . Во время сканирования “Обнаружение” показывает текущий этап: . | Этап | Что происходит | . | Подготовка | Сохранение твоей текущей конфигурации и подготовка к сканированию. | . | Переключение на <preset> | Переключение радио на следующий пресет для тестирования. | . | Переподключение | Восстановление соединения после смены пресета. | . | Прослушивание | Прослушивание текущего пресета для сбора пакетов с обратным отсчётом до следующего шага. | . | Анализ | Обработка собранных пакетов и ранжирование пресетов. | . | Восстановление | Возврат твоей исходной конфигурации LoRa. | . Чтение результатов . По завершении сканирования “Обнаружение” показывает карточку результатов для каждого протестированного пресета, а также общую сводку. Метрики включают: . | Метрическая | Что для тебя это значит | . | Состояние радиоэфира | Общее качество радиообстановки на этом пресете. | . | Использование канала | Насколько загруженным был эфир во время прослушивания. | . | Время вещания | Наблюдаемое время передачи. | . | Прямые и ретранслированные ноды | Сколько mesh-нод было услышано напрямую, а сколько через ретранслятор. | . | Повреждённые / повторные пакеты | Количество повреждённых и повторных пакетов, указывающее на перегрузку или помехи. | . Дополнительные функции, доступные из результатов: . | История сканирования — сохранённые сеансы, которые ты можешь просмотреть снова; просматривайте или удаляйте прошлые сканирования. | Карта обнаружения — карта нод, найденных во время сканирования. | Экспорт отчёта — экспортируйте отчёт в формате PDF на Android или в виде текста на других платформах. | . 💡 Совет: На Android “Обнаружение” может создавать на устройстве сводку твоих результатов с помощью ИИ (Gemini Nano). Если модель на устройстве недоступна, вместо неё используется алгоритмическая сводка — так что ты всегда получаешь читаемую интерпретацию сканирования. ", "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#обнаружение-локальной-сети-сканер" - },"1534": { + },"1462": { "doc": "Обнаружение", "title": "Маяк сети", "content": "Маяк mesh-сети позволяет нодам приглашать другие устройства присоединиться к своей сети. Нода-маяк периодически передаёт приглашение, при необходимости указывая канал, регион и пресет модема, которое ближайшие устройства могут услышать ещё до того, как получат общую конфигурацию. Настройте его в разделе Настройки → Конфигурация модулей → Маяк mesh-сети: . | Слушать маяки — принимать приглашения, передаваемые другими нодами. | Передавать маяк — отправлять собственное приглашение через заданный интервал с необязательным сообщением и предлагаемым каналом. | . Полученные приглашения отображаются в виде карточек “Приглашения mesh-сети” на экране “Обнаружение”. На каждой карточке показано сообщение отправителя, а также предлагаемые канал, регион, пресет и качество сигнала, и доступны следующие действия: . | Присоединиться — переключиться на предлагаемый канал и пресет (перенастраивает радио и перезагружает его). Если предложение совпадает с вашим текущим частотным слотом, действие “Добавить канал” добавляет его без перезагрузки. | Обнаружить — запустить сканирование «Обнаружения» с предложенным пресетом, чтобы ты мог изучить эту сеть перед присоединением (отображается, только если маяк передаёт пресет). | Отклонить — проигнорировать приглашение. | . Каналы, объявленные маяками, также отображаются в настройках сканирования как Каналы маяков — выберите один, чтобы включить его в число целей сканирования. ", "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#маяк-сети" - },"1535": { + },"1463": { "doc": "Обнаружение", "title": "Ручное исследование", "content": "Приведённые ниже инструменты доступны в любое время из списка нод и с экранов сведений ноде. Используйте их для исследования конкретных путей и построения картины топологии — вместе с полным сканированием или вместо него. ", "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.html#%D1%80%D1%83%D1%87%D0%BD%D0%BE%D0%B5-%D0%B8%D1%81%D1%81%D0%BB%D0%B5%D0%B4%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5", "relUrl": "/ru-rRU/user/discovery.html#ручное-исследование" - },"1536": { + },"1464": { "doc": "Обнаружение", "title": "Трассировка маршрута", "content": "Трассировка показывает точный путь, который сообщение проходит от твоей ноды до любой другой ноды в сети. Это самый полезный инструмент для отладки проблем с подключением. Выполнение трассировки . | Перейди в Ноды и коснись ноды, которую ты хочешь отследить. | На экране деталей ноды нажми Трассировка. | Приложение отправляет запрос трассировки и ожидает ответа. | Результаты отображают каждую ноду по порядку с качеством сигнала на каждом этапе. | . Чтение результатов . Результат трассировки выглядит так: . Ты → Нода A (SNR: 8.5, RSSI: -95) → Нода B (SNR: 5.2, RSSI: -108) → Цель . Каждый хоп представляет собой ретранслирующую ноду, которая переслала сообщение. Значения SNR и RSSI на каждой ноде говорят о качестве соединения на этом конкретном участке. | На что обращать внимание | Что это значит | . | Все хопы показывают хороший SNR (≥ −7 дБ, зелёный цвет) | Здоровый путь — сообщения идут без сбоев | . | Один хоп показывает плохой SNR (< −15 дБ, красный цвет) | Слабое звено — этот сегмент ретрансляции хрупкий | . | Много хопов (4+) | Длинный путь — подумай о перемещении ноды для его сокращения | . | Другой путь при повторе | Сеть адаптируется — существуют несколько маршрутов (это хорошо!) | . 💡 Совет: Запусти трассировку несколько раз в течение нескольких минут. Если путь изменяется, у твоей сети есть лишние маршруты — признак хорошо связанной сети. Устранение неполадок с трассировкой . | '’Маршрут не найден’‘ — Целевая нода может быть оффлайн, находиться вне зоны действия или на другом канале. Проверь, что обе ноды имеют хотя бы один канал с одинаковым ключом шифрования. | Время ожидания трассировки истекло — путь может быть слишком длинным (превышен лимит хопов) или нода ретрансляции перегружена. Попробуй увеличить лимит хопов в Настройки → Конфигурация LoRa. | Асимметричные маршруты — трассировка от A→B может проходить по другому пути, чем B→A. Это нормально — распространение радиоволн не всегда симметрично. | . ", "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.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/discovery.html#трассировка-маршрута" - },"1537": { + },"1465": { "doc": "Обнаружение", "title": "Информация об окружении", "content": "Модуль информации о соседях позволяет каждой ноде передавать список нод, которые она может слышать напрямую (на расстоянии одного хопа). Когда несколько нод делятся своими списками соседей, ты можешь составить карту топологии всей mesh-сети. Включение информации о соседях . | Перейдите в Настройки → Конфигурация модуля → Информация о соседях. | Включение модуля | Установите интервал передачи (по умолчанию: 900 секунд / 15 минут). | . После включения твоя нода периодически передаёт свою таблицу соседей. Другие ноды с включённым модулем информации о соседях делают то же самое. Просмотр данных соседа . | Откройте экран сведений любой ноды и найдите раздел “Соседи”. | Каждая запись о соседе показывает ноду, которая была услышана напрямую, и качество её сигнала. | Объединяйте данные о соседях от нескольких нод, чтобы понять полную топологию mesh-сети. | . ⚠️ Примечание: Информация о соседях увеличивает использование эфирного времени, поскольку каждая включённая нода периодически передаёт свой список соседей. В загруженных mesh-сетях с большим количеством нод рассмотрите более длинные интервалы передачи (3600 секунд или более), чтобы избежать перегрузки. ", "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.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/discovery.html#информация-об-окружении" - },"1538": { + },"1466": { "doc": "Обнаружение", "title": "Список узлов как инструмент для обзора", "content": "Сам по себе список нод — мощный инструмент обнаружения, если ты эффективно будешь использовать его возможности фильтрации и сортировки. Поиск новых узлов . | Сортируйте по “Последнему приёму”, чтобы увидеть вверху списка ноды, активные в последнее время. | Включите “Включая неизвестные”, чтобы увидеть ноды, которые появились в mesh-сети, но ещё не передали информацию о пользователе — часто это недавно включённые устройства. | . Оценка подключения . | Сортируйте по «Хопам», чтобы видеть, какие ноды доступны напрямую (0 хопов), а какие — через ретрансляцию. | Сортируйте по “Расстоянию”, чтобы найти близлежащие ноды и убедиться, что они доступны. | Используйте “Исключить MQTT”, чтобы сосредоточиться на нодах, доступных по радио (а не через интернет-мост). | . Аудит инфраструктуры . | Отключите “Исключить инфраструктуру”, чтобы увидеть ноды Router, Router Late и Client Base. | Проверьте качество их сигнала и время последнего приёма, чтобы убедиться, что твои ноды инфраструктуры работают исправно. | . См. раздел Ноды для получения полной информации о параметрах фильтрации и сортировки. ", "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.html#%D1%81%D0%BF%D0%B8%D1%81%D0%BE%D0%BA-%D1%83%D0%B7%D0%BB%D0%BE%D0%B2-%D0%BA%D0%B0%D0%BA-%D0%B8%D0%BD%D1%81%D1%82%D1%80%D1%83%D0%BC%D0%B5%D0%BD%D1%82-%D0%B4%D0%BB%D1%8F-%D0%BE%D0%B1%D0%B7%D0%BE%D1%80%D0%B0", "relUrl": "/ru-rRU/user/discovery.html#список-узлов-как-инструмент-для-обзора" - },"1539": { + },"1467": { "doc": "Обнаружение", "title": "Советы по исследованию сети", "content": ". | Начните с трассировки — она даёт тебе немедленную, пригодную для использования информацию о конкретном пути. | Включите информацию о соседях на ключевых нодах — особенно на роутерах и ретрансляторах, чтобы составить картину магистральной сети. | Проверьте карту — расположение нод на Карте в сочетании с данными о сигнале помогает тебе понять, почему одни соединения сильные, а другие слабые. | Сравнивайте сигнал с течением времени — используйте руководство по Измерителю сигнала для правильной интерпретации значений SNR и RSSI. | . ", "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.html#%D1%81%D0%BE%D0%B2%D0%B5%D1%82%D1%8B-%D0%BF%D0%BE-%D0%B8%D1%81%D1%81%D0%BB%D0%B5%D0%B4%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D1%8E-%D1%81%D0%B5%D1%82%D0%B8", "relUrl": "/ru-rRU/user/discovery.html#советы-по-исследованию-сети" - },"1540": { + },"1468": { "doc": "Discovery", "title": "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 radio 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", + "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html", - "relUrl": "/nl-rNL/user/discovery.html" - },"1541": { + "relUrl": "/ko-rKR/user/discovery.html" + },"1469": { "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#local-mesh-discovery-scanner", - "relUrl": "/nl-rNL/user/discovery.html#local-mesh-discovery-scanner" - },"1542": { + "relUrl": "/ko-rKR/user/discovery.html#local-mesh-discovery-scanner" + },"1470": { "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#mesh-beacon", + "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#mesh-beacon", - "relUrl": "/nl-rNL/user/discovery.html#mesh-beacon" - },"1543": { + "relUrl": "/ko-rKR/user/discovery.html#mesh-beacon" + },"1471": { "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#manual-exploration", + "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#manual-exploration", - "relUrl": "/nl-rNL/user/discovery.html#manual-exploration" - },"1544": { + "relUrl": "/ko-rKR/user/discovery.html#manual-exploration" + },"1472": { "doc": "Discovery", - "title": "Traceroute", + "title": "추적 루트", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#traceroute", + "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#%EC%B6%94%EC%A0%81-%EB%A3%A8%ED%8A%B8", - "relUrl": "/nl-rNL/user/discovery.html#traceroute" - },"1545": { + "relUrl": "/ko-rKR/user/discovery.html#추적-루트" + },"1473": { "doc": "Discovery", - "title": "Neighbor Info", + "title": "이웃 정보", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#neighbor-info", + "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#%EC%9D%B4%EC%9B%83-%EC%A0%95%EB%B3%B4", - "relUrl": "/nl-rNL/user/discovery.html#neighbor-info" - },"1546": { + "relUrl": "/ko-rKR/user/discovery.html#이웃-정보" + },"1474": { "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#node-list-as-a-discovery-tool", - "relUrl": "/nl-rNL/user/discovery.html#node-list-as-a-discovery-tool" - },"1547": { + "relUrl": "/ko-rKR/user/discovery.html#node-list-as-a-discovery-tool" + },"1475": { "doc": "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", + "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#tips-for-mesh-exploration", - "relUrl": "/nl-rNL/user/discovery.html#tips-for-mesh-exploration" + "relUrl": "/ko-rKR/user/discovery.html#tips-for-mesh-exploration" + },"1476": { + "doc": "Discovery", + "title": "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 radio 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" + },"1477": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/hr-rHR/user/discovery.html#local-mesh-discovery-scanner" + },"1478": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#mesh-beacon", + + "relUrl": "/hr-rHR/user/discovery.html#mesh-beacon" + },"1479": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#manual-exploration", + + "relUrl": "/hr-rHR/user/discovery.html#manual-exploration" + },"1480": { + "doc": "Discovery", + "title": "Traceroute", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#traceroute", + + "relUrl": "/hr-rHR/user/discovery.html#traceroute" + },"1481": { + "doc": "Discovery", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#neighbor-info", + + "relUrl": "/hr-rHR/user/discovery.html#neighbor-info" + },"1482": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/hr-rHR/user/discovery.html#node-list-as-a-discovery-tool" + },"1483": { + "doc": "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" + },"1484": { + "doc": "Discovery", + "title": "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 radio 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" + },"1485": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/sq-rAL/user/discovery.html#local-mesh-discovery-scanner" + },"1486": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#mesh-beacon", + + "relUrl": "/sq-rAL/user/discovery.html#mesh-beacon" + },"1487": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#manual-exploration", + + "relUrl": "/sq-rAL/user/discovery.html#manual-exploration" + },"1488": { + "doc": "Discovery", + "title": "Traceroute", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#traceroute", + + "relUrl": "/sq-rAL/user/discovery.html#traceroute" + },"1489": { + "doc": "Discovery", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#neighbor-info", + + "relUrl": "/sq-rAL/user/discovery.html#neighbor-info" + },"1490": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/sq-rAL/user/discovery.html#node-list-as-a-discovery-tool" + },"1491": { + "doc": "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" + },"1492": { + "doc": "Discovery", + "title": "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 radio 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" + },"1493": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/no-rNO/user/discovery.html#local-mesh-discovery-scanner" + },"1494": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#mesh-beacon", + + "relUrl": "/no-rNO/user/discovery.html#mesh-beacon" + },"1495": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#manual-exploration", + + "relUrl": "/no-rNO/user/discovery.html#manual-exploration" + },"1496": { + "doc": "Discovery", + "title": "Traceroute", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#traceroute", + + "relUrl": "/no-rNO/user/discovery.html#traceroute" + },"1497": { + "doc": "Discovery", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#neighbor-info", + + "relUrl": "/no-rNO/user/discovery.html#neighbor-info" + },"1498": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/no-rNO/user/discovery.html#node-list-as-a-discovery-tool" + },"1499": { + "doc": "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" + },"1500": { + "doc": "Discovery", + "title": "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 radio 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" + },"1501": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/lt-rLT/user/discovery.html#local-mesh-discovery-scanner" + },"1502": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#mesh-beacon", + + "relUrl": "/lt-rLT/user/discovery.html#mesh-beacon" + },"1503": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#manual-exploration", + + "relUrl": "/lt-rLT/user/discovery.html#manual-exploration" + },"1504": { + "doc": "Discovery", + "title": "Žinutės kelias", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#%C5%BEinut%C4%97s-kelias", + + "relUrl": "/lt-rLT/user/discovery.html#žinutės-kelias" + },"1505": { + "doc": "Discovery", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#neighbor-info", + + "relUrl": "/lt-rLT/user/discovery.html#neighbor-info" + },"1506": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/lt-rLT/user/discovery.html#node-list-as-a-discovery-tool" + },"1507": { + "doc": "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" + },"1508": { + "doc": "Discovery", + "title": "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 radio 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" + },"1509": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/ar-rSA/user/discovery.html#local-mesh-discovery-scanner" + },"1510": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#mesh-beacon", + + "relUrl": "/ar-rSA/user/discovery.html#mesh-beacon" + },"1511": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#manual-exploration", + + "relUrl": "/ar-rSA/user/discovery.html#manual-exploration" + },"1512": { + "doc": "Discovery", + "title": "Traceroute", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#traceroute", + + "relUrl": "/ar-rSA/user/discovery.html#traceroute" + },"1513": { + "doc": "Discovery", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#neighbor-info", + + "relUrl": "/ar-rSA/user/discovery.html#neighbor-info" + },"1514": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/ar-rSA/user/discovery.html#node-list-as-a-discovery-tool" + },"1515": { + "doc": "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" + },"1516": { + "doc": "Discovery", + "title": "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 radio 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" + },"1517": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/pt-rPT/user/discovery.html#local-mesh-discovery-scanner" + },"1518": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#mesh-beacon", + + "relUrl": "/pt-rPT/user/discovery.html#mesh-beacon" + },"1519": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#manual-exploration", + + "relUrl": "/pt-rPT/user/discovery.html#manual-exploration" + },"1520": { + "doc": "Discovery", + "title": "Traçar rota", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#tra%C3%A7ar-rota", + + "relUrl": "/pt-rPT/user/discovery.html#traçar-rota" + },"1521": { + "doc": "Discovery", + "title": "Informações da vizinhança", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#informa%C3%A7%C3%B5es-da-vizinhan%C3%A7a", + + "relUrl": "/pt-rPT/user/discovery.html#informações-da-vizinhança" + },"1522": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/pt-rPT/user/discovery.html#node-list-as-a-discovery-tool" + },"1523": { + "doc": "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" + },"1524": { + "doc": "Discovery", + "title": "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 radio 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" + },"1525": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/iw-rIL/user/discovery.html#local-mesh-discovery-scanner" + },"1526": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#mesh-beacon", + + "relUrl": "/iw-rIL/user/discovery.html#mesh-beacon" + },"1527": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#manual-exploration", + + "relUrl": "/iw-rIL/user/discovery.html#manual-exploration" + },"1528": { + "doc": "Discovery", + "title": "בדיקת מסלול", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.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/discovery.html#בדיקת-מסלול" + },"1529": { + "doc": "Discovery", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#neighbor-info", + + "relUrl": "/iw-rIL/user/discovery.html#neighbor-info" + },"1530": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/iw-rIL/user/discovery.html#node-list-as-a-discovery-tool" + },"1531": { + "doc": "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" + },"1532": { + "doc": "Discovery", + "title": "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 radio 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" + },"1533": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/el-rGR/user/discovery.html#local-mesh-discovery-scanner" + },"1534": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#mesh-beacon", + + "relUrl": "/el-rGR/user/discovery.html#mesh-beacon" + },"1535": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#manual-exploration", + + "relUrl": "/el-rGR/user/discovery.html#manual-exploration" + },"1536": { + "doc": "Discovery", + "title": "Traceroute", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#traceroute", + + "relUrl": "/el-rGR/user/discovery.html#traceroute" + },"1537": { + "doc": "Discovery", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#neighbor-info", + + "relUrl": "/el-rGR/user/discovery.html#neighbor-info" + },"1538": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/el-rGR/user/discovery.html#node-list-as-a-discovery-tool" + },"1539": { + "doc": "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" + },"1540": { + "doc": "Descoperiți", + "title": "Descoperiți", + "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 radio 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" + },"1541": { + "doc": "Descoperiți", + "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/ro-rRO/user/discovery.html#local-mesh-discovery-scanner" + },"1542": { + "doc": "Descoperiți", + "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#mesh-beacon", + + "relUrl": "/ro-rRO/user/discovery.html#mesh-beacon" + },"1543": { + "doc": "Descoperiți", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#manual-exploration", + + "relUrl": "/ro-rRO/user/discovery.html#manual-exploration" + },"1544": { + "doc": "Descoperiți", + "title": "Trasare traseu", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#trasare-traseu", + + "relUrl": "/ro-rRO/user/discovery.html#trasare-traseu" + },"1545": { + "doc": "Descoperiți", + "title": "Informații vecin", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#informa%C8%9Bii-vecin", + + "relUrl": "/ro-rRO/user/discovery.html#informații-vecin" + },"1546": { + "doc": "Descoperiți", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/ro-rRO/user/discovery.html#node-list-as-a-discovery-tool" + },"1547": { + "doc": "Descoperiți", + "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" },"1548": { "doc": "Avastamine", "title": "Avastamine", @@ -10894,2186 +10894,2186 @@ "doc": "Discovery", "title": "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 radio 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html", - "relUrl": "/it-rIT/user/discovery.html" + "relUrl": "/ga-rIE/user/discovery.html" },"1557": { "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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. | . | Utilizzo 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#local-mesh-discovery-scanner", - "relUrl": "/it-rIT/user/discovery.html#local-mesh-discovery-scanner" + "relUrl": "/ga-rIE/user/discovery.html#local-mesh-discovery-scanner" },"1558": { "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#mesh-beacon", + "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#mesh-beacon", - "relUrl": "/it-rIT/user/discovery.html#mesh-beacon" + "relUrl": "/ga-rIE/user/discovery.html#mesh-beacon" },"1559": { "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#manual-exploration", + "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#manual-exploration", - "relUrl": "/it-rIT/user/discovery.html#manual-exploration" + "relUrl": "/ga-rIE/user/discovery.html#manual-exploration" },"1560": { "doc": "Discovery", - "title": "Traceroute", + "title": "Céim rianadóireachta", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#traceroute", + "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#c%C3%A9im-rianad%C3%B3ireachta", - "relUrl": "/it-rIT/user/discovery.html#traceroute" + "relUrl": "/ga-rIE/user/discovery.html#céim-rianadóireachta" },"1561": { "doc": "Discovery", - "title": "Informazioni Vicinato", + "title": "Neighbor Info", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#informazioni-vicinato", + "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#neighbor-info", - "relUrl": "/it-rIT/user/discovery.html#informazioni-vicinato" + "relUrl": "/ga-rIE/user/discovery.html#neighbor-info" },"1562": { "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#node-list-as-a-discovery-tool", - "relUrl": "/it-rIT/user/discovery.html#node-list-as-a-discovery-tool" + "relUrl": "/ga-rIE/user/discovery.html#node-list-as-a-discovery-tool" },"1563": { "doc": "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/it-rIT/user/discovery.html#tips-for-mesh-exploration", + "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#tips-for-mesh-exploration", - "relUrl": "/it-rIT/user/discovery.html#tips-for-mesh-exploration" + "relUrl": "/ga-rIE/user/discovery.html#tips-for-mesh-exploration" },"1564": { - "doc": "Discovery", - "title": "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 radio 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" - },"1565": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/ar-rSA/user/discovery.html#local-mesh-discovery-scanner" - },"1566": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#mesh-beacon", - - "relUrl": "/ar-rSA/user/discovery.html#mesh-beacon" - },"1567": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#manual-exploration", - - "relUrl": "/ar-rSA/user/discovery.html#manual-exploration" - },"1568": { - "doc": "Discovery", - "title": "Traceroute", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#traceroute", - - "relUrl": "/ar-rSA/user/discovery.html#traceroute" - },"1569": { - "doc": "Discovery", - "title": "Neighbor Info", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#neighbor-info", - - "relUrl": "/ar-rSA/user/discovery.html#neighbor-info" - },"1570": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/ar-rSA/user/discovery.html#node-list-as-a-discovery-tool" - },"1571": { - "doc": "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" - },"1572": { - "doc": "Discovery", - "title": "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 radio 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" - },"1573": { - "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#local-mesh-discovery-scanner", - - "relUrl": "/sk-rSK/user/discovery.html#local-mesh-discovery-scanner" - },"1574": { - "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#mesh-beacon", - - "relUrl": "/sk-rSK/user/discovery.html#mesh-beacon" - },"1575": { - "doc": "Discovery", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#manual-exploration", - - "relUrl": "/sk-rSK/user/discovery.html#manual-exploration" - },"1576": { - "doc": "Discovery", - "title": "Trasovanie", - "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#trasovanie", - - "relUrl": "/sk-rSK/user/discovery.html#trasovanie" - },"1577": { - "doc": "Discovery", - "title": "Informácia o susedoch", - "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#inform%C3%A1cia-o-susedoch", - - "relUrl": "/sk-rSK/user/discovery.html#informácia-o-susedoch" - },"1578": { - "doc": "Discovery", - "title": "Node List as a Discovery Tool", - "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", - - "relUrl": "/sk-rSK/user/discovery.html#node-list-as-a-discovery-tool" - },"1579": { - "doc": "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" - },"1580": { "doc": "Discovery", "title": "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 radio 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" - },"1581": { + },"1565": { "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html#local-mesh-discovery-scanner", "relUrl": "/pl-rPL/user/discovery.html#local-mesh-discovery-scanner" - },"1582": { + },"1566": { "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html#mesh-beacon", "relUrl": "/pl-rPL/user/discovery.html#mesh-beacon" - },"1583": { + },"1567": { "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html#manual-exploration", "relUrl": "/pl-rPL/user/discovery.html#manual-exploration" - },"1584": { + },"1568": { "doc": "Discovery", "title": "Pokaż trasę", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html#poka%C5%BC-tras%C4%99", "relUrl": "/pl-rPL/user/discovery.html#pokaż-trasę" - },"1585": { + },"1569": { "doc": "Discovery", "title": "Informacje o sąsiadze", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html#informacje-o-s%C4%85siadze", "relUrl": "/pl-rPL/user/discovery.html#informacje-o-sąsiadze" - },"1586": { + },"1570": { "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", "relUrl": "/pl-rPL/user/discovery.html#node-list-as-a-discovery-tool" - },"1587": { + },"1571": { "doc": "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" + },"1572": { + "doc": "Discovery", + "title": "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 radio 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" + },"1573": { + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/nl-rNL/user/discovery.html#local-mesh-discovery-scanner" + },"1574": { + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#mesh-beacon", + + "relUrl": "/nl-rNL/user/discovery.html#mesh-beacon" + },"1575": { + "doc": "Discovery", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#manual-exploration", + + "relUrl": "/nl-rNL/user/discovery.html#manual-exploration" + },"1576": { + "doc": "Discovery", + "title": "Traceroute", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#traceroute", + + "relUrl": "/nl-rNL/user/discovery.html#traceroute" + },"1577": { + "doc": "Discovery", + "title": "Neighbor Info", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#neighbor-info", + + "relUrl": "/nl-rNL/user/discovery.html#neighbor-info" + },"1578": { + "doc": "Discovery", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/nl-rNL/user/discovery.html#node-list-as-a-discovery-tool" + },"1579": { + "doc": "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" + },"1580": { + "doc": "Upptäckt", + "title": "Upptäckt", + "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 radio 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" + },"1581": { + "doc": "Upptäckt", + "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#local-mesh-discovery-scanner", + + "relUrl": "/sv-rSE/user/discovery.html#local-mesh-discovery-scanner" + },"1582": { + "doc": "Upptäckt", + "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#mesh-beacon", + + "relUrl": "/sv-rSE/user/discovery.html#mesh-beacon" + },"1583": { + "doc": "Upptäckt", + "title": "Manual Exploration", + "content": "The tools below 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. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#manual-exploration", + + "relUrl": "/sv-rSE/user/discovery.html#manual-exploration" + },"1584": { + "doc": "Upptäckt", + "title": "Traceroute (spåra rutt)", + "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#traceroute-sp%C3%A5ra-rutt", + + "relUrl": "/sv-rSE/user/discovery.html#traceroute-spåra-rutt" + },"1585": { + "doc": "Upptäckt", + "title": "Granninformation", + "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#granninformation", + + "relUrl": "/sv-rSE/user/discovery.html#granninformation" + },"1586": { + "doc": "Upptäckt", + "title": "Node List as a Discovery Tool", + "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + + "relUrl": "/sv-rSE/user/discovery.html#node-list-as-a-discovery-tool" + },"1587": { + "doc": "Upptäckt", + "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" },"1588": { - "doc": "尋找", - "title": "尋找", - "content": "探索工具可協助您了解 mesh 網路的連線方式——哪些節點彼此可以收到訊號、訊息所經過的路徑，以及哪裡存在瓶頸或訊號薄弱的連結。 . The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected radio 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", + "doc": "探索", + "title": "探索", + "content": "探索ツールは、メッシュネットワークがどのようにつながっているか（どのノードが互いに受信できるか、メッセージがどの経路を通るか、ボトルネックや弱いリンクがどこにあるか）を把握するのに役立ちます。 . アプリは、互いを補完する 2 つの方法を提供します： . | ローカルメッシュ探索（スキャナー）：接続中の無線機をさまざまな LoRa プリセットで順に切り替え、それぞれで受信し、あなたの場所でどのプリセットが最も性能が良いかをランク付けする自動モードです。 | 手動での探索：ルート追跡、隣接ノード情報、ノードリスト。特定の経路やトポロジーを調べるために、いつでも使えます。 | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html", - "relUrl": "/zh-rTW/user/discovery.html" + "relUrl": "/ja-rJP/user/discovery.html" },"1589": { - "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 解讀結果 . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#local-mesh-discovery-scanner", + "doc": "探索", + "title": "ローカルメッシュ探索（スキャナー）", + "content": "ローカルメッシュ探索は、あなたの場所に最適な LoRa モデムプリセットを見つけ、各プリセットでどのノードがアクティブかを確認できる、専用のスキャンモードです。 接続中の無線機を、選択した 1 つ以上のプリセットで順に切り替え、パケットを収集するために各プリセットで一定時間受信（「滞在」）し、その後、結果を分析してランク付けします。 . 「設定 → 詳細設定 → ローカルメッシュ探索」から開きます。 デスクトップでは、独自の「設定 → ローカルメッシュ探索」の項目があります。 . ⚠️ 注意： 探索は、スキャン中に無線機の LoRa 設定を一時的に変更し、完了時に元の構成に戻します。 スキャンを実行するには、デバイスが接続されている必要があります。 . スキャンを設定する . 開始する前に、次のコントロールを設定します： . | コントロール | 説明 | . | LoRa プリセットの選択 | スキャンするプリセットを 1 つ以上選択します。 探索は、選択した各プリセットに順番に滞在します。 | . | 滞在時間 | 各プリセットで受信する時間。 1、5、15、30、45、60、90、120、180 分から選択します。 滞在時間を長くすると、より多くのパケットを収集してより明確な状況が分かりますが、時間もかかります。 | . | 画面をスリープさせない | 長いスキャン中に画面がスリープするのを防ぐ、任意のトグルです。 | . 「開始」ボタンは、スキャンを実行できるようになるまで（理由の説明とともに）無効のままです。 無効になる主な理由： . | デバイスが接続されていない。 | スキャンするプリセットが選択されていない。 | 選択したプリセットが、ハードウェアが対応していない 2.4 GHz を使用している。 | . リアルタイムの進行状況 . スキャンの実行中、探索は現在の段階を表示します： . | 段階 | 実行中の内容 | . | 準備中 | 現在の構成を保存し、スキャンの準備をしています。 | . | <preset> に切り替え中 | テストする次のプリセットに無線機を切り替えています。 | . | 再接続中 | プリセット変更後に接続を再確立しています。 | . | 滞在 | 現在のプリセットで受信してパケットを収集しており、次のステップまでのカウントダウンが表示されます。 | . | 分析 | 収集したパケットを処理し、プリセットをランク付けしています。 | . | 復元中 | 元の LoRa 構成に戻しています。 | . 結果の見方 . スキャンが完了すると、探索はテストした各プリセットのプリセット別の結果カードと、全体の概要を表示します。 . メトリクスには次が含まれます： . | メトリクス | 分かること | . | RF の健全性 | そのプリセットにおける無線環境の総合的な品質。 | . | チャンネル利用率 | 滞在中に電波がどれだけ混雑していたか。 | . | 電波利用時間 | 観測された送信時間。 | . | 直接受信と中継ノード | 直接受信できたメッシュノードと、中継経由のノードの数。 | . | 不良／重複パケット | 破損したパケットと繰り返されたパケットの数で、輻輳や干渉を示します。 | . 結果から利用できる追加機能： . | スキャン履歴：後で見直せる保存済みのセッション。過去のスキャンを表示または削除できます。 | 探索マップ：スキャン中に見つかったノードのマップ。 | レポートのエクスポート：Android では PDF として、他のプラットフォームではテキストとしてレポートをエクスポートします。 | . 💡 ヒント： Android では、探索が結果のオンデバイス AI 要約（Gemini Nano）を生成できます。 オンデバイスのモデルが利用できない場合は、代わりにアルゴリズムによる要約が使われるため、常にスキャンの読みやすい解釈が得られます。 . ", + "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": "/zh-rTW/user/discovery.html#local-mesh-discovery-scanner" + "relUrl": "/ja-rJP/user/discovery.html#ローカルメッシュ探索スキャナー" },"1590": { - "doc": "尋找", - "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#mesh-beacon", + "doc": "探索", + "title": "メッシュビーコン", + "content": "メッシュビーコンを使うと、ノードが他のノードを自分のメッシュに招待できます。 ビーコンを発信するノードは、招待を定期的にブロードキャストします（任意でチャンネル、リージョン、モデムプリセットを告知）。近くのデバイスは、設定を共有する前でもこれを受信できます。 . 「設定 → モジュール設定 → メッシュビーコン」で設定します： . | ビーコンを受信：他のノードがブロードキャストする招待を受け取ります。 | ビーコンを発信：一定間隔で自分の招待を送信します。任意でメッセージと提示するチャンネルを設定できます。 | . 受信した招待は、探索画面に「メッシュへの招待」カードとして表示されます。 各カードには、送信者のメッセージと、提示されたチャンネル・リージョン・プリセット・信号品質が表示され、次の操作ができます： . | 参加：提示されたチャンネルとプリセットに切り替えます（無線機を再調整して再起動します）。 提示内容が現在の周波数スロットと一致する場合は、再起動なしで追加できる「チャンネルを追加」の操作が表示されます。 | 探索：提示されたプリセットで探索スキャンを開始し、参加する前にそのメッシュを調べられます（ビーコンがプリセットを提示している場合のみ表示）。 | 閉じる：招待を無視します。 | . ビーコンが告知したチャンネルは、スキャン設定にも「ビーコンのチャンネル」として表示されます。選択すると、スキャン対象に含められます。 . ", + "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": "/zh-rTW/user/discovery.html#mesh-beacon" + "relUrl": "/ja-rJP/user/discovery.html#メッシュビーコン" },"1591": { - "doc": "尋找", - "title": "Manual Exploration", - "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#manual-exploration", + "doc": "探索", + "title": "手動での探索", + "content": "以下のツールは、ノードリストとノードの詳細画面からいつでも利用できます。 完全なスキャンと併用して、またはその代わりに、特定の経路を調べてトポロジーの全体像を組み立てるのに使えます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E6%89%8B%E5%8B%95%E3%81%A7%E3%81%AE%E6%8E%A2%E7%B4%A2", - "relUrl": "/zh-rTW/user/discovery.html#manual-exploration" + "relUrl": "/ja-rJP/user/discovery.html#手動での探索" },"1592": { - "doc": "尋找", - "title": "路由追蹤", - "content": "路由追蹤可顯示訊息從您的節點到 mesh 網路上任一節點所經過的確切路徑。 這是診斷連線問題最有效的工具。 . 執行路由追蹤 . | 前往「節點」，並點選您要追蹤的節點。 | 在節點詳細資訊畫面上，點選「路由追蹤」。 | 應用程式將發送路由追蹤請求並等待回應。 | 結果將依序顯示每一個跳躍點，並呈現每個步驟的訊號品質。 | . 解讀結果 . 路由追蹤結果的顯示方式如下： . 你 → 裝置 A (SNR: 8.5, RSSI: -95) → 裝置 B (SNR: 5.2, RSSI: -108) → 目標 . 每個跳躍點代表一個轉送該訊息的中繼節點。 每個跳躍點的 SNR 與 RSSI 數值可反映該路段的連線品質。 . | 判讀重點 | 代表意義 | . | All hops show Good SNR (≥ −7 dB, green) | 路徑狀況良好 — 訊息可穩定傳送 | . | One hop shows Bad SNR (< −15 dB, red) | 訊號薄弱 — 此中繼路段不穩定 | . | 跳躍點過多（4 個以上） | 路徑過長 — 建議調整節點位置以縮短路徑 | . | 重試時走不同路徑 | Mesh 網路正在自動調整 — 存在多條路由（這是好現象！） | . 💡 提示：請在幾分鐘內多次執行路由追蹤。 若路徑發生變化，代表您的 mesh 網路具備備援路由 — 這是網路連線良好的象徵。 . 使用路由追蹤進行疑難排解 . | 「找不到路由」— 目標節點可能已離線、超出範圍，或使用不同的頻道。 請確認兩個節點至少共用一個使用相同加密金鑰的頻道。 | 「路由追蹤逾時」— 路徑可能過長（超過跳躍限制），或某中繼節點發生壅塞。 請嘗試在「設定 → LoRa 設定」中提高跳躍限制。 | 非對稱路徑 — 從 A → B 的路由追蹤路徑，可能與 B → A 不同。 這屬於正常現象 — 無線電訊號的傳播並不總是對稱的。 | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#%E8%B7%AF%E7%94%B1%E8%BF%BD%E8%B9%A4", + "doc": "探索", + "title": "ルート追跡", + "content": "ルート追跡は、メッセージが自分のノードから、メッシュ上の他の任意のノードへ通る正確な経路を明らかにします。 接続の問題をデバッグするのに、最も役立つツールです。 . ルート追跡を実行する . | 「ノード」に移動し、追跡したいノードをタップします。 | ノードの詳細画面で、「ルート追跡」をタップします。 | アプリがルート追跡の要求を送信し、応答を待ちます。 | 結果には、各ホップが順番に、各段階の信号品質とともに表示されます。 | . 結果の見方 . ルート追跡の結果は次のように表示されます： . 自分 → ノード A (SNR: 8.5, RSSI: -95) → ノード B (SNR: 5.2, RSSI: -108) → ターゲット . 各ホップは、メッセージを転送した中継ノードを表します。 各ホップの SNR と RSSI の値から、その特定の区間のリンク品質が分かります。 . | 確認すべき点 | 意味 | . | すべてのホップが良い SNR（−7 dB 以上、緑）を示す | 健全な経路。メッセージが確実に流れます | . | 1 つのホップが悪い SNR（−15 dB 未満、赤）を示す | 弱いリンク。この中継区間は脆弱です | . | ホップ数が多い（4 以上） | 長い経路。短くするためにノードの再配置を検討してください | . | 再試行で経路が変わる | メッシュが適応しています。複数の経路が存在します（これは良いことです！） | . 💡 ヒント： ルート追跡を数分間かけて何度か実行してください。 経路が変わる場合、メッシュには冗長な経路があり、よくつながったネットワークの兆候です。 . ルート追跡によるトラブルシューティング . | 「経路が見つかりません」：対象のノードがオフラインか、圏外か、別のチャンネルにいる可能性があります。 両方のノードが、同じ暗号化鍵を持つチャンネルを少なくとも 1 つ共有しているか確認してください。 | ルート追跡がタイムアウトする：経路が長すぎる（ホップ数上限を超える）か、中継ノードが混雑している可能性があります。 「設定 → LoRa 設定」でホップ数上限を増やしてみてください。 | 非対称な経路：A→B のルート追跡は、B→A とは異なる経路を通ることがあります。 これは正常です。電波の伝搬は常に対称とは限りません。 | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E3%83%AB%E3%83%BC%E3%83%88%E8%BF%BD%E8%B7%A1", - "relUrl": "/zh-rTW/user/discovery.html#路由追蹤" + "relUrl": "/ja-rJP/user/discovery.html#ルート追跡" },"1593": { - "doc": "尋找", - "title": "鄰近節點資訊", - "content": "鄰近節點資訊模組可讓每個節點廣播其可直接收到訊號的節點清單（單跳躍）。 當多個節點共享各自的鄰近節點清單時，您便可拼湊出整個 mesh 網路的拓撲圖。 . 啟用鄰近節點資訊 . | 前往「設定 → 模組設定 → 鄰近節點資訊」。 | 啟用此模組。 | 設定廣播間隔（預設：900 秒 / 15 分鐘）。 | . 啟用後，您的節點將定期廣播其鄰近節點列表。 其他已啟用鄰近節點資訊的節點也會執行相同動作。 . 檢視鄰近節點資料 . | 開啟任一節點的詳細資訊畫面，並尋找「鄰近節點」區段。 | 每筆鄰近節點記錄會顯示可直接收到訊號的節點及其訊號品質。 | 結合多個節點的鄰近節點資料，以了解完整的 mesh 網路拓撲。 | . ⚠️ 注意：鄰近節點資訊會增加無線電佔用時間，因為每個已啟用的節點會定期廣播其鄰近節點清單。 在節點眾多的繁忙 mesh 網路中，建議設定較長的廣播間隔（3600 秒以上）以避免壅塞。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#%E9%84%B0%E8%BF%91%E7%AF%80%E9%BB%9E%E8%B3%87%E8%A8%8A", + "doc": "探索", + "title": "隣接ノード情報", + "content": "隣接ノード情報モジュールを使うと、各ノードが直接受信できる（シングルホップの）ノードのリストをブロードキャストできます。 複数のノードが隣接ノードのリストを共有すると、メッシュ全体のトポロジーマップを組み立てられます。 . 隣接ノード情報を有効にする . | 「設定 → モジュール設定 → 隣接ノード情報」に移動します。 | モジュールを有効にします。 | ブロードキャスト間隔を設定します（デフォルト：900 秒／15 分）。 | . 有効にすると、ノードは隣接ノードのテーブルを定期的にブロードキャストします。 隣接ノード情報を有効にしている他のノードも、同じことを行います。 . 隣接ノードのデータを表示する . | 任意のノードの詳細画面を開き、「隣接ノード」セクションを探します。 | 各隣接ノードの項目には、直接受信したノードとその信号品質が表示されます。 | 複数のノードの隣接ノードデータを組み合わせて、メッシュ全体のトポロジーを把握します。 | . ⚠️ 注意： 隣接ノード情報は、有効にした各ノードが隣接ノードのリストを定期的にブロードキャストするため、電波利用時間の消費が増えます。 ノードの多い混雑したメッシュでは、輻輳を避けるために、より長いブロードキャスト間隔（3600 秒以上）を検討してください。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E9%9A%A3%E6%8E%A5%E3%83%8E%E3%83%BC%E3%83%89%E6%83%85%E5%A0%B1", - "relUrl": "/zh-rTW/user/discovery.html#鄰近節點資訊" + "relUrl": "/ja-rJP/user/discovery.html#隣接ノード情報" },"1594": { - "doc": "尋找", - "title": "將節點清單作為探索工具", - "content": "善用節點清單的篩選與排序功能，即可將其作為強大的探索工具。 . 尋找新節點 . | 依「最後收到訊號」排序，可將最近有活動的節點顯示於頂部。 | 啟用「包含未知節點」，可顯示已出現於 mesh 網路但尚未傳送使用者資訊的節點 — 這些通常是剛開機的裝置。 | . 評估連線狀況 . | 依「跳躍距離」排序，可區分可直接到達的節點（0 個跳躍點）與需中繼轉送的節點。 | 依「距離」排序，可找出附近的節點並確認是否可到達。 | 使用「排除 MQTT」，可專注於透過無線電（而非網際網路橋接）可到達的節點。 | . 基礎架構稽核 . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | 檢查其訊號品質與最後收到訊號的時間，以確認基礎架構節點運作正常。 | . 請參閱〔節點〕(nodes) 以了解完整的篩選與排序選項說明。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#%E5%B0%87%E7%AF%80%E9%BB%9E%E6%B8%85%E5%96%AE%E4%BD%9C%E7%82%BA%E6%8E%A2%E7%B4%A2%E5%B7%A5%E5%85%B7", + "doc": "探索", + "title": "探索ツールとしてのノードリスト", + "content": "ノードリスト自体も、絞り込みと並べ替えの機能を効果的に使えば、強力な探索ツールになります。 . 新しいノードを見つける . | 「最後の通信」で並べ替えると、最近アクティブだったノードが先頭に表示されます。 | 「不明なノードを含む」を有効にすると、メッシュに現れたもののまだユーザー情報を送信していないノードが表示されます。これらは、電源を入れたばかりのデバイスであることがよくあります。 | . 接続性を評価する . | 「ホップ数」で並べ替えると、直接到達できるノード（0 ホップ）と中継されるノードが分かります。 | 「距離」で並べ替えると、近くのノードを見つけて、到達できるか確認できます。 | 「MQTT を除外」を使うと、（インターネットブリッジ経由ではなく）無線で到達できるノードに絞り込めます。 | . インフラの監査 . | 「インフラを除外」を無効にすると、ルーター、ルーター・レイト、クライアント・ベースのノードが表示されます。 | 信号品質と最後の通信時刻を確認して、インフラのノードが健全であることを確かめます。 | . 絞り込みと並べ替えのオプションの詳細については、ノード を参照してください。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E6%8E%A2%E7%B4%A2%E3%83%84%E3%83%BC%E3%83%AB%E3%81%A8%E3%81%97%E3%81%A6%E3%81%AE%E3%83%8E%E3%83%BC%E3%83%89%E3%83%AA%E3%82%B9%E3%83%88", - "relUrl": "/zh-rTW/user/discovery.html#將節點清單作為探索工具" + "relUrl": "/ja-rJP/user/discovery.html#探索ツールとしてのノードリスト" },"1595": { - "doc": "尋找", - "title": "Mesh 網路探索技巧", - "content": ". | 從路由追蹤開始 — 可立即取得特定路徑的具體可行資訊。 | 在關鍵節點上啟用鄰近節點資訊 — 尤其是路由器與中繼器，以建立骨幹網路的整體概況。 | 查看地圖 —〔地圖〕(map-and-waypoints) 上的節點位置結合訊號資料，有助於了解為何某些連結訊號強，而其他連結訊號弱。 | 比較訊號變化趨勢 — 請參閱〔訊號儀表〕(signal-meter) 指南，以正確解讀 SNR 與 RSSI 數值。 | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#mesh-%E7%B6%B2%E8%B7%AF%E6%8E%A2%E7%B4%A2%E6%8A%80%E5%B7%A7", + "doc": "探索", + "title": "メッシュ探索のヒント", + "content": ". | まずルート追跡から：特定の経路について、すぐに役立つ情報が得られます。 | 主要なノードで隣接ノード情報を有効に：特にルーターやリピーターで有効にして、バックボーンの全体像を組み立てます。 | マップを確認：マップ 上のノードの位置と信号データを組み合わせると、なぜあるリンクは強く、別のリンクは弱いのかが分かります。 | 信号を時系列で比較：信号メーター のガイドを使って、SNR と RSSI の値を正しく解釈します。 | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E3%83%A1%E3%83%83%E3%82%B7%E3%83%A5%E6%8E%A2%E7%B4%A2%E3%81%AE%E3%83%92%E3%83%B3%E3%83%88", - "relUrl": "/zh-rTW/user/discovery.html#mesh-網路探索技巧" + "relUrl": "/ja-rJP/user/discovery.html#メッシュ探索のヒント" },"1596": { - "doc": "Objevujte", - "title": "Objevujte", + "doc": "Discovery", + "title": "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 radio 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html", - "relUrl": "/cs-rCZ/user/discovery.html" + "relUrl": "/hu-rHU/user/discovery.html" },"1597": { - "doc": "Objevujte", + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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. | . | 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#local-mesh-discovery-scanner", - "relUrl": "/cs-rCZ/user/discovery.html#local-mesh-discovery-scanner" + "relUrl": "/hu-rHU/user/discovery.html#local-mesh-discovery-scanner" },"1598": { - "doc": "Objevujte", + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#mesh-beacon", + "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#mesh-beacon", - "relUrl": "/cs-rCZ/user/discovery.html#mesh-beacon" + "relUrl": "/hu-rHU/user/discovery.html#mesh-beacon" },"1599": { - "doc": "Objevujte", + "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#manual-exploration", + "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#manual-exploration", - "relUrl": "/cs-rCZ/user/discovery.html#manual-exploration" + "relUrl": "/hu-rHU/user/discovery.html#manual-exploration" },"1600": { - "doc": "Objevujte", + "doc": "Discovery", "title": "Traceroute", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#traceroute", + "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#traceroute", - "relUrl": "/cs-rCZ/user/discovery.html#traceroute" + "relUrl": "/hu-rHU/user/discovery.html#traceroute" },"1601": { - "doc": "Objevujte", - "title": "Informace o sousedech", + "doc": "Discovery", + "title": "Szomszéd-információ", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#informace-o-sousedech", + "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#szomsz%C3%A9d-inform%C3%A1ci%C3%B3", - "relUrl": "/cs-rCZ/user/discovery.html#informace-o-sousedech" + "relUrl": "/hu-rHU/user/discovery.html#szomszéd-információ" },"1602": { - "doc": "Objevujte", + "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#node-list-as-a-discovery-tool", - "relUrl": "/cs-rCZ/user/discovery.html#node-list-as-a-discovery-tool" + "relUrl": "/hu-rHU/user/discovery.html#node-list-as-a-discovery-tool" },"1603": { - "doc": "Objevujte", + "doc": "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/cs-rCZ/user/discovery.html#tips-for-mesh-exploration", + "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#tips-for-mesh-exploration", - "relUrl": "/cs-rCZ/user/discovery.html#tips-for-mesh-exploration" + "relUrl": "/hu-rHU/user/discovery.html#tips-for-mesh-exploration" },"1604": { - "doc": "Découverte", - "title": "Découverte", + "doc": "Discovery", + "title": "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 radio 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html", - "relUrl": "/fr-rFR/user/discovery.html" + "relUrl": "/ht-rHT/user/discovery.html" },"1605": { - "doc": "Découverte", + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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. | . | 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#local-mesh-discovery-scanner", - "relUrl": "/fr-rFR/user/discovery.html#local-mesh-discovery-scanner" + "relUrl": "/ht-rHT/user/discovery.html#local-mesh-discovery-scanner" },"1606": { - "doc": "Découverte", + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#mesh-beacon", + "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#mesh-beacon", - "relUrl": "/fr-rFR/user/discovery.html#mesh-beacon" + "relUrl": "/ht-rHT/user/discovery.html#mesh-beacon" },"1607": { - "doc": "Découverte", + "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#manual-exploration", + "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#manual-exploration", - "relUrl": "/fr-rFR/user/discovery.html#manual-exploration" + "relUrl": "/ht-rHT/user/discovery.html#manual-exploration" },"1608": { - "doc": "Découverte", + "doc": "Discovery", "title": "Traceroute", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#traceroute", + "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#traceroute", - "relUrl": "/fr-rFR/user/discovery.html#traceroute" + "relUrl": "/ht-rHT/user/discovery.html#traceroute" },"1609": { - "doc": "Découverte", - "title": "Informations sur les voisins", + "doc": "Discovery", + "title": "Neighbor Info", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#informations-sur-les-voisins", + "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#neighbor-info", - "relUrl": "/fr-rFR/user/discovery.html#informations-sur-les-voisins" + "relUrl": "/ht-rHT/user/discovery.html#neighbor-info" },"1610": { - "doc": "Découverte", + "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#node-list-as-a-discovery-tool", - "relUrl": "/fr-rFR/user/discovery.html#node-list-as-a-discovery-tool" + "relUrl": "/ht-rHT/user/discovery.html#node-list-as-a-discovery-tool" },"1611": { - "doc": "Découverte", + "doc": "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/fr-rFR/user/discovery.html#tips-for-mesh-exploration", + "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#tips-for-mesh-exploration", - "relUrl": "/fr-rFR/user/discovery.html#tips-for-mesh-exploration" + "relUrl": "/ht-rHT/user/discovery.html#tips-for-mesh-exploration" },"1612": { - "doc": "发现", - "title": "发现", + "doc": "Discovery", + "title": "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 radio 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", + "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html", - "relUrl": "/zh-rCN/user/discovery.html" + "relUrl": "/gl-rES/user/discovery.html" },"1613": { - "doc": "发现", + "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#local-mesh-discovery-scanner", - "relUrl": "/zh-rCN/user/discovery.html#local-mesh-discovery-scanner" + "relUrl": "/gl-rES/user/discovery.html#local-mesh-discovery-scanner" },"1614": { - "doc": "发现", - "title": "Mesh 信标", + "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#mesh-%E4%BF%A1%E6%A0%87", + "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#mesh-beacon", - "relUrl": "/zh-rCN/user/discovery.html#mesh-信标" + "relUrl": "/gl-rES/user/discovery.html#mesh-beacon" },"1615": { - "doc": "发现", + "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#manual-exploration", + "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#manual-exploration", - "relUrl": "/zh-rCN/user/discovery.html#manual-exploration" + "relUrl": "/gl-rES/user/discovery.html#manual-exploration" },"1616": { - "doc": "发现", - "title": "追踪器", + "doc": "Discovery", + "title": "Traza-ruta", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#%E8%BF%BD%E8%B8%AA%E5%99%A8", + "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#traza-ruta", - "relUrl": "/zh-rCN/user/discovery.html#追踪器" + "relUrl": "/gl-rES/user/discovery.html#traza-ruta" },"1617": { - "doc": "发现", - "title": "邻居信息", + "doc": "Discovery", + "title": "Neighbor Info", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#%E9%82%BB%E5%B1%85%E4%BF%A1%E6%81%AF", + "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#neighbor-info", - "relUrl": "/zh-rCN/user/discovery.html#邻居信息" + "relUrl": "/gl-rES/user/discovery.html#neighbor-info" },"1618": { - "doc": "发现", + "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#node-list-as-a-discovery-tool", - "relUrl": "/zh-rCN/user/discovery.html#node-list-as-a-discovery-tool" + "relUrl": "/gl-rES/user/discovery.html#node-list-as-a-discovery-tool" },"1619": { - "doc": "发现", + "doc": "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/zh-rCN/user/discovery.html#tips-for-mesh-exploration", + "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#tips-for-mesh-exploration", - "relUrl": "/zh-rCN/user/discovery.html#tips-for-mesh-exploration" + "relUrl": "/gl-rES/user/discovery.html#tips-for-mesh-exploration" },"1620": { "doc": "Discovery", "title": "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 radio 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html", - "relUrl": "/srp/user/discovery.html" + "relUrl": "/tr-rTR/user/discovery.html" },"1621": { "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/srp/user/discovery.html#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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#local-mesh-discovery-scanner", - "relUrl": "/srp/user/discovery.html#local-mesh-discovery-scanner" + "relUrl": "/tr-rTR/user/discovery.html#local-mesh-discovery-scanner" },"1622": { "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/srp/user/discovery.html#mesh-beacon", + "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#mesh-beacon", - "relUrl": "/srp/user/discovery.html#mesh-beacon" + "relUrl": "/tr-rTR/user/discovery.html#mesh-beacon" },"1623": { "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/srp/user/discovery.html#manual-exploration", + "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#manual-exploration", - "relUrl": "/srp/user/discovery.html#manual-exploration" + "relUrl": "/tr-rTR/user/discovery.html#manual-exploration" },"1624": { "doc": "Discovery", - "title": "Праћење руте", + "title": "Yol izle", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/srp/user/discovery.html#%D0%BF%D1%80%D0%B0%D1%9B%D0%B5%D1%9A%D0%B5-%D1%80%D1%83%D1%82%D0%B5", + "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#yol-izle", - "relUrl": "/srp/user/discovery.html#праћење-руте" + "relUrl": "/tr-rTR/user/discovery.html#yol-izle" },"1625": { "doc": "Discovery", - "title": "Neighbor Info", + "title": "Komşu Bilgisi", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/srp/user/discovery.html#neighbor-info", + "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#kom%C5%9Fu-bilgisi", - "relUrl": "/srp/user/discovery.html#neighbor-info" + "relUrl": "/tr-rTR/user/discovery.html#komşu-bilgisi" },"1626": { "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#node-list-as-a-discovery-tool", - "relUrl": "/srp/user/discovery.html#node-list-as-a-discovery-tool" + "relUrl": "/tr-rTR/user/discovery.html#node-list-as-a-discovery-tool" },"1627": { "doc": "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#tips-for-mesh-exploration", - "relUrl": "/srp/user/discovery.html#tips-for-mesh-exploration" + "relUrl": "/tr-rTR/user/discovery.html#tips-for-mesh-exploration" },"1628": { "doc": "Discovery", "title": "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 radio 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", + "url": "/Meshtastic-Android/main/es-rES/user/discovery.html", - "relUrl": "/sq-rAL/user/discovery.html" + "relUrl": "/es-rES/user/discovery.html" },"1629": { "doc": "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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#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 radio through one or more presets you choose, listens (or “dwells”) on each one for a set time to collect packets, then analyzes and ranks the results. Open it from Settings → Advanced → Local Mesh Discovery. On desktop, it has its own Settings → Local Mesh Discovery entry. ⚠️ Note: Discovery temporarily changes your radio’s LoRa settings while it scans, then restores your original configuration when it finishes. Your device must be connected to run a scan. 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 | Optional toggle that prevents the screen from sleeping during a long scan. | . The Start button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The device 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 | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the radio to the next preset to test. | . | Reconnecting | Re-establishing the connection after the preset change. | . | Dwell | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analysis | Processing the collected packets and ranking the presets. | . | Restoring | Putting your original LoRa configuration back. | . 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 Android, Discovery can generate an on-device AI summary (Gemini Nano) of your results. If the on-device model isn’t available, an algorithmic summary is used instead — so you always get a readable interpretation of the scan. ", + "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#local-mesh-discovery-scanner", - "relUrl": "/sq-rAL/user/discovery.html#local-mesh-discovery-scanner" + "relUrl": "/es-rES/user/discovery.html#local-mesh-discovery-scanner" },"1630": { "doc": "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 devices can hear even before they share a configuration. Configure it under Settings → Module Config → Mesh Beacon: . | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast beacon — send your own invitation at a set interval, with an optional message and an offered channel. | . 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 radio 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. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#mesh-beacon", + "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#mesh-beacon", - "relUrl": "/sq-rAL/user/discovery.html#mesh-beacon" + "relUrl": "/es-rES/user/discovery.html#mesh-beacon" },"1631": { "doc": "Discovery", "title": "Manual Exploration", "content": "The tools below 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. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#manual-exploration", + "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#manual-exploration", - "relUrl": "/sq-rAL/user/discovery.html#manual-exploration" + "relUrl": "/es-rES/user/discovery.html#manual-exploration" },"1632": { "doc": "Discovery", "title": "Traceroute", "content": "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, tap Traceroute. | The app sends a traceroute request and waits for the response. | Results display each hop in order, with signal quality at every step. | . Reading the Results . A traceroute result looks like this: . You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target . Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment. | What to look for | What it means | . | All hops show Good SNR (≥ −7 dB, green) | Healthy path — messages flow reliably | . | One hop shows Bad SNR (< −15 dB, 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 route found” — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa Config. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric. | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#traceroute", + "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#traceroute", - "relUrl": "/sq-rAL/user/discovery.html#traceroute" + "relUrl": "/es-rES/user/discovery.html#traceroute" },"1633": { "doc": "Discovery", - "title": "Neighbor Info", + "title": "Información de Vecinos", "content": "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 Config → Neighbor Info. | Enable the module. | Set the broadcast interval (default: 900 seconds / 15 minutes). | . Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same. Viewing Neighbor Data . | Open any node’s detail screen and look for the Neighbors section. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ⚠️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#neighbor-info", + "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#informaci%C3%B3n-de-vecinos", - "relUrl": "/sq-rAL/user/discovery.html#neighbor-info" + "relUrl": "/es-rES/user/discovery.html#información-de-vecinos" },"1634": { "doc": "Discovery", "title": "Node List as a Discovery Tool", "content": "The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding New Nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on devices. | . Assessing Connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over radio (not via internet bridge). | . Infrastructure Audit . | Disable Exclude infrastructure to see Router, 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#node-list-as-a-discovery-tool", + "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#node-list-as-a-discovery-tool", - "relUrl": "/sq-rAL/user/discovery.html#node-list-as-a-discovery-tool" + "relUrl": "/es-rES/user/discovery.html#node-list-as-a-discovery-tool" },"1635": { "doc": "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", + "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#tips-for-mesh-exploration", - "relUrl": "/sq-rAL/user/discovery.html#tips-for-mesh-exploration" + "relUrl": "/es-rES/user/discovery.html#tips-for-mesh-exploration" },"1636": { - "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" - },"1637": { - "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 devices. | 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" - },"1638": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1639": { - "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" - },"1640": { - "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 | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#pre-update-checklist", - - "relUrl": "/is-rIS/user/firmware.html#pre-update-checklist" - },"1641": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1642": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#troubleshooting", - - "relUrl": "/is-rIS/user/firmware.html#troubleshooting" - },"1643": { - "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" - },"1644": { - "doc": "ファームウェア更新", - "title": "ファームウェア更新", - "content": "新機能、バグ修正、セキュリティ改善のために、Meshtastic 無線機を最新のファームウェアに保ちましょう。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html", - - "relUrl": "/ja-rJP/user/firmware.html" - },"1645": { - "doc": "ファームウェア更新", - "title": "更新を確認する", - "content": ". | 接続中の無線機の設定を開き、「詳細設定」で「ファームウェア更新」をタップします。 この項目は、OTA に対応したデバイスでのみ表示されます。 | アプリが、利用可能なファームウェアバージョンを確認します。 | 利用可能な更新には、バージョン番号と変更履歴の概要が表示されます。 | . ", - "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#更新を確認する" - },"1646": { - "doc": "ファームウェア更新", - "title": "更新方法", - "content": "Bluetooth 経由の OTA（無線更新） . Android ユーザーにとって最も一般的な更新方法です： . | 無線機が Bluetooth で接続されていることを確認します。 | ファームウェア更新画面に移動します。 | 希望するファームウェアバージョンを選択します。 | 「更新」をタップして OTA 処理を開始します。 | 更新が完了するまで待ちます。更新中は接続を切断しないでください。 | . ⚠️ 警告： ファームウェア更新を中断すると、デバイスが起動不能になることがあります。 無線機のバッテリーが十分にある（50% 以上を推奨）ことを確認し、処理の間ずっと Bluetooth の通信範囲内に置いてください。 . アプリ内での USB 更新 . 無線機が（Bluetooth ではなく）USB／シリアルで接続されている場合、ファームウェア更新画面に「USB ファイル転送」が表示されます。 アプリはデバイスを DFU モードで再起動し、システムのファイル選択画面を使って .uf2 ファイルをデバイスの DFU ドライブに保存するよう促します。 このオプションは USB／シリアル接続でのみ表示され、Bluetooth では利用できません。 . ℹ️ nRF ブートローダーに関する注意： 一部のデバイス（例：RAK WisBlock RAK4631）では、ベンダーのシリアル DFU ツール（adafruit-nrfutil など）でブートローダーを書き込む必要があります。.uf2 をコピーするだけではブートローダーは更新されません。 これに該当する場合、アプリがヒントを表示します。 . その他の書き込み方法 . 復旧時、または 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#更新方法" - },"1647": { - "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#バージョンチャンネル" - },"1648": { - "doc": "ファームウェア更新", - "title": "更新前のチェックリスト", - "content": "更新する前に： . | バッテリー 50% 以上 | 安定した Bluetooth 接続 | 現在の設定を控えておく（メジャーバージョンの変更時にリセットされることがあります） | 破壊的変更がないか、リリースノートを確認する | . ", - "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#更新前のチェックリスト" - },"1649": { - "doc": "ファームウェア更新", - "title": "更新後", - "content": "ファームウェアの書き込み後、アプリは更新を検証し、デバイスが再びオンラインになるのを待ちます： . 更新が成功すると： . | 無線機が自動的に再起動します | Bluetooth 接続が再確立されます | 設定が保持されているか確認します | ファームウェア更新画面の「現在インストール済み」で新しいバージョンを確認します。バージョンは、ノードの詳細ページや接続画面にも表示されます | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html#%E6%9B%B4%E6%96%B0%E5%BE%8C", - - "relUrl": "/ja-rJP/user/firmware.html#更新後" - },"1650": { - "doc": "ファームウェア更新", - "title": "トラブルシューティング", - "content": "更新が止まる . 更新が固まったように見える場合： . | 手を加える前に、少なくとも 5 分待つ | 本当に止まっている場合は、無線機の電源を入れ直す | もう一度更新を試みる | . 更新後にデバイスが起動しない . デバイスが起動しない場合： . | USB でコンピューターに接続してみる | リカバリー／DFU モードで Web Flasher を使用する | 動作確認済みのファームウェアバージョンを書き込む | デバイス固有の復旧手順については、Meshtastic の Discord を確認する | . 互換性の警告 . 次の場合、アプリが警告を表示することがあります： . | 接続中の無線機のファームウェアが、対応する最小バージョンを下回っている | アプリとファームウェアの間でメジャーバージョンが一致していない | 非推奨の機能に移行が必要 | . ⚠️ 重要： 互換性を確保するため、ファームウェア更新の前、または同時に、必ず Meshtastic アプリを更新してください。 . ", - "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#トラブルシューティング" - },"1651": { - "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#関連トピック" - },"1652": { - "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" - },"1653": { - "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 devices. | 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" - },"1654": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1655": { - "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" - },"1656": { - "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 | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#pre-update-checklist", - - "relUrl": "/ca-rES/user/firmware.html#pre-update-checklist" - },"1657": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1658": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#troubleshooting", - - "relUrl": "/ca-rES/user/firmware.html#troubleshooting" - },"1659": { - "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" - },"1660": { - "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" - },"1661": { - "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 devices. | 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" - },"1662": { - "doc": "Ажурирања фирмвера", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1663": { - "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" - },"1664": { - "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 | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html#pre-update-checklist", - - "relUrl": "/sr-rLatn/user/firmware.html#pre-update-checklist" - },"1665": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1666": { - "doc": "Ажурирања фирмвера", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html#troubleshooting", - - "relUrl": "/sr-rLatn/user/firmware.html#troubleshooting" - },"1667": { - "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" - },"1668": { - "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" - },"1669": { - "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 devices. | 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" - },"1670": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1671": { - "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" - },"1672": { - "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 | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html#pre-update-checklist", - - "relUrl": "/ko-rKR/user/firmware.html#pre-update-checklist" - },"1673": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1674": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html#troubleshooting", - - "relUrl": "/ko-rKR/user/firmware.html#troubleshooting" - },"1675": { - "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" - },"1676": { - "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" - },"1677": { - "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 devices. | 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" - },"1678": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1679": { - "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" - },"1680": { - "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 | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#pre-update-checklist", - - "relUrl": "/ro-rRO/user/firmware.html#pre-update-checklist" - },"1681": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1682": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#troubleshooting", - - "relUrl": "/ro-rRO/user/firmware.html#troubleshooting" - },"1683": { - "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" - },"1684": { - "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" - },"1685": { - "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 devices. | 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" - },"1686": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1687": { - "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" - },"1688": { - "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 | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#pre-update-checklist", - - "relUrl": "/ga-rIE/user/firmware.html#pre-update-checklist" - },"1689": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1690": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#troubleshooting", - - "relUrl": "/ga-rIE/user/firmware.html#troubleshooting" - },"1691": { - "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" - },"1692": { - "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" - },"1693": { - "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 devices. | 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" - },"1694": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1695": { - "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" - },"1696": { - "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 | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html#pre-update-checklist", - - "relUrl": "/iw-rIL/user/firmware.html#pre-update-checklist" - },"1697": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1698": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html#troubleshooting", - - "relUrl": "/iw-rIL/user/firmware.html#troubleshooting" - },"1699": { - "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" - },"1700": { - "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" - },"1701": { - "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 devices. | 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" - },"1702": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1703": { - "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" - },"1704": { - "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 | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html#pre-update-checklist", - - "relUrl": "/sv-rSE/user/firmware.html#pre-update-checklist" - },"1705": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1706": { - "doc": "Firmware Updates", - "title": "Felsökning", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html#fels%C3%B6kning", - - "relUrl": "/sv-rSE/user/firmware.html#felsökning" - },"1707": { - "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" - },"1708": { - "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" - },"1709": { - "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 devices. | 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" - },"1710": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1711": { - "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" - },"1712": { - "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 | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#pre-update-checklist", - - "relUrl": "/ht-rHT/user/firmware.html#pre-update-checklist" - },"1713": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1714": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#troubleshooting", - - "relUrl": "/ht-rHT/user/firmware.html#troubleshooting" - },"1715": { - "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" - },"1716": { - "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" - },"1717": { - "doc": "Laiteohjelmiston päivitykset", - "title": "Päivitysten tarkistaminen", - "content": ". | Avaa yhdistetyn radion asetukset ja valitse Lisäasetukset → Laiteohjelmiston päivitys. Tämä vaihtoehto näkyy vain laitteilla, jotka tukevat OTA-päivityksiä. | 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" - },"1718": { - "doc": "Laiteohjelmiston päivitykset", - "title": "Päivitysmenetelmät", - "content": "OTA (Over-The-Air) Bluetooth-yhteyden kautta . Yleisin päivitystapa Android-käyttäjille: . | Varmista, että radiosi on yhdistetty Bluetoothilla. | Siirry Firmware-päivitys -näkymään. | Valitse haluamasi firmware-versio. | Napauta Päivitä aloittaaksesi OTA-päivityksen. | Odota, että päivitys valmistuu — älä katkaise yhteyttä päivityksen aikana. | . ⚠️ Varoitus: firmware-päivityksen keskeyttäminen voi rikkoa laitteen. Varmista, että radiossa on riittävästi akkua (>50 % suositus) ja pidä Bluetooth-yhteys lähellä koko prosessin ajan. 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. ℹ️ nRF-käynnistyslatain: Jotkin laitteet (esimerkiksi RAK WisBlock RAK4631) edellyttävät, että käynnistyslatain päivitetään valmistajan sarjamuotoisella DFU-työkalulla (kuten adafruit-nrfutil). Pelkän .uf2-tiedoston kopioiminen ei päivitä käynnistyslatainta. Sovellus näyttää tästä vihjeen, kun se on tarpeen. 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" - },"1719": { - "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" - },"1720": { - "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 | . ", - "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" - },"1721": { - "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 muodostuu 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" - },"1722": { - "doc": "Laiteohjelmiston päivitykset", - "title": "Vianetsintä", - "content": "Päivitys jumissa . Jos päivitys näyttää jumiutuneen: . | Odota vähintään 5 minuuttia ennen toimenpiteitä | Jos laite on edelleen jumissa, käynnistä radio uudelleen virrankatkaisulla | Yritä päivitystä uudelleen | . Laite ei käynnisty päivityksen jälkeen . Jos laite ei käynnisty: . | 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 . Sovellus voi näyttää varoituksia, kun: . | Yhdistetyn radion laiteohjelmisto on alle tuetun vähimmäisversion | Sovelluksen ja laiteohjelmiston version välillä on ristiriita | Vanhentuneet ominaisuudet vaativat siirtymistä uuteen versioon | . ⚠️ Tärkeää: Päivitä Meshtastic-sovellus aina ennen firmware-päivitystä tai sen yhteydessä varmistaaksesi yhteensopivuuden. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/firmware.html#vianetsint%C3%A4", - - "relUrl": "/fi-rFI/user/firmware.html#vianetsintä" - },"1723": { - "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" - },"1724": { - "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" - },"1725": { - "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 devices. | 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" - },"1726": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1727": { - "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" - },"1728": { - "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 | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#pre-update-checklist", - - "relUrl": "/gl-rES/user/firmware.html#pre-update-checklist" - },"1729": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1730": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#troubleshooting", - - "relUrl": "/gl-rES/user/firmware.html#troubleshooting" - },"1731": { - "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" - },"1732": { - "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" - },"1733": { - "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 devices. | 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" - },"1734": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1735": { - "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" - },"1736": { - "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 | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html#pre-update-checklist", - - "relUrl": "/uk-rUA/user/firmware.html#pre-update-checklist" - },"1737": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1738": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html#troubleshooting", - - "relUrl": "/uk-rUA/user/firmware.html#troubleshooting" - },"1739": { - "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" - },"1740": { "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" - },"1741": { + },"1637": { "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 devices. | 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" - },"1742": { + },"1638": { "doc": "Firmwareaktualisierungen", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1743": { + },"1639": { "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" - },"1744": { + },"1640": { "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 | . ", "url": "/Meshtastic-Android/main/de-rDE/user/firmware.html#pre-update-checklist", "relUrl": "/de-rDE/user/firmware.html#pre-update-checklist" - },"1745": { + },"1641": { "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1746": { + },"1642": { "doc": "Firmwareaktualisierungen", "title": "Fehlerbehebung", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", "url": "/Meshtastic-Android/main/de-rDE/user/firmware.html#fehlerbehebung", "relUrl": "/de-rDE/user/firmware.html#fehlerbehebung" - },"1747": { + },"1643": { "doc": "Firmwareaktualisierungen", "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/de-rDE/user/firmware.html#related-topics", "relUrl": "/de-rDE/user/firmware.html#related-topics" - },"1748": { + },"1644": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html", - "relUrl": "/hr-rHR/user/firmware.html" - },"1749": { + "relUrl": "/ca-rES/user/firmware.html" + },"1645": { "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 devices. | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#checking-for-updates", - "relUrl": "/hr-rHR/user/firmware.html#checking-for-updates" - },"1750": { + "relUrl": "/ca-rES/user/firmware.html#checking-for-updates" + },"1646": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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", + "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#update-methods", - "relUrl": "/hr-rHR/user/firmware.html#update-methods" - },"1751": { + "relUrl": "/ca-rES/user/firmware.html#update-methods" + },"1647": { "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", + "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": "/hr-rHR/user/firmware.html#version-channels" - },"1752": { + "relUrl": "/ca-rES/user/firmware.html#version-channels" + },"1648": { "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 | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html#pre-update-checklist", + "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#pre-update-checklist", - "relUrl": "/hr-rHR/user/firmware.html#pre-update-checklist" - },"1753": { + "relUrl": "/ca-rES/user/firmware.html#pre-update-checklist" + },"1649": { "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 will reboot automatically | Bluetooth connection will re-establish | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#post-update", - "relUrl": "/hr-rHR/user/firmware.html#post-update" - },"1754": { + "relUrl": "/ca-rES/user/firmware.html#post-update" + },"1650": { "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html#troubleshooting", + "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#troubleshooting", - "relUrl": "/hr-rHR/user/firmware.html#troubleshooting" - },"1755": { + "relUrl": "/ca-rES/user/firmware.html#troubleshooting" + },"1651": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#related-topics", - "relUrl": "/hr-rHR/user/firmware.html#related-topics" - },"1756": { - "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" - },"1757": { - "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 devices. | 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" - },"1758": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1759": { - "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" - },"1760": { - "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 | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html#pre-update-checklist", - - "relUrl": "/lt-rLT/user/firmware.html#pre-update-checklist" - },"1761": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1762": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html#troubleshooting", - - "relUrl": "/lt-rLT/user/firmware.html#troubleshooting" - },"1763": { - "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" - },"1764": { - "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" - },"1765": { - "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 devices. | 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" - },"1766": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1767": { - "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" - },"1768": { - "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 | . ", - "url": "/Meshtastic-Android/main/en/user/firmware.html#pre-update-checklist", - - "relUrl": "/en/user/firmware.html#pre-update-checklist" - },"1769": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1770": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/en/user/firmware.html#troubleshooting", - - "relUrl": "/en/user/firmware.html#troubleshooting" - },"1771": { - "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" - },"1772": { - "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" - },"1773": { - "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 devices. | 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" - },"1774": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1775": { - "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" - },"1776": { - "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 | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#pre-update-checklist", - - "relUrl": "/hu-rHU/user/firmware.html#pre-update-checklist" - },"1777": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1778": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#troubleshooting", - - "relUrl": "/hu-rHU/user/firmware.html#troubleshooting" - },"1779": { - "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" - },"1780": { - "doc": "Актуализации на фърмуера", - "title": "Актуализации на фърмуера", - "content": "Поддържайте вашето Meshtastic радио актуално с най-новия фърмуер за нови функции, корекции на грешки и подобрения в сигурността. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/firmware.html", - - "relUrl": "/bg-rBG/user/firmware.html" - },"1781": { - "doc": "Актуализации на фърмуера", - "title": "Проверка за актуализации", - "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable devices. | Приложението проверява за налични версии на фърмуера. | 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#проверка-за-актуализации" - },"1782": { - "doc": "Актуализации на фърмуера", - "title": "Методи за актуализиране", - "content": "OTA (Over-The-Air) чрез Bluetooth . Най-често срещаният метод за актуализиране за потребителите на Android: . | Уверете се, че радиото ви е свързано чрез Bluetooth. | Отидете до екрана за актуализация на фърмуера. | Изберете желаната версия на фърмуера. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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#методи-за-актуализиране" - },"1783": { - "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#канали-на-версиите" - },"1784": { - "doc": "Актуализации на фърмуера", - "title": "Контролен списък преди актуализация", - "content": "Преди актуализиране: . | Батерия > 50% | Стабилна Bluetooth връзка | Запишете текущите си настройки (те могат да се нулират при големи промени във версията) | Проверете бележките към изданието за важни промени | . ", - "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#контролен-списък-преди-актуализация" - },"1785": { - "doc": "Актуализации на фърмуера", - "title": "След актуализация", - "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . След като актуализацията е успешна: . | Радиото ще се рестартира автоматично | Bluetooth връзката ще се възстанови | Проверете дали настройките ви са непокътнати | 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#след-актуализация" - },"1786": { - "doc": "Актуализации на фърмуера", - "title": "Отстраняване на неизправности", - "content": "Update Stuck . If the update appears frozen: . | Изчакайте поне 5 минути, преди да се намесите | If truly stuck, power-cycle the radio | Опитайте актуализацията отново | . Устройството не се стартира след актуализация . If your device 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 | . Предупреждения за съвместимост . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "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#отстраняване-на-неизправности" - },"1787": { - "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#свързани-теми" - },"1788": { - "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" - },"1789": { - "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 devices. | 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" - },"1790": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1791": { - "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" - },"1792": { - "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 | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html#pre-update-checklist", - - "relUrl": "/sl-rSI/user/firmware.html#pre-update-checklist" - },"1793": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1794": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html#troubleshooting", - - "relUrl": "/sl-rSI/user/firmware.html#troubleshooting" - },"1795": { - "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" - },"1796": { - "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" - },"1797": { - "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 devices. | 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" - },"1798": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1799": { - "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" - },"1800": { - "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 | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html#pre-update-checklist", - - "relUrl": "/pt-rPT/user/firmware.html#pre-update-checklist" - },"1801": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1802": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html#troubleshooting", - - "relUrl": "/pt-rPT/user/firmware.html#troubleshooting" - },"1803": { - "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" - },"1804": { + "relUrl": "/ca-rES/user/firmware.html#related-topics" + },"1652": { "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" - },"1805": { + },"1653": { "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 devices. | 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" - },"1806": { + },"1654": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1807": { + },"1655": { "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" - },"1808": { + },"1656": { "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 | . ", "url": "/Meshtastic-Android/main/be-rBY/user/firmware.html#pre-update-checklist", "relUrl": "/be-rBY/user/firmware.html#pre-update-checklist" - },"1809": { + },"1657": { "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1810": { + },"1658": { "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", "url": "/Meshtastic-Android/main/be-rBY/user/firmware.html#troubleshooting", "relUrl": "/be-rBY/user/firmware.html#troubleshooting" - },"1811": { + },"1659": { "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" - },"1812": { + },"1660": { + "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" + },"1661": { + "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 devices. | 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" + },"1662": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1663": { + "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" + },"1664": { + "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 | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html#pre-update-checklist", + + "relUrl": "/uk-rUA/user/firmware.html#pre-update-checklist" + },"1665": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1666": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html#troubleshooting", + + "relUrl": "/uk-rUA/user/firmware.html#troubleshooting" + },"1667": { + "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" + },"1668": { + "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" + },"1669": { + "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 devices. | 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" + },"1670": { + "doc": "固件升级", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1671": { + "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" + },"1672": { + "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 | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/firmware.html#pre-update-checklist", + + "relUrl": "/zh-rCN/user/firmware.html#pre-update-checklist" + },"1673": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1674": { + "doc": "固件升级", + "title": "问题排查", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "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#问题排查" + },"1675": { + "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" + },"1676": { + "doc": "Актуализации на фърмуера", + "title": "Актуализации на фърмуера", + "content": "Поддържайте вашето Meshtastic радио актуално с най-новия фърмуер за нови функции, корекции на грешки и подобрения в сигурността. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/firmware.html", + + "relUrl": "/bg-rBG/user/firmware.html" + },"1677": { + "doc": "Актуализации на фърмуера", + "title": "Проверка за актуализации", + "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable devices. | Приложението проверява за налични версии на фърмуера. | 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#проверка-за-актуализации" + },"1678": { + "doc": "Актуализации на фърмуера", + "title": "Методи за актуализиране", + "content": "OTA (Over-The-Air) чрез Bluetooth . Най-често срещаният метод за актуализиране за потребителите на Android: . | Уверете се, че радиото ви е свързано чрез Bluetooth. | Отидете до екрана за актуализация на фърмуера. | Изберете желаната версия на фърмуера. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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#методи-за-актуализиране" + },"1679": { + "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#канали-на-версиите" + },"1680": { + "doc": "Актуализации на фърмуера", + "title": "Контролен списък преди актуализация", + "content": "Преди актуализиране: . | Батерия > 50% | Стабилна Bluetooth връзка | Запишете текущите си настройки (те могат да се нулират при големи промени във версията) | Проверете бележките към изданието за важни промени | . ", + "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#контролен-списък-преди-актуализация" + },"1681": { + "doc": "Актуализации на фърмуера", + "title": "След актуализация", + "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . След като актуализацията е успешна: . | Радиото ще се рестартира автоматично | Bluetooth връзката ще се възстанови | Проверете дали настройките ви са непокътнати | 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#след-актуализация" + },"1682": { + "doc": "Актуализации на фърмуера", + "title": "Отстраняване на неизправности", + "content": "Update Stuck . If the update appears frozen: . | Изчакайте поне 5 минути, преди да се намесите | If truly stuck, power-cycle the radio | Опитайте актуализацията отново | . Устройството не се стартира след актуализация . If your device 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 | . Предупреждения за съвместимост . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "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#отстраняване-на-неизправности" + },"1683": { + "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#свързани-теми" + },"1684": { + "doc": "韌體更新", + "title": "韌體更新", + "content": "保持 Meshtastic 無線電裝置的韌體為最新版本，以取得新功能、錯誤修正與安全性改善。 . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html", + + "relUrl": "/zh-rTW/user/firmware.html" + },"1685": { + "doc": "韌體更新", + "title": "檢查更新", + "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable devices. | 應用程式將檢查可用的韌體版本。 | 如有可用更新將顯示版本號碼與更新記錄摘要。 | . ", + "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#檢查更新" + },"1686": { + "doc": "韌體更新", + "title": "更新方式", + "content": "OTA（無線空中下載）透過藍牙 . Android 使用者最常用的更新方式： . | 請確認您的無線電裝置已透過藍牙連線。 | 前往韌體更新畫面。 | 選取所需的韌體版本。 | 點選「更新」以開始 OTA 流程。 | 請等待更新完成 — 更新期間請勿中斷連線。 | . ⚠️ 警告：中斷韌體更新可能導致裝置變磚。 請確認無線電裝置電量充足（建議 50% 以上），並在整個更新過程中保持藍牙通訊距離。 . 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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#更新方式" + },"1687": { + "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#版本頻道" + },"1688": { + "doc": "韌體更新", + "title": "更新前檢查清單", + "content": "更新前請確認： . | 電量 > 50% | 藍牙連線穩定 | 記錄目前的設定（主要版本更新時可能會重設） | 查看版本說明中是否有重大變更 | . ", + "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#更新前檢查清單" + },"1689": { + "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: . | 無線電裝置將自動重新開機 | 藍牙連線將自動重新建立 | 確認您的設定完整無缺 | 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#更新後" + },"1690": { + "doc": "韌體更新", + "title": "故障排除", + "content": "更新卡住 . 若更新似乎停滯不動： . | 請至少等待 5 分鐘再採取行動 | 若確實卡住，請將無線電裝置重新開關機 | 再次嘗試更新 | . 更新後裝置無法開機 . 若您的裝置無法開機： . | 請嘗試透過 USB 連接至電腦 | 在復原／DFU 模式下使用網頁燒錄工具 | 燒錄已知可正常運作的韌體版本 | 前往 Meshtastic Discord 查詢特定裝置的復原步驟 | . 相容性警告 . 應用程式在以下情況可能顯示警告： . | 已連接的無線電裝置韌體低於最低支援版本 | 應用程式與韌體之間的主要版本不相符 | 已棄用的功能需要進行遷移 | . ⚠️ 重要：請在韌體更新之前或同時更新 Meshtastic 應用程式，以確保相容性。 . ", + "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#故障排除" + },"1691": { + "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#相關主題" + },"1692": { + "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" + },"1693": { + "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 devices. | 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" + },"1694": { + "doc": "Ажурирања фирмвера", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1695": { + "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" + },"1696": { + "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 | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html#pre-update-checklist", + + "relUrl": "/sr-rLatn/user/firmware.html#pre-update-checklist" + },"1697": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1698": { + "doc": "Ажурирања фирмвера", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html#troubleshooting", + + "relUrl": "/sr-rLatn/user/firmware.html#troubleshooting" + },"1699": { + "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" + },"1700": { + "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/cs-rCZ/user/firmware.html", + + "relUrl": "/cs-rCZ/user/firmware.html" + },"1701": { + "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 devices. | 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" + },"1702": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1703": { + "doc": "Firmware Updates", + "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" + },"1704": { + "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 | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html#pre-update-checklist", + + "relUrl": "/cs-rCZ/user/firmware.html#pre-update-checklist" + },"1705": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1706": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html#troubleshooting", + + "relUrl": "/cs-rCZ/user/firmware.html#troubleshooting" + },"1707": { + "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/cs-rCZ/user/firmware.html#related-topics", + + "relUrl": "/cs-rCZ/user/firmware.html#related-topics" + },"1708": { + "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" + },"1709": { + "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 devices. | 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" + },"1710": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1711": { + "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" + },"1712": { + "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 | . ", + "url": "/Meshtastic-Android/main/en/user/firmware.html#pre-update-checklist", + + "relUrl": "/en/user/firmware.html#pre-update-checklist" + },"1713": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1714": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/en/user/firmware.html#troubleshooting", + + "relUrl": "/en/user/firmware.html#troubleshooting" + },"1715": { + "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" + },"1716": { + "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" + },"1717": { + "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 devices. | 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" + },"1718": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1719": { + "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" + },"1720": { + "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 | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html#pre-update-checklist", + + "relUrl": "/sl-rSI/user/firmware.html#pre-update-checklist" + },"1721": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1722": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html#troubleshooting", + + "relUrl": "/sl-rSI/user/firmware.html#troubleshooting" + },"1723": { + "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" + },"1724": { + "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" + },"1725": { + "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 devices. | 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" + },"1726": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1727": { + "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" + },"1728": { + "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 | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html#pre-update-checklist", + + "relUrl": "/it-rIT/user/firmware.html#pre-update-checklist" + },"1729": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1730": { + "doc": "Firmware Updates", + "title": "Risoluzione problemi", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html#risoluzione-problemi", + + "relUrl": "/it-rIT/user/firmware.html#risoluzione-problemi" + },"1731": { + "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" + },"1732": { "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" - },"1813": { + },"1733": { "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 devices. | 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" - },"1814": { + },"1734": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1815": { + },"1735": { "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" - },"1816": { + },"1736": { "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 | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/firmware.html#pre-update-checklist", "relUrl": "/pt-rBR/user/firmware.html#pre-update-checklist" - },"1817": { + },"1737": { "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1818": { + },"1738": { "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", "url": "/Meshtastic-Android/main/pt-rBR/user/firmware.html#troubleshooting", "relUrl": "/pt-rBR/user/firmware.html#troubleshooting" - },"1819": { + },"1739": { "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" - },"1820": { + },"1740": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html", - "relUrl": "/el-rGR/user/firmware.html" - },"1821": { + "relUrl": "/is-rIS/user/firmware.html" + },"1741": { "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 devices. | 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", + "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#checking-for-updates", - "relUrl": "/el-rGR/user/firmware.html#checking-for-updates" - },"1822": { + "relUrl": "/is-rIS/user/firmware.html#checking-for-updates" + },"1742": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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", + "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#update-methods", - "relUrl": "/el-rGR/user/firmware.html#update-methods" - },"1823": { + "relUrl": "/is-rIS/user/firmware.html#update-methods" + },"1743": { "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", + "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": "/el-rGR/user/firmware.html#version-channels" - },"1824": { + "relUrl": "/is-rIS/user/firmware.html#version-channels" + },"1744": { "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 | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html#pre-update-checklist", + "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#pre-update-checklist", - "relUrl": "/el-rGR/user/firmware.html#pre-update-checklist" - },"1825": { + "relUrl": "/is-rIS/user/firmware.html#pre-update-checklist" + },"1745": { "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 will reboot automatically | Bluetooth connection will re-establish | 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", + "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#post-update", - "relUrl": "/el-rGR/user/firmware.html#post-update" - },"1826": { + "relUrl": "/is-rIS/user/firmware.html#post-update" + },"1746": { "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html#troubleshooting", + "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#troubleshooting", - "relUrl": "/el-rGR/user/firmware.html#troubleshooting" - },"1827": { + "relUrl": "/is-rIS/user/firmware.html#troubleshooting" + },"1747": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#related-topics", - "relUrl": "/el-rGR/user/firmware.html#related-topics" - },"1828": { + "relUrl": "/is-rIS/user/firmware.html#related-topics" + },"1748": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html", - "relUrl": "/es-rES/user/firmware.html" - },"1829": { + "relUrl": "/fr-rFR/user/firmware.html" + },"1749": { "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 devices. | 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#checking-for-updates", - "relUrl": "/es-rES/user/firmware.html#checking-for-updates" - },"1830": { + "relUrl": "/fr-rFR/user/firmware.html#checking-for-updates" + },"1750": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#update-methods", - "relUrl": "/es-rES/user/firmware.html#update-methods" - },"1831": { + "relUrl": "/fr-rFR/user/firmware.html#update-methods" + },"1751": { "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", + "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": "/es-rES/user/firmware.html#version-channels" - },"1832": { + "relUrl": "/fr-rFR/user/firmware.html#version-channels" + },"1752": { "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 | . ", - "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#pre-update-checklist", + "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#pre-update-checklist", - "relUrl": "/es-rES/user/firmware.html#pre-update-checklist" - },"1833": { + "relUrl": "/fr-rFR/user/firmware.html#pre-update-checklist" + },"1753": { "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 will reboot automatically | Bluetooth connection will re-establish | 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#post-update", - "relUrl": "/es-rES/user/firmware.html#post-update" - },"1834": { + "relUrl": "/fr-rFR/user/firmware.html#post-update" + },"1754": { "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#troubleshooting", + "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#troubleshooting", - "relUrl": "/es-rES/user/firmware.html#troubleshooting" - },"1835": { + "relUrl": "/fr-rFR/user/firmware.html#troubleshooting" + },"1755": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#related-topics", - "relUrl": "/es-rES/user/firmware.html#related-topics" - },"1836": { + "relUrl": "/fr-rFR/user/firmware.html#related-topics" + },"1756": { + "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" + },"1757": { + "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 devices. | 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" + },"1758": { + "doc": "Ажурирања фирмвера", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1759": { + "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" + },"1760": { + "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 | . ", + "url": "/Meshtastic-Android/main/srp/user/firmware.html#pre-update-checklist", + + "relUrl": "/srp/user/firmware.html#pre-update-checklist" + },"1761": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1762": { + "doc": "Ажурирања фирмвера", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/srp/user/firmware.html#troubleshooting", + + "relUrl": "/srp/user/firmware.html#troubleshooting" + },"1763": { + "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" + },"1764": { "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", + "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html", - "relUrl": "/tr-rTR/user/firmware.html" - },"1837": { + "relUrl": "/sk-rSK/user/firmware.html" + },"1765": { "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 devices. | 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", + "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#checking-for-updates", - "relUrl": "/tr-rTR/user/firmware.html#checking-for-updates" - },"1838": { + "relUrl": "/sk-rSK/user/firmware.html#checking-for-updates" + },"1766": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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", + "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#update-methods", - "relUrl": "/tr-rTR/user/firmware.html#update-methods" - },"1839": { + "relUrl": "/sk-rSK/user/firmware.html#update-methods" + },"1767": { "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", + "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": "/tr-rTR/user/firmware.html#version-channels" - },"1840": { + "relUrl": "/sk-rSK/user/firmware.html#version-channels" + },"1768": { "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 | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html#pre-update-checklist", + "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#pre-update-checklist", - "relUrl": "/tr-rTR/user/firmware.html#pre-update-checklist" - },"1841": { + "relUrl": "/sk-rSK/user/firmware.html#pre-update-checklist" + },"1769": { "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 will reboot automatically | Bluetooth connection will re-establish | 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", + "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#post-update", - "relUrl": "/tr-rTR/user/firmware.html#post-update" - },"1842": { + "relUrl": "/sk-rSK/user/firmware.html#post-update" + },"1770": { "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html#troubleshooting", + "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#troubleshooting", - "relUrl": "/tr-rTR/user/firmware.html#troubleshooting" - },"1843": { + "relUrl": "/sk-rSK/user/firmware.html#troubleshooting" + },"1771": { "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", + "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#related-topics", - "relUrl": "/tr-rTR/user/firmware.html#related-topics" - },"1844": { - "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": "/sk-rSK/user/firmware.html#related-topics" + },"1772": { + "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": "/no-rNO/user/firmware.html" - },"1845": { - "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 devices. | 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": "/fi-rFI/user/firmware.html" + },"1773": { + "doc": "Laiteohjelmiston päivitykset", + "title": "Päivitysten tarkistaminen", + "content": ". | Avaa yhdistetyn radion asetukset ja valitse Lisäasetukset → Laiteohjelmiston päivitys. Tämä vaihtoehto näkyy vain laitteilla, jotka tukevat OTA-päivityksiä. | 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": "/no-rNO/user/firmware.html#checking-for-updates" - },"1846": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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": "/fi-rFI/user/firmware.html#päivitysten-tarkistaminen" + },"1774": { + "doc": "Laiteohjelmiston päivitykset", + "title": "Päivitysmenetelmät", + "content": "OTA (Over-The-Air) Bluetooth-yhteyden kautta . Yleisin päivitystapa Android-käyttäjille: . | Varmista, että radiosi on yhdistetty Bluetoothilla. | Siirry Firmware-päivitys -näkymään. | Valitse haluamasi firmware-versio. | Napauta Päivitä aloittaaksesi OTA-päivityksen. | Odota, että päivitys valmistuu — älä katkaise yhteyttä päivityksen aikana. | . ⚠️ Varoitus: firmware-päivityksen keskeyttäminen voi rikkoa laitteen. Varmista, että radiossa on riittävästi akkua (>50 % suositus) ja pidä Bluetooth-yhteys lähellä koko prosessin ajan. 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. ℹ️ nRF-käynnistyslatain: Jotkin laitteet (esimerkiksi RAK WisBlock RAK4631) edellyttävät, että käynnistyslatain päivitetään valmistajan sarjamuotoisella DFU-työkalulla (kuten adafruit-nrfutil). Pelkän .uf2-tiedoston kopioiminen ei päivitä käynnistyslatainta. Sovellus näyttää tästä vihjeen, kun se on tarpeen. 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": "/no-rNO/user/firmware.html#update-methods" - },"1847": { - "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": "/fi-rFI/user/firmware.html#päivitysmenetelmät" + },"1775": { + "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": "/no-rNO/user/firmware.html#version-channels" - },"1848": { - "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 | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html#pre-update-checklist", + "relUrl": "/fi-rFI/user/firmware.html#versiokanavat" + },"1776": { + "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 | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/firmware.html#p%C3%A4ivityst%C3%A4-edelt%C3%A4v%C3%A4-tarkistuslista", - "relUrl": "/no-rNO/user/firmware.html#pre-update-checklist" - },"1849": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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": "/fi-rFI/user/firmware.html#päivitystä-edeltävä-tarkistuslista" + },"1777": { + "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 muodostuu 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": "/no-rNO/user/firmware.html#post-update" - },"1850": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html#troubleshooting", + "relUrl": "/fi-rFI/user/firmware.html#päivityksen-jälkeen" + },"1778": { + "doc": "Laiteohjelmiston päivitykset", + "title": "Vianetsintä", + "content": "Päivitys jumissa . Jos päivitys näyttää jumiutuneen: . | Odota vähintään 5 minuuttia ennen toimenpiteitä | Jos laite on edelleen jumissa, käynnistä radio uudelleen virrankatkaisulla | Yritä päivitystä uudelleen | . Laite ei käynnisty päivityksen jälkeen . Jos laite ei käynnisty: . | 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 . Sovellus voi näyttää varoituksia, kun: . | Yhdistetyn radion laiteohjelmisto on alle tuetun vähimmäisversion | Sovelluksen ja laiteohjelmiston version välillä on ristiriita | Vanhentuneet ominaisuudet vaativat siirtymistä uuteen versioon | . ⚠️ Tärkeää: Päivitä Meshtastic-sovellus aina ennen firmware-päivitystä tai sen yhteydessä varmistaaksesi yhteensopivuuden. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/firmware.html#vianetsint%C3%A4", - "relUrl": "/no-rNO/user/firmware.html#troubleshooting" - },"1851": { - "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": "/fi-rFI/user/firmware.html#vianetsintä" + },"1779": { + "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": "/no-rNO/user/firmware.html#related-topics" - },"1852": { + "relUrl": "/fi-rFI/user/firmware.html#aiheeseen-liittyvät-aiheet" + },"1780": { "doc": "Обновления прошивки", "title": "Обновления прошивки", "content": "Поддерживайте своё радио Meshtastic в актуальном состоянии с помощью последней прошивки для получения новых функций, исправлений ошибок и улучшений безопасности. ", "url": "/Meshtastic-Android/main/ru-rRU/user/firmware.html", "relUrl": "/ru-rRU/user/firmware.html" - },"1853": { + },"1781": { "doc": "Обновления прошивки", "title": "Проверка обновлений", "content": ". | Откройте конфигурацию подключённого радио и в разделе “Дополнительно” нажмите “Обновление прошивки”. Этот пункт появляется только для устройств, поддерживающих OTA. | Приложение проверяет доступные версии прошивки. | Доступные обновления показывают номер версии и сводку изменений. | . ", "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#проверка-обновлений" - },"1854": { + },"1782": { "doc": "Обновления прошивки", "title": "Методы обновления", "content": "OTA (беспроводное обновление) через Bluetooth . Наиболее распространённый способ обновления для пользователей Android: . | Убедитесь, что твоё радио подключено по Bluetooth. | Перейдите на экран “Обновление прошивки”. | Выберите нужную версию прошивки. | Нажмите “Обновить”, чтобы начать процесс OTA. | Дождитесь завершения обновления — не отключайте устройство во время обновления. | . ⚠️ Предупреждение: Прерывание обновления прошивки может вывести твоё устройство из строя. Убедись, что твоё радио имеет достаточный заряд батареи (рекомендуется >50%) и сохраняйте близость Bluetooth на протяжении всего процесса. Обновление внутри приложения по USB . Когда твоё радио подключено по USB/serial (а не по Bluetooth), на экране обновления прошивки появляется опция “Передача файла по USB”. Приложение перезагружает устройство в режим DFU, а затем предлагает сохранить файл .uf2 на DFU-диск устройства с помощью системного выбора файлов. Эта опция появляется только при подключении по USB/serial — она недоступна по Bluetooth. ℹ️ Примечание о загрузчике nRF: Некоторым устройствам (например, RAK WisBlock RAK4631) требуется прошить загрузчик с помощью фирменной последовательной утилиты DFU (такой как adafruit-nrfutil) — простое копирование .uf2 не обновит загрузчик. Приложение покажет подсказку, когда это необходимо. Другие способы прошивки . Для восстановления или когда ни 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#методы-обновления" - },"1855": { + },"1783": { "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#каналы-версий" - },"1856": { + },"1784": { "doc": "Обновления прошивки", "title": "Предполётная проверка", "content": "Перед обновлением: . | Заряд батареи > 50% | Стабильное соединение Bluetooth | Запишите свои текущие настройки (они могут сброситься при смене мажорной версии) | Проверьте примечания к релизу на наличие критических изменений | . ", "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#предполётная-проверка" - },"1857": { + },"1785": { "doc": "Обновления прошивки", "title": "После обновления", "content": "После записи прошивки приложение проверяет обновление и ждёт, пока устройство снова станет доступным: . После успешного обновления: . | Радио перезагрузится автоматически | Соединение Bluetooth восстановится | Убедись, что твои настройки сохранились | Проверьте новую версию в разделе “Установленная версия” на экране обновления прошивки — она также отображается на странице сведений о ноде и на экране “Подключения” | . ", "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#после-обновления" - },"1858": { + },"1786": { "doc": "Обновления прошивки", "title": "Устранение неполадок", "content": "Обновление зависло . Если обновление кажется зависшим: . | Подождите не менее 5 минут, прежде чем предпринимать действия | Если действительно зависло, перезагрузите радио выключением и включением питания | Попробуйте обновление снова | . Устройство не загружается после обновления . Если твоё устройство не загружается: . | Попробуйте подключиться по USB к компьютеру | Используйте Web Flasher в режиме восстановления/DFU | Прошивайте заведомо рабочую версию прошивки | Обратитесь к Discord-серверу Meshtastic для получения инструкций по восстановлению, специфичных для твоего устройства | . Предупреждения о совместимости . Приложение может показывать предупреждения, когда: . | Прошивка подключённого радио ниже минимально поддерживаемой версии | Несовпадение мажорных версий приложения и прошивки | Устаревшие функции требуют миграции | . ⚠️ Важно: Всегда обновляйте приложение Meshtastic до или одновременно с обновлением прошивки, чтобы обеспечить совместимость. ", "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#устранение-неполадок" - },"1859": { + },"1787": { "doc": "Обновления прошивки", "title": "Связанные темы", "content": ". | Подключения — восстановление соединения после обновления прошивки | Руководство по прошивке— полное пошаговое руководство по полной прошивке на meshtastic.org | Поддерживаемые устройства — проверьте совместимость прошивки с устройством | Часто задаваемые вопросы — распространённые вопросы на 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#связанные-темы" + },"1788": { + "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" + },"1789": { + "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 devices. | 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" + },"1790": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1791": { + "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" + },"1792": { + "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 | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html#pre-update-checklist", + + "relUrl": "/ko-rKR/user/firmware.html#pre-update-checklist" + },"1793": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1794": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html#troubleshooting", + + "relUrl": "/ko-rKR/user/firmware.html#troubleshooting" + },"1795": { + "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" + },"1796": { + "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" + },"1797": { + "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 devices. | 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" + },"1798": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1799": { + "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" + },"1800": { + "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 | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html#pre-update-checklist", + + "relUrl": "/hr-rHR/user/firmware.html#pre-update-checklist" + },"1801": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1802": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html#troubleshooting", + + "relUrl": "/hr-rHR/user/firmware.html#troubleshooting" + },"1803": { + "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" + },"1804": { + "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" + },"1805": { + "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 devices. | 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" + },"1806": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1807": { + "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" + },"1808": { + "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 | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html#pre-update-checklist", + + "relUrl": "/sq-rAL/user/firmware.html#pre-update-checklist" + },"1809": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1810": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html#troubleshooting", + + "relUrl": "/sq-rAL/user/firmware.html#troubleshooting" + },"1811": { + "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" + },"1812": { + "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" + },"1813": { + "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 devices. | 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" + },"1814": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1815": { + "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" + },"1816": { + "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 | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html#pre-update-checklist", + + "relUrl": "/no-rNO/user/firmware.html#pre-update-checklist" + },"1817": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1818": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html#troubleshooting", + + "relUrl": "/no-rNO/user/firmware.html#troubleshooting" + },"1819": { + "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" + },"1820": { + "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" + },"1821": { + "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 devices. | 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" + },"1822": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1823": { + "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" + },"1824": { + "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 | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html#pre-update-checklist", + + "relUrl": "/lt-rLT/user/firmware.html#pre-update-checklist" + },"1825": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1826": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html#troubleshooting", + + "relUrl": "/lt-rLT/user/firmware.html#troubleshooting" + },"1827": { + "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" + },"1828": { + "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" + },"1829": { + "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 devices. | 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" + },"1830": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1831": { + "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" + },"1832": { + "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 | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html#pre-update-checklist", + + "relUrl": "/ar-rSA/user/firmware.html#pre-update-checklist" + },"1833": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1834": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html#troubleshooting", + + "relUrl": "/ar-rSA/user/firmware.html#troubleshooting" + },"1835": { + "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" + },"1836": { + "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" + },"1837": { + "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 devices. | 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" + },"1838": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1839": { + "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" + },"1840": { + "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 | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html#pre-update-checklist", + + "relUrl": "/pt-rPT/user/firmware.html#pre-update-checklist" + },"1841": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1842": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html#troubleshooting", + + "relUrl": "/pt-rPT/user/firmware.html#troubleshooting" + },"1843": { + "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" + },"1844": { + "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" + },"1845": { + "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 devices. | 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" + },"1846": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1847": { + "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" + },"1848": { + "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 | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html#pre-update-checklist", + + "relUrl": "/iw-rIL/user/firmware.html#pre-update-checklist" + },"1849": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1850": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html#troubleshooting", + + "relUrl": "/iw-rIL/user/firmware.html#troubleshooting" + },"1851": { + "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" + },"1852": { + "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" + },"1853": { + "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 devices. | 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" + },"1854": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1855": { + "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" + },"1856": { + "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 | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html#pre-update-checklist", + + "relUrl": "/el-rGR/user/firmware.html#pre-update-checklist" + },"1857": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1858": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html#troubleshooting", + + "relUrl": "/el-rGR/user/firmware.html#troubleshooting" + },"1859": { + "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" },"1860": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html", - "relUrl": "/nl-rNL/user/firmware.html" + "relUrl": "/ro-rRO/user/firmware.html" },"1861": { "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 devices. | 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#checking-for-updates", - "relUrl": "/nl-rNL/user/firmware.html#checking-for-updates" + "relUrl": "/ro-rRO/user/firmware.html#checking-for-updates" },"1862": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#update-methods", - "relUrl": "/nl-rNL/user/firmware.html#update-methods" + "relUrl": "/ro-rRO/user/firmware.html#update-methods" },"1863": { "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", + "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": "/nl-rNL/user/firmware.html#version-channels" + "relUrl": "/ro-rRO/user/firmware.html#version-channels" },"1864": { "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 | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html#pre-update-checklist", + "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#pre-update-checklist", - "relUrl": "/nl-rNL/user/firmware.html#pre-update-checklist" + "relUrl": "/ro-rRO/user/firmware.html#pre-update-checklist" },"1865": { "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 will reboot automatically | Bluetooth connection will re-establish | 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#post-update", - "relUrl": "/nl-rNL/user/firmware.html#post-update" + "relUrl": "/ro-rRO/user/firmware.html#post-update" },"1866": { "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html#troubleshooting", + "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#troubleshooting", - "relUrl": "/nl-rNL/user/firmware.html#troubleshooting" + "relUrl": "/ro-rRO/user/firmware.html#troubleshooting" },"1867": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#related-topics", - "relUrl": "/nl-rNL/user/firmware.html#related-topics" + "relUrl": "/ro-rRO/user/firmware.html#related-topics" },"1868": { "doc": "Püsivara värskendus", "title": "Püsivara värskendus", @@ -13134,2557 +13134,2557 @@ "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html", - "relUrl": "/it-rIT/user/firmware.html" + "relUrl": "/ga-rIE/user/firmware.html" },"1877": { "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 devices. | 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#checking-for-updates", - "relUrl": "/it-rIT/user/firmware.html#checking-for-updates" + "relUrl": "/ga-rIE/user/firmware.html#checking-for-updates" },"1878": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#update-methods", - "relUrl": "/it-rIT/user/firmware.html#update-methods" + "relUrl": "/ga-rIE/user/firmware.html#update-methods" },"1879": { "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", + "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": "/it-rIT/user/firmware.html#version-channels" + "relUrl": "/ga-rIE/user/firmware.html#version-channels" },"1880": { "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 | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html#pre-update-checklist", + "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#pre-update-checklist", - "relUrl": "/it-rIT/user/firmware.html#pre-update-checklist" + "relUrl": "/ga-rIE/user/firmware.html#pre-update-checklist" },"1881": { "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 will reboot automatically | Bluetooth connection will re-establish | 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#post-update", - "relUrl": "/it-rIT/user/firmware.html#post-update" + "relUrl": "/ga-rIE/user/firmware.html#post-update" },"1882": { "doc": "Firmware Updates", - "title": "Risoluzione problemi", + "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html#risoluzione-problemi", + "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#troubleshooting", - "relUrl": "/it-rIT/user/firmware.html#risoluzione-problemi" + "relUrl": "/ga-rIE/user/firmware.html#troubleshooting" },"1883": { "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#related-topics", - "relUrl": "/it-rIT/user/firmware.html#related-topics" + "relUrl": "/ga-rIE/user/firmware.html#related-topics" },"1884": { - "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" - },"1885": { - "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 devices. | 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" - },"1886": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1887": { - "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" - },"1888": { - "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 | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html#pre-update-checklist", - - "relUrl": "/ar-rSA/user/firmware.html#pre-update-checklist" - },"1889": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1890": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html#troubleshooting", - - "relUrl": "/ar-rSA/user/firmware.html#troubleshooting" - },"1891": { - "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" - },"1892": { - "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" - },"1893": { - "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 devices. | 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" - },"1894": { - "doc": "Firmware Updates", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1895": { - "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" - },"1896": { - "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 | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#pre-update-checklist", - - "relUrl": "/sk-rSK/user/firmware.html#pre-update-checklist" - },"1897": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1898": { - "doc": "Firmware Updates", - "title": "Troubleshooting", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#troubleshooting", - - "relUrl": "/sk-rSK/user/firmware.html#troubleshooting" - },"1899": { - "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" - },"1900": { "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" - },"1901": { + },"1885": { "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 devices. | 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" - },"1902": { + },"1886": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1903": { + },"1887": { "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" - },"1904": { + },"1888": { "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 | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/firmware.html#pre-update-checklist", "relUrl": "/pl-rPL/user/firmware.html#pre-update-checklist" - },"1905": { + },"1889": { "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1906": { + },"1890": { "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", "url": "/Meshtastic-Android/main/pl-rPL/user/firmware.html#troubleshooting", "relUrl": "/pl-rPL/user/firmware.html#troubleshooting" - },"1907": { + },"1891": { "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" + },"1892": { + "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" + },"1893": { + "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 devices. | 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" + },"1894": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1895": { + "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" + },"1896": { + "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 | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html#pre-update-checklist", + + "relUrl": "/nl-rNL/user/firmware.html#pre-update-checklist" + },"1897": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1898": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html#troubleshooting", + + "relUrl": "/nl-rNL/user/firmware.html#troubleshooting" + },"1899": { + "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" + },"1900": { + "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" + },"1901": { + "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 devices. | 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" + },"1902": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1903": { + "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" + },"1904": { + "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 | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html#pre-update-checklist", + + "relUrl": "/sv-rSE/user/firmware.html#pre-update-checklist" + },"1905": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1906": { + "doc": "Firmware Updates", + "title": "Felsökning", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html#fels%C3%B6kning", + + "relUrl": "/sv-rSE/user/firmware.html#felsökning" + },"1907": { + "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" },"1908": { - "doc": "韌體更新", - "title": "韌體更新", - "content": "保持 Meshtastic 無線電裝置的韌體為最新版本，以取得新功能、錯誤修正與安全性改善。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html", + "doc": "ファームウェア更新", + "title": "ファームウェア更新", + "content": "新機能、バグ修正、セキュリティ改善のために、Meshtastic 無線機を最新のファームウェアに保ちましょう。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html", - "relUrl": "/zh-rTW/user/firmware.html" + "relUrl": "/ja-rJP/user/firmware.html" },"1909": { - "doc": "韌體更新", - "title": "檢查更新", - "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable devices. | 應用程式將檢查可用的韌體版本。 | 如有可用更新將顯示版本號碼與更新記錄摘要。 | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html#%E6%AA%A2%E6%9F%A5%E6%9B%B4%E6%96%B0", + "doc": "ファームウェア更新", + "title": "更新を確認する", + "content": ". | 接続中の無線機の設定を開き、「詳細設定」で「ファームウェア更新」をタップします。 この項目は、OTA に対応したデバイスでのみ表示されます。 | アプリが、利用可能なファームウェアバージョンを確認します。 | 利用可能な更新には、バージョン番号と変更履歴の概要が表示されます。 | . ", + "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": "/zh-rTW/user/firmware.html#檢查更新" + "relUrl": "/ja-rJP/user/firmware.html#更新を確認する" },"1910": { - "doc": "韌體更新", - "title": "更新方式", - "content": "OTA（無線空中下載）透過藍牙 . Android 使用者最常用的更新方式： . | 請確認您的無線電裝置已透過藍牙連線。 | 前往韌體更新畫面。 | 選取所需的韌體版本。 | 點選「更新」以開始 OTA 流程。 | 請等待更新完成 — 更新期間請勿中斷連線。 | . ⚠️ 警告：中斷韌體更新可能導致裝置變磚。 請確認無線電裝置電量充足（建議 50% 以上），並在整個更新過程中保持藍牙通訊距離。 . 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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", + "doc": "ファームウェア更新", + "title": "更新方法", + "content": "Bluetooth 経由の OTA（無線更新） . Android ユーザーにとって最も一般的な更新方法です： . | 無線機が Bluetooth で接続されていることを確認します。 | ファームウェア更新画面に移動します。 | 希望するファームウェアバージョンを選択します。 | 「更新」をタップして OTA 処理を開始します。 | 更新が完了するまで待ちます。更新中は接続を切断しないでください。 | . ⚠️ 警告： ファームウェア更新を中断すると、デバイスが起動不能になることがあります。 無線機のバッテリーが十分にある（50% 以上を推奨）ことを確認し、処理の間ずっと Bluetooth の通信範囲内に置いてください。 . アプリ内での USB 更新 . 無線機が（Bluetooth ではなく）USB／シリアルで接続されている場合、ファームウェア更新画面に「USB ファイル転送」が表示されます。 アプリはデバイスを DFU モードで再起動し、システムのファイル選択画面を使って .uf2 ファイルをデバイスの DFU ドライブに保存するよう促します。 このオプションは USB／シリアル接続でのみ表示され、Bluetooth では利用できません。 . ℹ️ nRF ブートローダーに関する注意： 一部のデバイス（例：RAK WisBlock RAK4631）では、ベンダーのシリアル DFU ツール（adafruit-nrfutil など）でブートローダーを書き込む必要があります。.uf2 をコピーするだけではブートローダーは更新されません。 これに該当する場合、アプリがヒントを表示します。 . その他の書き込み方法 . 復旧時、または 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": "/zh-rTW/user/firmware.html#更新方式" + "relUrl": "/ja-rJP/user/firmware.html#更新方法" },"1911": { - "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", + "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": "/zh-rTW/user/firmware.html#版本頻道" + "relUrl": "/ja-rJP/user/firmware.html#バージョンチャンネル" },"1912": { - "doc": "韌體更新", - "title": "更新前檢查清單", - "content": "更新前請確認： . | 電量 > 50% | 藍牙連線穩定 | 記錄目前的設定（主要版本更新時可能會重設） | 查看版本說明中是否有重大變更 | . ", - "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", + "doc": "ファームウェア更新", + "title": "更新前のチェックリスト", + "content": "更新する前に： . | バッテリー 50% 以上 | 安定した Bluetooth 接続 | 現在の設定を控えておく（メジャーバージョンの変更時にリセットされることがあります） | 破壊的変更がないか、リリースノートを確認する | . ", + "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": "/zh-rTW/user/firmware.html#更新前檢查清單" + "relUrl": "/ja-rJP/user/firmware.html#更新前のチェックリスト" },"1913": { - "doc": "韌體更新", + "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: . | 無線電裝置將自動重新開機 | 藍牙連線將自動重新建立 | 確認您的設定完整無缺 | 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", + "content": "ファームウェアの書き込み後、アプリは更新を検証し、デバイスが再びオンラインになるのを待ちます： . 更新が成功すると： . | 無線機が自動的に再起動します | Bluetooth 接続が再確立されます | 設定が保持されているか確認します | ファームウェア更新画面の「現在インストール済み」で新しいバージョンを確認します。バージョンは、ノードの詳細ページや接続画面にも表示されます | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html#%E6%9B%B4%E6%96%B0%E5%BE%8C", - "relUrl": "/zh-rTW/user/firmware.html#更新後" + "relUrl": "/ja-rJP/user/firmware.html#更新後" },"1914": { - "doc": "韌體更新", - "title": "故障排除", - "content": "更新卡住 . 若更新似乎停滯不動： . | 請至少等待 5 分鐘再採取行動 | 若確實卡住，請將無線電裝置重新開關機 | 再次嘗試更新 | . 更新後裝置無法開機 . 若您的裝置無法開機： . | 請嘗試透過 USB 連接至電腦 | 在復原／DFU 模式下使用網頁燒錄工具 | 燒錄已知可正常運作的韌體版本 | 前往 Meshtastic Discord 查詢特定裝置的復原步驟 | . 相容性警告 . 應用程式在以下情況可能顯示警告： . | 已連接的無線電裝置韌體低於最低支援版本 | 應用程式與韌體之間的主要版本不相符 | 已棄用的功能需要進行遷移 | . ⚠️ 重要：請在韌體更新之前或同時更新 Meshtastic 應用程式，以確保相容性。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html#%E6%95%85%E9%9A%9C%E6%8E%92%E9%99%A4", + "doc": "ファームウェア更新", + "title": "トラブルシューティング", + "content": "更新が止まる . 更新が固まったように見える場合： . | 手を加える前に、少なくとも 5 分待つ | 本当に止まっている場合は、無線機の電源を入れ直す | もう一度更新を試みる | . 更新後にデバイスが起動しない . デバイスが起動しない場合： . | USB でコンピューターに接続してみる | リカバリー／DFU モードで Web Flasher を使用する | 動作確認済みのファームウェアバージョンを書き込む | デバイス固有の復旧手順については、Meshtastic の Discord を確認する | . 互換性の警告 . 次の場合、アプリが警告を表示することがあります： . | 接続中の無線機のファームウェアが、対応する最小バージョンを下回っている | アプリとファームウェアの間でメジャーバージョンが一致していない | 非推奨の機能に移行が必要 | . ⚠️ 重要： 互換性を確保するため、ファームウェア更新の前、または同時に、必ず Meshtastic アプリを更新してください。 . ", + "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": "/zh-rTW/user/firmware.html#故障排除" + "relUrl": "/ja-rJP/user/firmware.html#トラブルシューティング" },"1915": { - "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", + "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": "/zh-rTW/user/firmware.html#相關主題" + "relUrl": "/ja-rJP/user/firmware.html#関連トピック" },"1916": { "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/cs-rCZ/user/firmware.html", + "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html", - "relUrl": "/cs-rCZ/user/firmware.html" + "relUrl": "/hu-rHU/user/firmware.html" },"1917": { "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 devices. | 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#checking-for-updates", - "relUrl": "/cs-rCZ/user/firmware.html#checking-for-updates" + "relUrl": "/hu-rHU/user/firmware.html#checking-for-updates" },"1918": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#update-methods", - "relUrl": "/cs-rCZ/user/firmware.html#update-methods" + "relUrl": "/hu-rHU/user/firmware.html#update-methods" },"1919": { "doc": "Firmware Updates", "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", + "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": "/cs-rCZ/user/firmware.html#version-channels" + "relUrl": "/hu-rHU/user/firmware.html#version-channels" },"1920": { "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 | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html#pre-update-checklist", + "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#pre-update-checklist", - "relUrl": "/cs-rCZ/user/firmware.html#pre-update-checklist" + "relUrl": "/hu-rHU/user/firmware.html#pre-update-checklist" },"1921": { "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 will reboot automatically | Bluetooth connection will re-establish | 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#post-update", - "relUrl": "/cs-rCZ/user/firmware.html#post-update" + "relUrl": "/hu-rHU/user/firmware.html#post-update" },"1922": { "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html#troubleshooting", + "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#troubleshooting", - "relUrl": "/cs-rCZ/user/firmware.html#troubleshooting" + "relUrl": "/hu-rHU/user/firmware.html#troubleshooting" },"1923": { "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/cs-rCZ/user/firmware.html#related-topics", + "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#related-topics", - "relUrl": "/cs-rCZ/user/firmware.html#related-topics" + "relUrl": "/hu-rHU/user/firmware.html#related-topics" },"1924": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html", - "relUrl": "/fr-rFR/user/firmware.html" + "relUrl": "/ht-rHT/user/firmware.html" },"1925": { "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 devices. | 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#checking-for-updates", - "relUrl": "/fr-rFR/user/firmware.html#checking-for-updates" + "relUrl": "/ht-rHT/user/firmware.html#checking-for-updates" },"1926": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#update-methods", - "relUrl": "/fr-rFR/user/firmware.html#update-methods" + "relUrl": "/ht-rHT/user/firmware.html#update-methods" },"1927": { "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", + "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": "/fr-rFR/user/firmware.html#version-channels" + "relUrl": "/ht-rHT/user/firmware.html#version-channels" },"1928": { "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 | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#pre-update-checklist", + "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#pre-update-checklist", - "relUrl": "/fr-rFR/user/firmware.html#pre-update-checklist" + "relUrl": "/ht-rHT/user/firmware.html#pre-update-checklist" },"1929": { "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 will reboot automatically | Bluetooth connection will re-establish | 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#post-update", - "relUrl": "/fr-rFR/user/firmware.html#post-update" + "relUrl": "/ht-rHT/user/firmware.html#post-update" },"1930": { "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#troubleshooting", + "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#troubleshooting", - "relUrl": "/fr-rFR/user/firmware.html#troubleshooting" + "relUrl": "/ht-rHT/user/firmware.html#troubleshooting" },"1931": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#related-topics", - "relUrl": "/fr-rFR/user/firmware.html#related-topics" + "relUrl": "/ht-rHT/user/firmware.html#related-topics" },"1932": { - "doc": "固件升级", - "title": "固件升级", + "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/zh-rCN/user/firmware.html", + "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html", - "relUrl": "/zh-rCN/user/firmware.html" + "relUrl": "/gl-rES/user/firmware.html" },"1933": { - "doc": "固件升级", + "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 devices. | 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", + "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#checking-for-updates", - "relUrl": "/zh-rCN/user/firmware.html#checking-for-updates" + "relUrl": "/gl-rES/user/firmware.html#checking-for-updates" },"1934": { - "doc": "固件升级", + "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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", + "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#update-methods", - "relUrl": "/zh-rCN/user/firmware.html#update-methods" + "relUrl": "/gl-rES/user/firmware.html#update-methods" },"1935": { - "doc": "固件升级", + "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/zh-rCN/user/firmware.html#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": "/zh-rCN/user/firmware.html#version-channels" + "relUrl": "/gl-rES/user/firmware.html#version-channels" },"1936": { - "doc": "固件升级", + "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 | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/firmware.html#pre-update-checklist", + "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#pre-update-checklist", - "relUrl": "/zh-rCN/user/firmware.html#pre-update-checklist" + "relUrl": "/gl-rES/user/firmware.html#pre-update-checklist" },"1937": { - "doc": "固件升级", + "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 will reboot automatically | Bluetooth connection will re-establish | 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", + "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#post-update", - "relUrl": "/zh-rCN/user/firmware.html#post-update" + "relUrl": "/gl-rES/user/firmware.html#post-update" },"1938": { - "doc": "固件升级", - "title": "问题排查", - "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "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#问题排查" - },"1939": { - "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" - },"1940": { - "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" - },"1941": { - "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 devices. | 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" - },"1942": { - "doc": "Ажурирања фирмвера", - "title": "Update Methods", - "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" - },"1943": { - "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" - },"1944": { - "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 | . ", - "url": "/Meshtastic-Android/main/srp/user/firmware.html#pre-update-checklist", - - "relUrl": "/srp/user/firmware.html#pre-update-checklist" - },"1945": { - "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 will reboot automatically | Bluetooth connection will re-establish | 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" - },"1946": { - "doc": "Ажурирања фирмвера", + "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/srp/user/firmware.html#troubleshooting", + "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#troubleshooting", - "relUrl": "/srp/user/firmware.html#troubleshooting" - },"1947": { - "doc": "Ажурирања фирмвера", + "relUrl": "/gl-rES/user/firmware.html#troubleshooting" + },"1939": { + "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/srp/user/firmware.html#related-topics", + "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#related-topics", - "relUrl": "/srp/user/firmware.html#related-topics" + "relUrl": "/gl-rES/user/firmware.html#related-topics" + },"1940": { + "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" + },"1941": { + "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 devices. | 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" + },"1942": { + "doc": "Firmware Updates", + "title": "Update Methods", + "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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" + },"1943": { + "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" + },"1944": { + "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 | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html#pre-update-checklist", + + "relUrl": "/tr-rTR/user/firmware.html#pre-update-checklist" + },"1945": { + "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 will reboot automatically | Bluetooth connection will re-establish | 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" + },"1946": { + "doc": "Firmware Updates", + "title": "Troubleshooting", + "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html#troubleshooting", + + "relUrl": "/tr-rTR/user/firmware.html#troubleshooting" + },"1947": { + "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" },"1948": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/firmware.html", - "relUrl": "/sq-rAL/user/firmware.html" + "relUrl": "/es-rES/user/firmware.html" },"1949": { "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 devices. | 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", + "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#checking-for-updates", - "relUrl": "/sq-rAL/user/firmware.html#checking-for-updates" + "relUrl": "/es-rES/user/firmware.html#checking-for-updates" },"1950": { "doc": "Firmware Updates", "title": "Update Methods", "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update to begin the OTA process. | Wait for the update to complete — do not disconnect during the update. | . ⚠️ Warning: Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process. 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. ℹ️ nRF bootloader note: Some devices (e.g. RAK WisBlock RAK4631) need their bootloader flashed with the vendor’s serial DFU tool (such as adafruit-nrfutil) — copying the .uf2 alone won’t update the bootloader. The app surfaces a hint when this applies. 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", + "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#update-methods", - "relUrl": "/sq-rAL/user/firmware.html#update-methods" + "relUrl": "/es-rES/user/firmware.html#update-methods" },"1951": { "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", + "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": "/sq-rAL/user/firmware.html#version-channels" + "relUrl": "/es-rES/user/firmware.html#version-channels" },"1952": { "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 | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html#pre-update-checklist", + "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#pre-update-checklist", - "relUrl": "/sq-rAL/user/firmware.html#pre-update-checklist" + "relUrl": "/es-rES/user/firmware.html#pre-update-checklist" },"1953": { "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 will reboot automatically | Bluetooth connection will re-establish | 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", + "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#post-update", - "relUrl": "/sq-rAL/user/firmware.html#post-update" + "relUrl": "/es-rES/user/firmware.html#post-update" },"1954": { "doc": "Firmware Updates", "title": "Troubleshooting", "content": "Update Stuck . If the update appears frozen: . | Wait at least 5 minutes before intervening | If truly stuck, power-cycle the radio | Attempt the update again | . Device Won’t Boot After Update . If your device 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 . The app may show warnings when: . | Connected radio firmware is below minimum supported version | Major version mismatch between app and firmware | Deprecated features need migration | . ⚠️ Important: Always update the Meshtastic app before or alongside firmware updates to ensure compatibility. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html#troubleshooting", + "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#troubleshooting", - "relUrl": "/sq-rAL/user/firmware.html#troubleshooting" + "relUrl": "/es-rES/user/firmware.html#troubleshooting" },"1955": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#related-topics", - "relUrl": "/sq-rAL/user/firmware.html#related-topics" + "relUrl": "/es-rES/user/firmware.html#related-topics" },"1956": { - "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" - },"1957": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"1958": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"1959": { - "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" - },"1960": { - "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" - },"1961": { - "doc": "ヘルプとアプリ内ドキュメント", - "title": "ヘルプとアプリ内ドキュメント", - "content": "このユーザードキュメントはアプリ内にも同梱されており、Meshtastic を離れることなくオフラインで読めます。 「設定 → ヘルプとドキュメント」から開きます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/help-and-docs.html", - - "relUrl": "/ja-rJP/user/help-and-docs.html" - },"1962": { - "doc": "ヘルプとアプリ内ドキュメント", - "title": "閲覧する", - "content": "ドキュメントブラウザーには、ユーザーガイドのすべてのページが一覧表示されます。 ページをタップすると読めます。画像や相互リンクも、ここと同じように機能します。 . 検索 . 検索アイコンをタップして入力すると、タイトルとキーワードでページを絞り込めます。結果は入力に応じて更新されます。 . ブラウザーで開いたページ： . ", - "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#閲覧する" - },"1963": { - "doc": "ヘルプとアプリ内ドキュメント", - "title": "Chirpy：AI アシスタント", - "content": "Chirpy は、この同梱ドキュメントを情報源として、Meshtastic に関する平易な質問に答えます。 ドキュメントブラウザーで Chirpy ボタンをタップして質問を入力すると、回答と、関連ページへのリンクが返ってきます。 . 🔒 プライバシー： 対応する Google 版のデバイスでは、Chirpy は Gemini Nano を使ってオンデバイスで動作します。質問がスマートフォンの外に出ることはありません。 初回使用時に、小さなモデルがダウンロードされます。 . ⚠️ 注意： F-Droid 版、デスクトップ版、iOS 版では、Chirpy は生成モデルではなく、ドキュメントに対するキーワード検索にフォールバックします。 デバイスがオンデバイス AI に対応していない場合、アシスタントは非表示になり、ドキュメントの閲覧と検索は通常どおり行えます。 . ", - "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-アシスタント" - },"1964": { - "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#関連トピック" - },"1965": { - "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" - },"1966": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"1967": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"1968": { - "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" - },"1969": { - "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" - },"1970": { - "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" - },"1971": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"1972": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"1973": { - "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" - },"1974": { - "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" - },"1975": { - "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" - },"1976": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"1977": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"1978": { - "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" - },"1979": { - "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" - },"1980": { - "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" - },"1981": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"1982": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"1983": { - "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" - },"1984": { - "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" - },"1985": { - "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" - },"1986": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"1987": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"1988": { - "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" - },"1989": { - "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" - },"1990": { - "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" - },"1991": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"1992": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"1993": { - "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" - },"1994": { - "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" - },"1995": { - "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" - },"1996": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"1997": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"1998": { - "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" - },"1999": { - "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" - },"2000": { - "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" - },"2001": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2002": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2003": { - "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" - },"2004": { - "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" - },"2005": { - "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" - },"2006": { - "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 . Napauta hakukuvaketta ja kirjoita hakusanoja suodattaaksesi sivuja otsikon ja avainsanojen perusteella — tulokset päivittyvät kirjoittaessasi. Dokumentaatiosivu avattuna selaimessa: . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/help-and-docs.html#selaaminen", - - "relUrl": "/fi-rFI/user/help-and-docs.html#selaaminen" - },"2007": { - "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. ⚠️ Tietosuoja: Google-versiota käyttävillä laitteilla Chirpy toimii laitteella Gemini Nanon avulla — kysymyksesi eivät poistu puhelimestasi. Pieni kielimalli ladataan ensimmäisellä käyttökerralla. ⚠️ Huomautus: F-Droid-, Desktop- ja iOS-versioissa Chirpy käyttää generatiivisen mallin sijaan dokumentaatioon perustuvaa avainsanahakua. Jos laitteesi ei tue laitteella toimivaa tekoälyä, avustaja piilotetaan, mutta voit silti selata dokumentaatiota ja hakea siitä tietoa normaalisti. ", - "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" - },"2008": { - "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" - },"2009": { - "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" - },"2010": { - "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" - },"2011": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2012": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2013": { - "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" - },"2014": { - "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" - },"2015": { - "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" - },"2016": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2017": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2018": { - "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" - },"2019": { - "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" - },"2020": { "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" - },"2021": { + },"1957": { "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2022": { + },"1958": { "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", "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" - },"2023": { + },"1959": { "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" - },"2024": { + },"1960": { "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" - },"2025": { + },"1961": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/help-and-docs.html#help--in-app-docs", - "relUrl": "/hr-rHR/user/help-and-docs.html#help--in-app-docs" - },"2026": { + "relUrl": "/ca-rES/user/help-and-docs.html#help--in-app-docs" + },"1962": { "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 icon and type to filter pages by title and keywords — results update as you type. A page open in the browser: . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/help-and-docs.html#browsing", + "url": "/Meshtastic-Android/main/ca-rES/user/help-and-docs.html#browsing", - "relUrl": "/hr-rHR/user/help-and-docs.html#browsing" - },"2027": { + "relUrl": "/ca-rES/user/help-and-docs.html#browsing" + },"1963": { "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/help-and-docs.html#chirpy--the-ai-assistant", + "url": "/Meshtastic-Android/main/ca-rES/user/help-and-docs.html#chirpy--the-ai-assistant", - "relUrl": "/hr-rHR/user/help-and-docs.html#chirpy--the-ai-assistant" - },"2028": { + "relUrl": "/ca-rES/user/help-and-docs.html#chirpy--the-ai-assistant" + },"1964": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/help-and-docs.html#related-topics", - "relUrl": "/hr-rHR/user/help-and-docs.html#related-topics" - },"2029": { + "relUrl": "/ca-rES/user/help-and-docs.html#related-topics" + },"1965": { "doc": "Help & In-App Docs", "title": "Help & In-App Docs", "content": " ", - "url": "/Meshtastic-Android/main/hr-rHR/user/help-and-docs.html", + "url": "/Meshtastic-Android/main/ca-rES/user/help-and-docs.html", - "relUrl": "/hr-rHR/user/help-and-docs.html" - },"2030": { - "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" - },"2031": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2032": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2033": { - "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" - },"2034": { - "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" - },"2035": { - "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" - },"2036": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2037": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2038": { - "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" - },"2039": { - "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" - },"2040": { - "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" - },"2041": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2042": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2043": { - "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" - },"2044": { - "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" - },"2045": { - "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" - },"2046": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2047": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2048": { - "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#свързани-теми" - },"2049": { - "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" - },"2050": { - "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" - },"2051": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2052": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2053": { - "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" - },"2054": { - "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" - },"2055": { - "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" - },"2056": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2057": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2058": { - "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" - },"2059": { - "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" - },"2060": { + "relUrl": "/ca-rES/user/help-and-docs.html" + },"1966": { "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" - },"2061": { + },"1967": { "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2062": { + },"1968": { "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", "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" - },"2063": { + },"1969": { "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" - },"2064": { + },"1970": { "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" - },"2065": { + },"1971": { "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", + "url": "/Meshtastic-Android/main/uk-rUA/user/help-and-docs.html#help--in-app-docs", - "relUrl": "/pt-rBR/user/help-and-docs.html#help--in-app-docs" - },"2066": { + "relUrl": "/uk-rUA/user/help-and-docs.html#help--in-app-docs" + },"1972": { "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 icon and type to filter pages by title and keywords — results update as you type. A page open in the browser: . ", - "url": "/Meshtastic-Android/main/pt-rBR/user/help-and-docs.html#browsing", + "url": "/Meshtastic-Android/main/uk-rUA/user/help-and-docs.html#browsing", - "relUrl": "/pt-rBR/user/help-and-docs.html#browsing" - },"2067": { + "relUrl": "/uk-rUA/user/help-and-docs.html#browsing" + },"1973": { "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/help-and-docs.html#chirpy--the-ai-assistant", + "url": "/Meshtastic-Android/main/uk-rUA/user/help-and-docs.html#chirpy--the-ai-assistant", - "relUrl": "/pt-rBR/user/help-and-docs.html#chirpy--the-ai-assistant" - },"2068": { + "relUrl": "/uk-rUA/user/help-and-docs.html#chirpy--the-ai-assistant" + },"1974": { "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", + "url": "/Meshtastic-Android/main/uk-rUA/user/help-and-docs.html#related-topics", - "relUrl": "/pt-rBR/user/help-and-docs.html#related-topics" - },"2069": { + "relUrl": "/uk-rUA/user/help-and-docs.html#related-topics" + },"1975": { "doc": "Help & In-App Docs", "title": "Help & In-App Docs", "content": " ", - "url": "/Meshtastic-Android/main/pt-rBR/user/help-and-docs.html", + "url": "/Meshtastic-Android/main/uk-rUA/user/help-and-docs.html", - "relUrl": "/pt-rBR/user/help-and-docs.html" - },"2070": { - "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" - },"2071": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2072": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2073": { - "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" - },"2074": { - "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" - },"2075": { - "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" - },"2076": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2077": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2078": { - "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" - },"2079": { - "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" - },"2080": { - "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" - },"2081": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2082": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2083": { - "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" - },"2084": { - "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" - },"2085": { - "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" - },"2086": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2087": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2088": { - "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" - },"2089": { - "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" - },"2090": { - "doc": "Справка и встроенная документация", - "title": "Справка и встроенная документация", - "content": "Эта же пользовательская документация поставляется внутри приложения, поэтому вы можете читать её офлайн, не покидая Meshtastic. Откройте её через Настройки → Справка и документация. ", - "url": "/Meshtastic-Android/main/ru-rRU/user/help-and-docs.html", - - "relUrl": "/ru-rRU/user/help-and-docs.html" - },"2091": { - "doc": "Справка и встроенная документация", - "title": "Просмотр", - "content": "Браузер документации отображает список всех страниц руководства пользователя. Нажмите на страницу, чтобы прочитать её; изображения и перекрёстные ссылки работают точно так же, как здесь. Поиск . Нажмите на значок поиска и введите текст, чтобы отфильтровать страницы по названию и ключевым словам — результаты обновляются по мере твоего ввода. Страница, открытая в браузере: . ", - "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#просмотр" - },"2092": { - "doc": "Справка и встроенная документация", - "title": "Chirpy — ИИ-ассистент", - "content": "Chirpy отвечает на вопросы о Meshtastic на естественном языке, используя в качестве источника эту встроенную документацию. Нажмите кнопку Chirpy в браузере документации, введите вопрос — и он ответит, предложив ответ и ссылки на соответствующие страницы. 🔒 Приватность: На поддерживаемых устройствах Google-версии Chirpy работает на самом устройстве с помощью Gemini Nano — твои вопросы никогда не покидают твой телефон. Небольшая модель загружается при первом использовании. ⚠️ Примечание: В сборках для F-Droid, настольного приложения и iOS Chirpy переключается на поиск по ключевым словам в документации вместо генеративной модели. Если твоё устройство не поддерживает встроенный ИИ, ассистент скрыт, и ты по-прежнему можешь просматривать и искать документацию обычным способом. ", - "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--ии-ассистент" - },"2093": { - "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#связанные-темы" - },"2094": { - "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" - },"2095": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2096": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2097": { - "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" - },"2098": { - "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" - },"2099": { - "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" - },"2100": { - "doc": "Help & In-App Docs", - "title": "Browsing", - "content": "The docs browser lists every user-guide page. Selle lugemiseks klõpsa lehel; pildid ja ristlingid toimivad ka. Search . Lehtede pealkirja ja märksõnade järgi filtreerimiseks puuduta otsinguikooni ja tippi – tulemused värskendatakse tippimise ajal. 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" - },"2101": { - "doc": "Help & In-App Docs", - "title": "Chirpy — the AI Assistant", - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. Väike mudel laetakse alla esmakordsel kasutamisel. ⚠️ Märkus: F-Droidi, töölaua ja iOS-i versioonide puhul kasutab Chirpy dokumentatsiooni asemel märksõnaotsingut, mitte generatiivset mudelit. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "url": "/Meshtastic-Android/main/et-rEE/user/help-and-docs.html#chirpy--the-ai-assistant", - - "relUrl": "/et-rEE/user/help-and-docs.html#chirpy--the-ai-assistant" - },"2102": { - "doc": "Help & In-App Docs", - "title": "Related Topics", - "content": ". | [Tõlgi rakendus] (translate) — kuidas need lehed teistesse keeltesse lokaliseeritakse | App Functions — the separate system-AI integration (distinct from Chirpy) | . ", - "url": "/Meshtastic-Android/main/et-rEE/user/help-and-docs.html#related-topics", - - "relUrl": "/et-rEE/user/help-and-docs.html#related-topics" - },"2103": { - "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" - },"2104": { - "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" - },"2105": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2106": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2107": { - "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" - },"2108": { - "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" - },"2109": { - "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" - },"2110": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2111": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2112": { - "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" - },"2113": { - "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" - },"2114": { - "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" - },"2115": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2116": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2117": { - "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" - },"2118": { - "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" - },"2119": { - "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" - },"2120": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2121": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2122": { - "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" - },"2123": { - "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" - },"2124": { - "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" - },"2125": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2126": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2127": { - "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#相關主題" - },"2128": { - "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" - },"2129": { - "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" - },"2130": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2131": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2132": { - "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" - },"2133": { - "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" - },"2134": { - "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" - },"2135": { - "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2136": { - "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", - "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" - },"2137": { - "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" - },"2138": { - "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" - },"2139": { + "relUrl": "/uk-rUA/user/help-and-docs.html" + },"1976": { "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" - },"2140": { + },"1977": { "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2141": { + },"1978": { "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", "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" - },"2142": { + },"1979": { "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" - },"2143": { + },"1980": { "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" - },"2144": { + },"1981": { + "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" + },"1982": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"1983": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"1984": { + "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#свързани-теми" + },"1985": { + "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" + },"1986": { + "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" + },"1987": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"1988": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"1989": { + "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#相關主題" + },"1990": { + "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" + },"1991": { + "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" + },"1992": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"1993": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"1994": { + "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" + },"1995": { + "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" + },"1996": { + "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" + },"1997": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"1998": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"1999": { + "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" + },"2000": { + "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" + },"2001": { + "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" + },"2002": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2003": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2004": { + "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" + },"2005": { + "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" + },"2006": { + "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" + },"2007": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2008": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2009": { + "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" + },"2010": { + "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" + },"2011": { + "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" + },"2012": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2013": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2014": { + "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" + },"2015": { + "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" + },"2016": { + "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" + },"2017": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2018": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2019": { + "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" + },"2020": { + "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" + },"2021": { + "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" + },"2022": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2023": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2024": { + "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" + },"2025": { + "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" + },"2026": { + "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" + },"2027": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2028": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2029": { + "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" + },"2030": { + "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" + },"2031": { "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" - },"2145": { + },"2032": { "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2146": { + },"2033": { "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", "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" - },"2147": { + },"2034": { "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" - },"2148": { + },"2035": { "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" - },"2149": { + },"2036": { + "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" + },"2037": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2038": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2039": { + "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" + },"2040": { + "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" + },"2041": { + "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" + },"2042": { + "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 . Napauta hakukuvaketta ja kirjoita hakusanoja suodattaaksesi sivuja otsikon ja avainsanojen perusteella — tulokset päivittyvät kirjoittaessasi. Dokumentaatiosivu avattuna selaimessa: . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/help-and-docs.html#selaaminen", + + "relUrl": "/fi-rFI/user/help-and-docs.html#selaaminen" + },"2043": { + "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. ⚠️ Tietosuoja: Google-versiota käyttävillä laitteilla Chirpy toimii laitteella Gemini Nanon avulla — kysymyksesi eivät poistu puhelimestasi. Pieni kielimalli ladataan ensimmäisellä käyttökerralla. ⚠️ Huomautus: F-Droid-, Desktop- ja iOS-versioissa Chirpy käyttää generatiivisen mallin sijaan dokumentaatioon perustuvaa avainsanahakua. Jos laitteesi ei tue laitteella toimivaa tekoälyä, avustaja piilotetaan, mutta voit silti selata dokumentaatiota ja hakea siitä tietoa normaalisti. ", + "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" + },"2044": { + "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" + },"2045": { + "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" + },"2046": { + "doc": "Справка и встроенная документация", + "title": "Справка и встроенная документация", + "content": "Эта же пользовательская документация поставляется внутри приложения, поэтому вы можете читать её офлайн, не покидая Meshtastic. Откройте её через Настройки → Справка и документация. ", + "url": "/Meshtastic-Android/main/ru-rRU/user/help-and-docs.html", + + "relUrl": "/ru-rRU/user/help-and-docs.html" + },"2047": { + "doc": "Справка и встроенная документация", + "title": "Просмотр", + "content": "Браузер документации отображает список всех страниц руководства пользователя. Нажмите на страницу, чтобы прочитать её; изображения и перекрёстные ссылки работают точно так же, как здесь. Поиск . Нажмите на значок поиска и введите текст, чтобы отфильтровать страницы по названию и ключевым словам — результаты обновляются по мере твоего ввода. Страница, открытая в браузере: . ", + "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#просмотр" + },"2048": { + "doc": "Справка и встроенная документация", + "title": "Chirpy — ИИ-ассистент", + "content": "Chirpy отвечает на вопросы о Meshtastic на естественном языке, используя в качестве источника эту встроенную документацию. Нажмите кнопку Chirpy в браузере документации, введите вопрос — и он ответит, предложив ответ и ссылки на соответствующие страницы. 🔒 Приватность: На поддерживаемых устройствах Google-версии Chirpy работает на самом устройстве с помощью Gemini Nano — твои вопросы никогда не покидают твой телефон. Небольшая модель загружается при первом использовании. ⚠️ Примечание: В сборках для F-Droid, настольного приложения и iOS Chirpy переключается на поиск по ключевым словам в документации вместо генеративной модели. Если твоё устройство не поддерживает встроенный ИИ, ассистент скрыт, и ты по-прежнему можешь просматривать и искать документацию обычным способом. ", + "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--ии-ассистент" + },"2049": { + "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#связанные-темы" + },"2050": { + "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" + },"2051": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2052": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2053": { + "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" + },"2054": { + "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" + },"2055": { + "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" + },"2056": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2057": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2058": { + "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" + },"2059": { + "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" + },"2060": { "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" - },"2150": { + },"2061": { "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 icon and type to filter pages by title and keywords — results update as you type. 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" - },"2151": { + },"2062": { "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", "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" - },"2152": { + },"2063": { "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" - },"2153": { + },"2064": { "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" + },"2065": { + "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" + },"2066": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2067": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2068": { + "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" + },"2069": { + "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" + },"2070": { + "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" + },"2071": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2072": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2073": { + "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" + },"2074": { + "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" + },"2075": { + "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" + },"2076": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2077": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2078": { + "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" + },"2079": { + "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" + },"2080": { + "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" + },"2081": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2082": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2083": { + "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" + },"2084": { + "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" + },"2085": { + "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" + },"2086": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2087": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2088": { + "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" + },"2089": { + "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" + },"2090": { + "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" + },"2091": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2092": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2093": { + "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" + },"2094": { + "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" + },"2095": { + "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" + },"2096": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2097": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2098": { + "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" + },"2099": { + "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" + },"2100": { + "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" + },"2101": { + "doc": "Help & In-App Docs", + "title": "Browsing", + "content": "The docs browser lists every user-guide page. Selle lugemiseks klõpsa lehel; pildid ja ristlingid toimivad ka. Search . Lehtede pealkirja ja märksõnade järgi filtreerimiseks puuduta otsinguikooni ja tippi – tulemused värskendatakse tippimise ajal. 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" + },"2102": { + "doc": "Help & In-App Docs", + "title": "Chirpy — the AI Assistant", + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. Väike mudel laetakse alla esmakordsel kasutamisel. ⚠️ Märkus: F-Droidi, töölaua ja iOS-i versioonide puhul kasutab Chirpy dokumentatsiooni asemel märksõnaotsingut, mitte generatiivset mudelit. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "url": "/Meshtastic-Android/main/et-rEE/user/help-and-docs.html#chirpy--the-ai-assistant", + + "relUrl": "/et-rEE/user/help-and-docs.html#chirpy--the-ai-assistant" + },"2103": { + "doc": "Help & In-App Docs", + "title": "Related Topics", + "content": ". | [Tõlgi rakendus] (translate) — kuidas need lehed teistesse keeltesse lokaliseeritakse | App Functions — the separate system-AI integration (distinct from Chirpy) | . ", + "url": "/Meshtastic-Android/main/et-rEE/user/help-and-docs.html#related-topics", + + "relUrl": "/et-rEE/user/help-and-docs.html#related-topics" + },"2104": { + "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" + },"2105": { + "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" + },"2106": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2107": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2108": { + "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" + },"2109": { + "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" + },"2110": { + "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" + },"2111": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2112": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2113": { + "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" + },"2114": { + "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" + },"2115": { + "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" + },"2116": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2117": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2118": { + "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" + },"2119": { + "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" + },"2120": { + "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" + },"2121": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2122": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2123": { + "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" + },"2124": { + "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" + },"2125": { + "doc": "ヘルプとアプリ内ドキュメント", + "title": "ヘルプとアプリ内ドキュメント", + "content": "このユーザードキュメントはアプリ内にも同梱されており、Meshtastic を離れることなくオフラインで読めます。 「設定 → ヘルプとドキュメント」から開きます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/help-and-docs.html", + + "relUrl": "/ja-rJP/user/help-and-docs.html" + },"2126": { + "doc": "ヘルプとアプリ内ドキュメント", + "title": "閲覧する", + "content": "ドキュメントブラウザーには、ユーザーガイドのすべてのページが一覧表示されます。 ページをタップすると読めます。画像や相互リンクも、ここと同じように機能します。 . 検索 . 検索アイコンをタップして入力すると、タイトルとキーワードでページを絞り込めます。結果は入力に応じて更新されます。 . ブラウザーで開いたページ： . ", + "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#閲覧する" + },"2127": { + "doc": "ヘルプとアプリ内ドキュメント", + "title": "Chirpy：AI アシスタント", + "content": "Chirpy は、この同梱ドキュメントを情報源として、Meshtastic に関する平易な質問に答えます。 ドキュメントブラウザーで Chirpy ボタンをタップして質問を入力すると、回答と、関連ページへのリンクが返ってきます。 . 🔒 プライバシー： 対応する Google 版のデバイスでは、Chirpy は Gemini Nano を使ってオンデバイスで動作します。質問がスマートフォンの外に出ることはありません。 初回使用時に、小さなモデルがダウンロードされます。 . ⚠️ 注意： F-Droid 版、デスクトップ版、iOS 版では、Chirpy は生成モデルではなく、ドキュメントに対するキーワード検索にフォールバックします。 デバイスがオンデバイス AI に対応していない場合、アシスタントは非表示になり、ドキュメントの閲覧と検索は通常どおり行えます。 . ", + "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-アシスタント" + },"2128": { + "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#関連トピック" + },"2129": { + "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" + },"2130": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2131": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2132": { + "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" + },"2133": { + "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" + },"2134": { + "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" + },"2135": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2136": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2137": { + "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" + },"2138": { + "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" + },"2139": { + "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" + },"2140": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2141": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2142": { + "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" + },"2143": { + "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" + },"2144": { + "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" + },"2145": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2146": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2147": { + "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" + },"2148": { + "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" + },"2149": { + "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" + },"2150": { + "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 icon and type to filter pages by title and keywords — results update as you type. 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" + },"2151": { + "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. 🔒 Privacy: On supported Google-flavor devices, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ⚠️ Note: On F-Droid, Desktop, and iOS builds, Chirpy falls back to a keyword search over the documentation rather than a generative model. If your device doesn’t support on-device AI, the assistant is hidden and you can still browse and search the docs normally. ", + "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" + },"2152": { + "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" + },"2153": { + "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" },"2154": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/is-rIS/#meshtastic-android-app-documentation", - - "relUrl": "/is-rIS/#meshtastic-android-app-documentation" - },"2155": { - "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" - },"2156": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/is-rIS/", - - "relUrl": "/is-rIS/" - },"2157": { - "doc": "ホーム", - "title": "Meshtastic Android アプリのドキュメント", - "content": "KMP（Kotlin Multiplatform）で構築された Meshtastic の Android、デスクトップ、iOS アプリ向けの、ユーザーおよび開発者向けドキュメントです。 . サイドバーのナビゲーションから、アプリの機能についてはユーザーガイドを、プロジェクトへの貢献については開発者ガイドをご覧ください。 . ", - "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-アプリのドキュメント" - },"2158": { - "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/#クイックリンク" - },"2159": { - "doc": "ホーム", - "title": "ホーム", - "content": " ", - "url": "/Meshtastic-Android/main/ja-rJP/", - - "relUrl": "/ja-rJP/" - },"2160": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/ca-rES/#meshtastic-android-app-documentation", - - "relUrl": "/ca-rES/#meshtastic-android-app-documentation" - },"2161": { - "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" - },"2162": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/ca-rES/", - - "relUrl": "/ca-rES/" - },"2163": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/sr-rLatn/#meshtastic-android-app-documentation", - - "relUrl": "/sr-rLatn/#meshtastic-android-app-documentation" - },"2164": { - "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" - },"2165": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/sr-rLatn/", - - "relUrl": "/sr-rLatn/" - },"2166": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/ko-rKR/#meshtastic-android-app-documentation", - - "relUrl": "/ko-rKR/#meshtastic-android-app-documentation" - },"2167": { - "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" - },"2168": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/ko-rKR/", - - "relUrl": "/ko-rKR/" - },"2169": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/ro-rRO/#meshtastic-android-app-documentation", - - "relUrl": "/ro-rRO/#meshtastic-android-app-documentation" - },"2170": { - "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" - },"2171": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/ro-rRO/", - - "relUrl": "/ro-rRO/" - },"2172": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/ga-rIE/#meshtastic-android-app-documentation", - - "relUrl": "/ga-rIE/#meshtastic-android-app-documentation" - },"2173": { - "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" - },"2174": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/ga-rIE/", - - "relUrl": "/ga-rIE/" - },"2175": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/iw-rIL/#meshtastic-android-app-documentation", - - "relUrl": "/iw-rIL/#meshtastic-android-app-documentation" - },"2176": { - "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" - },"2177": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/iw-rIL/", - - "relUrl": "/iw-rIL/" - },"2178": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/sv-rSE/#meshtastic-android-app-documentation", - - "relUrl": "/sv-rSE/#meshtastic-android-app-documentation" - },"2179": { - "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" - },"2180": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/sv-rSE/", - - "relUrl": "/sv-rSE/" - },"2181": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/ht-rHT/#meshtastic-android-app-documentation", - - "relUrl": "/ht-rHT/#meshtastic-android-app-documentation" - },"2182": { - "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" - },"2183": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/ht-rHT/", - - "relUrl": "/ht-rHT/" - },"2184": { - "doc": "Etusivu", - "title": "Meshtastic Android -sovelluksen dokumentaatio", - "content": "Käyttäjä- ja kehittäjädokumentaatio Meshtasticin Android-, Desktop- ja iOS-sovelluksille, jotka on toteutettu Kotlin Multiplatform (KMP) -teknologialla. 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" - },"2185": { - "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" - },"2186": { - "doc": "Etusivu", - "title": "Etusivu", - "content": " ", - "url": "/Meshtastic-Android/main/fi-rFI/", - - "relUrl": "/fi-rFI/" - },"2187": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/gl-rES/#meshtastic-android-app-documentation", - - "relUrl": "/gl-rES/#meshtastic-android-app-documentation" - },"2188": { - "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" - },"2189": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/gl-rES/", - - "relUrl": "/gl-rES/" - },"2190": { - "doc": "Головна", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/uk-rUA/#meshtastic-android-app-documentation", - - "relUrl": "/uk-rUA/#meshtastic-android-app-documentation" - },"2191": { - "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/#швидкі-посилання" - },"2192": { - "doc": "Головна", - "title": "Головна", - "content": " ", - "url": "/Meshtastic-Android/main/uk-rUA/", - - "relUrl": "/uk-rUA/" - },"2193": { "doc": "Startseite", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", "url": "/Meshtastic-Android/main/de-rDE/#meshtastic-android-app-documentation", "relUrl": "/de-rDE/#meshtastic-android-app-documentation" - },"2194": { + },"2155": { "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" - },"2195": { + },"2156": { "doc": "Startseite", "title": "Startseite", "content": " ", "url": "/Meshtastic-Android/main/de-rDE/", "relUrl": "/de-rDE/" - },"2196": { + },"2157": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/hr-rHR/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/ca-rES/#meshtastic-android-app-documentation", - "relUrl": "/hr-rHR/#meshtastic-android-app-documentation" - },"2197": { + "relUrl": "/ca-rES/#meshtastic-android-app-documentation" + },"2158": { "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", + "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": "/hr-rHR/#quick-links" - },"2198": { + "relUrl": "/ca-rES/#quick-links" + },"2159": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/hr-rHR/", + "url": "/Meshtastic-Android/main/ca-rES/", - "relUrl": "/hr-rHR/" - },"2199": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/lt-rLT/#meshtastic-android-app-documentation", - - "relUrl": "/lt-rLT/#meshtastic-android-app-documentation" - },"2200": { - "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" - },"2201": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/lt-rLT/", - - "relUrl": "/lt-rLT/" - },"2202": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/en/#meshtastic-android-app-documentation", - - "relUrl": "/en/#meshtastic-android-app-documentation" - },"2203": { - "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" - },"2204": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/en/", - - "relUrl": "/en/" - },"2205": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/hu-rHU/#meshtastic-android-app-documentation", - - "relUrl": "/hu-rHU/#meshtastic-android-app-documentation" - },"2206": { - "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" - },"2207": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/hu-rHU/", - - "relUrl": "/hu-rHU/" - },"2208": { - "doc": "Home", - "title": "Документация за приложението Meshtastic за Android", - "content": "Документация за потребители и разработчици за приложенията Meshtastic за Android, настолни компютри и iOS, задвижвани от KMP (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" - },"2209": { - "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/#бързи-връзки" - },"2210": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/bg-rBG/", - - "relUrl": "/bg-rBG/" - },"2211": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/sl-rSI/#meshtastic-android-app-documentation", - - "relUrl": "/sl-rSI/#meshtastic-android-app-documentation" - },"2212": { - "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" - },"2213": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/sl-rSI/", - - "relUrl": "/sl-rSI/" - },"2214": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/pt-rPT/#meshtastic-android-app-documentation", - - "relUrl": "/pt-rPT/#meshtastic-android-app-documentation" - },"2215": { - "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" - },"2216": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/pt-rPT/", - - "relUrl": "/pt-rPT/" - },"2217": { + "relUrl": "/ca-rES/" + },"2160": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", "url": "/Meshtastic-Android/main/be-rBY/#meshtastic-android-app-documentation", "relUrl": "/be-rBY/#meshtastic-android-app-documentation" - },"2218": { + },"2161": { "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" - },"2219": { + },"2162": { "doc": "Home", "title": "Home", "content": " ", "url": "/Meshtastic-Android/main/be-rBY/", "relUrl": "/be-rBY/" - },"2220": { + },"2163": { + "doc": "Головна", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/uk-rUA/#meshtastic-android-app-documentation", + + "relUrl": "/uk-rUA/#meshtastic-android-app-documentation" + },"2164": { + "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/#швидкі-посилання" + },"2165": { + "doc": "Головна", + "title": "Головна", + "content": " ", + "url": "/Meshtastic-Android/main/uk-rUA/", + + "relUrl": "/uk-rUA/" + },"2166": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/zh-rCN/#meshtastic-android-app-documentation", + + "relUrl": "/zh-rCN/#meshtastic-android-app-documentation" + },"2167": { + "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" + },"2168": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/zh-rCN/", + + "relUrl": "/zh-rCN/" + },"2169": { + "doc": "Home", + "title": "Документация за приложението Meshtastic за Android", + "content": "Документация за потребители и разработчици за приложенията Meshtastic за Android, настолни компютри и iOS, задвижвани от KMP (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" + },"2170": { + "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/#бързи-връзки" + },"2171": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/bg-rBG/", + + "relUrl": "/bg-rBG/" + },"2172": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/zh-rTW/#meshtastic-android-app-documentation", + + "relUrl": "/zh-rTW/#meshtastic-android-app-documentation" + },"2173": { + "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-rTW/#quick-links", + + "relUrl": "/zh-rTW/#quick-links" + },"2174": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/zh-rTW/", + + "relUrl": "/zh-rTW/" + },"2175": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/sr-rLatn/#meshtastic-android-app-documentation", + + "relUrl": "/sr-rLatn/#meshtastic-android-app-documentation" + },"2176": { + "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" + },"2177": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/sr-rLatn/", + + "relUrl": "/sr-rLatn/" + },"2178": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/cs-rCZ/#meshtastic-android-app-documentation", + + "relUrl": "/cs-rCZ/#meshtastic-android-app-documentation" + },"2179": { + "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/cs-rCZ/#quick-links", + + "relUrl": "/cs-rCZ/#quick-links" + },"2180": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/cs-rCZ/", + + "relUrl": "/cs-rCZ/" + },"2181": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/en/#meshtastic-android-app-documentation", + + "relUrl": "/en/#meshtastic-android-app-documentation" + },"2182": { + "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" + },"2183": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/en/", + + "relUrl": "/en/" + },"2184": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/sl-rSI/#meshtastic-android-app-documentation", + + "relUrl": "/sl-rSI/#meshtastic-android-app-documentation" + },"2185": { + "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" + },"2186": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/sl-rSI/", + + "relUrl": "/sl-rSI/" + },"2187": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/it-rIT/#meshtastic-android-app-documentation", + + "relUrl": "/it-rIT/#meshtastic-android-app-documentation" + },"2188": { + "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" + },"2189": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/it-rIT/", + + "relUrl": "/it-rIT/" + },"2190": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", "url": "/Meshtastic-Android/main/pt-rBR/#meshtastic-android-app-documentation", "relUrl": "/pt-rBR/#meshtastic-android-app-documentation" - },"2221": { + },"2191": { "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" - },"2222": { + },"2192": { "doc": "Home", "title": "Home", "content": " ", "url": "/Meshtastic-Android/main/pt-rBR/", "relUrl": "/pt-rBR/" - },"2223": { + },"2193": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/el-rGR/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/is-rIS/#meshtastic-android-app-documentation", - "relUrl": "/el-rGR/#meshtastic-android-app-documentation" - },"2224": { + "relUrl": "/is-rIS/#meshtastic-android-app-documentation" + },"2194": { "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", + "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": "/el-rGR/#quick-links" - },"2225": { + "relUrl": "/is-rIS/#quick-links" + },"2195": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/el-rGR/", + "url": "/Meshtastic-Android/main/is-rIS/", - "relUrl": "/el-rGR/" - },"2226": { + "relUrl": "/is-rIS/" + },"2196": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/es-rES/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/fr-rFR/#meshtastic-android-app-documentation", - "relUrl": "/es-rES/#meshtastic-android-app-documentation" - },"2227": { + "relUrl": "/fr-rFR/#meshtastic-android-app-documentation" + },"2197": { "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", + "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/fr-rFR/#quick-links", - "relUrl": "/es-rES/#quick-links" - },"2228": { + "relUrl": "/fr-rFR/#quick-links" + },"2198": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/es-rES/", + "url": "/Meshtastic-Android/main/fr-rFR/", - "relUrl": "/es-rES/" - },"2229": { + "relUrl": "/fr-rFR/" + },"2199": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/tr-rTR/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/srp/#meshtastic-android-app-documentation", - "relUrl": "/tr-rTR/#meshtastic-android-app-documentation" - },"2230": { + "relUrl": "/srp/#meshtastic-android-app-documentation" + },"2200": { "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", + "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": "/tr-rTR/#quick-links" - },"2231": { + "relUrl": "/srp/#quick-links" + },"2201": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/tr-rTR/", + "url": "/Meshtastic-Android/main/srp/", - "relUrl": "/tr-rTR/" - },"2232": { + "relUrl": "/srp/" + },"2202": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/no-rNO/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/sk-rSK/#meshtastic-android-app-documentation", - "relUrl": "/no-rNO/#meshtastic-android-app-documentation" - },"2233": { + "relUrl": "/sk-rSK/#meshtastic-android-app-documentation" + },"2203": { "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", + "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": "/no-rNO/#quick-links" - },"2234": { + "relUrl": "/sk-rSK/#quick-links" + },"2204": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/no-rNO/", + "url": "/Meshtastic-Android/main/sk-rSK/", - "relUrl": "/no-rNO/" - },"2235": { + "relUrl": "/sk-rSK/" + },"2205": { + "doc": "Etusivu", + "title": "Meshtastic Android -sovelluksen dokumentaatio", + "content": "Käyttäjä- ja kehittäjädokumentaatio Meshtasticin Android-, Desktop- ja iOS-sovelluksille, jotka on toteutettu Kotlin Multiplatform (KMP) -teknologialla. 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" + },"2206": { + "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" + },"2207": { + "doc": "Etusivu", + "title": "Etusivu", + "content": " ", + "url": "/Meshtastic-Android/main/fi-rFI/", + + "relUrl": "/fi-rFI/" + },"2208": { "doc": "Домой", "title": "Документация приложения Meshtastic Android", "content": "Документация для пользователей и разработчиков приложения Meshtastic на Android, ПК и iOS, работающих на KMP (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" - },"2236": { + },"2209": { "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/#быстрые-ссылки" - },"2237": { + },"2210": { "doc": "Домой", "title": "Домой", "content": " ", "url": "/Meshtastic-Android/main/ru-rRU/", "relUrl": "/ru-rRU/" + },"2211": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/ko-rKR/#meshtastic-android-app-documentation", + + "relUrl": "/ko-rKR/#meshtastic-android-app-documentation" + },"2212": { + "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" + },"2213": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/ko-rKR/", + + "relUrl": "/ko-rKR/" + },"2214": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/hr-rHR/#meshtastic-android-app-documentation", + + "relUrl": "/hr-rHR/#meshtastic-android-app-documentation" + },"2215": { + "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" + },"2216": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/hr-rHR/", + + "relUrl": "/hr-rHR/" + },"2217": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/sq-rAL/#meshtastic-android-app-documentation", + + "relUrl": "/sq-rAL/#meshtastic-android-app-documentation" + },"2218": { + "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" + },"2219": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/sq-rAL/", + + "relUrl": "/sq-rAL/" + },"2220": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/no-rNO/#meshtastic-android-app-documentation", + + "relUrl": "/no-rNO/#meshtastic-android-app-documentation" + },"2221": { + "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" + },"2222": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/no-rNO/", + + "relUrl": "/no-rNO/" + },"2223": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/lt-rLT/#meshtastic-android-app-documentation", + + "relUrl": "/lt-rLT/#meshtastic-android-app-documentation" + },"2224": { + "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" + },"2225": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/lt-rLT/", + + "relUrl": "/lt-rLT/" + },"2226": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/ar-rSA/#meshtastic-android-app-documentation", + + "relUrl": "/ar-rSA/#meshtastic-android-app-documentation" + },"2227": { + "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" + },"2228": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/ar-rSA/", + + "relUrl": "/ar-rSA/" + },"2229": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/pt-rPT/#meshtastic-android-app-documentation", + + "relUrl": "/pt-rPT/#meshtastic-android-app-documentation" + },"2230": { + "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" + },"2231": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/pt-rPT/", + + "relUrl": "/pt-rPT/" + },"2232": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/iw-rIL/#meshtastic-android-app-documentation", + + "relUrl": "/iw-rIL/#meshtastic-android-app-documentation" + },"2233": { + "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" + },"2234": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/iw-rIL/", + + "relUrl": "/iw-rIL/" + },"2235": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/el-rGR/#meshtastic-android-app-documentation", + + "relUrl": "/el-rGR/#meshtastic-android-app-documentation" + },"2236": { + "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" + },"2237": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/el-rGR/", + + "relUrl": "/el-rGR/" },"2238": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/nl-rNL/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/ro-rRO/#meshtastic-android-app-documentation", - "relUrl": "/nl-rNL/#meshtastic-android-app-documentation" + "relUrl": "/ro-rRO/#meshtastic-android-app-documentation" },"2239": { "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", + "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": "/nl-rNL/#quick-links" + "relUrl": "/ro-rRO/#quick-links" },"2240": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/nl-rNL/", + "url": "/Meshtastic-Android/main/ro-rRO/", - "relUrl": "/nl-rNL/" + "relUrl": "/ro-rRO/" },"2241": { "doc": "Home", "title": "Meshtastic Androidi rakenduse dokumentatsioon", @@ -15710,1815 +15710,1815 @@ "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/it-rIT/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/ga-rIE/#meshtastic-android-app-documentation", - "relUrl": "/it-rIT/#meshtastic-android-app-documentation" + "relUrl": "/ga-rIE/#meshtastic-android-app-documentation" },"2245": { "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", + "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": "/it-rIT/#quick-links" + "relUrl": "/ga-rIE/#quick-links" },"2246": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/it-rIT/", + "url": "/Meshtastic-Android/main/ga-rIE/", - "relUrl": "/it-rIT/" + "relUrl": "/ga-rIE/" },"2247": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/ar-rSA/#meshtastic-android-app-documentation", - - "relUrl": "/ar-rSA/#meshtastic-android-app-documentation" - },"2248": { - "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" - },"2249": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/ar-rSA/", - - "relUrl": "/ar-rSA/" - },"2250": { - "doc": "Home", - "title": "Meshtastic Android App Documentation", - "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/sk-rSK/#meshtastic-android-app-documentation", - - "relUrl": "/sk-rSK/#meshtastic-android-app-documentation" - },"2251": { - "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" - },"2252": { - "doc": "Home", - "title": "Home", - "content": " ", - "url": "/Meshtastic-Android/main/sk-rSK/", - - "relUrl": "/sk-rSK/" - },"2253": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", "url": "/Meshtastic-Android/main/pl-rPL/#meshtastic-android-app-documentation", "relUrl": "/pl-rPL/#meshtastic-android-app-documentation" - },"2254": { + },"2248": { "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" - },"2255": { + },"2249": { "doc": "Home", "title": "Home", "content": " ", "url": "/Meshtastic-Android/main/pl-rPL/", "relUrl": "/pl-rPL/" - },"2256": { + },"2250": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/zh-rTW/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/nl-rNL/#meshtastic-android-app-documentation", - "relUrl": "/zh-rTW/#meshtastic-android-app-documentation" - },"2257": { + "relUrl": "/nl-rNL/#meshtastic-android-app-documentation" + },"2251": { "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-rTW/#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": "/zh-rTW/#quick-links" - },"2258": { + "relUrl": "/nl-rNL/#quick-links" + },"2252": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/zh-rTW/", + "url": "/Meshtastic-Android/main/nl-rNL/", - "relUrl": "/zh-rTW/" + "relUrl": "/nl-rNL/" + },"2253": { + "doc": "Home", + "title": "Meshtastic Android App Documentation", + "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", + "url": "/Meshtastic-Android/main/sv-rSE/#meshtastic-android-app-documentation", + + "relUrl": "/sv-rSE/#meshtastic-android-app-documentation" + },"2254": { + "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" + },"2255": { + "doc": "Home", + "title": "Home", + "content": " ", + "url": "/Meshtastic-Android/main/sv-rSE/", + + "relUrl": "/sv-rSE/" + },"2256": { + "doc": "ホーム", + "title": "Meshtastic Android アプリのドキュメント", + "content": "KMP（Kotlin Multiplatform）で構築された Meshtastic の Android、デスクトップ、iOS アプリ向けの、ユーザーおよび開発者向けドキュメントです。 . サイドバーのナビゲーションから、アプリの機能についてはユーザーガイドを、プロジェクトへの貢献については開発者ガイドをご覧ください。 . ", + "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-アプリのドキュメント" + },"2257": { + "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/#クイックリンク" + },"2258": { + "doc": "ホーム", + "title": "ホーム", + "content": " ", + "url": "/Meshtastic-Android/main/ja-rJP/", + + "relUrl": "/ja-rJP/" },"2259": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/cs-rCZ/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/hu-rHU/#meshtastic-android-app-documentation", - "relUrl": "/cs-rCZ/#meshtastic-android-app-documentation" + "relUrl": "/hu-rHU/#meshtastic-android-app-documentation" },"2260": { "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/cs-rCZ/#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": "/cs-rCZ/#quick-links" + "relUrl": "/hu-rHU/#quick-links" },"2261": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/cs-rCZ/", + "url": "/Meshtastic-Android/main/hu-rHU/", - "relUrl": "/cs-rCZ/" + "relUrl": "/hu-rHU/" },"2262": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/fr-rFR/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/ht-rHT/#meshtastic-android-app-documentation", - "relUrl": "/fr-rFR/#meshtastic-android-app-documentation" + "relUrl": "/ht-rHT/#meshtastic-android-app-documentation" },"2263": { "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/fr-rFR/#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": "/fr-rFR/#quick-links" + "relUrl": "/ht-rHT/#quick-links" },"2264": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/fr-rFR/", + "url": "/Meshtastic-Android/main/ht-rHT/", - "relUrl": "/fr-rFR/" + "relUrl": "/ht-rHT/" },"2265": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/zh-rCN/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/gl-rES/#meshtastic-android-app-documentation", - "relUrl": "/zh-rCN/#meshtastic-android-app-documentation" + "relUrl": "/gl-rES/#meshtastic-android-app-documentation" },"2266": { "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", + "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": "/zh-rCN/#quick-links" + "relUrl": "/gl-rES/#quick-links" },"2267": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/zh-rCN/", + "url": "/Meshtastic-Android/main/gl-rES/", - "relUrl": "/zh-rCN/" + "relUrl": "/gl-rES/" },"2268": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/srp/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/tr-rTR/#meshtastic-android-app-documentation", - "relUrl": "/srp/#meshtastic-android-app-documentation" + "relUrl": "/tr-rTR/#meshtastic-android-app-documentation" },"2269": { "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", + "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": "/srp/#quick-links" + "relUrl": "/tr-rTR/#quick-links" },"2270": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/srp/", + "url": "/Meshtastic-Android/main/tr-rTR/", - "relUrl": "/srp/" + "relUrl": "/tr-rTR/" },"2271": { "doc": "Home", "title": "Meshtastic Android App Documentation", "content": "User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform). Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ", - "url": "/Meshtastic-Android/main/sq-rAL/#meshtastic-android-app-documentation", + "url": "/Meshtastic-Android/main/es-rES/#meshtastic-android-app-documentation", - "relUrl": "/sq-rAL/#meshtastic-android-app-documentation" + "relUrl": "/es-rES/#meshtastic-android-app-documentation" },"2272": { "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", + "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": "/sq-rAL/#quick-links" + "relUrl": "/es-rES/#quick-links" },"2273": { "doc": "Home", "title": "Home", "content": " ", - "url": "/Meshtastic-Android/main/sq-rAL/", + "url": "/Meshtastic-Android/main/es-rES/", - "relUrl": "/sq-rAL/" + "relUrl": "/es-rES/" },"2274": { - "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" - },"2275": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#map-view", - - "relUrl": "/is-rIS/user/map-and-waypoints.html#map-view" - },"2276": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#waypoints", - - "relUrl": "/is-rIS/user/map-and-waypoints.html#waypoints" - },"2277": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#map-layers", - - "relUrl": "/is-rIS/user/map-and-waypoints.html#map-layers" - },"2278": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/is-rIS/user/map-and-waypoints.html#position-sharing" - },"2279": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#map-sources", - - "relUrl": "/is-rIS/user/map-and-waypoints.html#map-sources" - },"2280": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2281": { - "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" - },"2282": { - "doc": "マップとウェイポイント", - "title": "マップとウェイポイント", - "content": "マップ画面には、メッシュ上のノードの地理的な位置が、共有されたウェイポイントとともに表示されます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/map-and-waypoints.html", - - "relUrl": "/ja-rJP/user/map-and-waypoints.html" - },"2283": { - "doc": "マップとウェイポイント", - "title": "マップビュー", - "content": "マップには次のものが表示されます： . | ノードの位置： 位置を報告している各ノードの色付きマーカー | ウェイポイント： 共有された注目地点 | 自分の位置： 現在の GPS 位置 | . ノードのマーカー . 位置を報告している各ノードは、そのノードの短縮名を表示するノードチップマーカーとして表示されます。 チップは、そのノード固有のアイデンティティカラー（ノード番号から導かれる一定の色）で色付けされます。ノードリストで使われるのと同じチップなので、どこでも同じ見た目になります。 マーカーの色は、オンライン／オフラインの状態を表しません。 ノードの位置がライブで更新されると、そのマーカーが短く脈打つように点滅します。 縮小すると、近くのマーカーはまとめて表示（クラスタリング）されます。 . マップの操作 . | ズーム： ピンチ操作、または +/− ボタンを使います | 移動： ドラッグして見て回ります | 中央に配置： 位置ボタンを選ぶと、自分の位置を中央に表示します | ノードのタップ： ノードのマーカーをタップすると詳細を表示します | . フローティングツールバーから、コンパス、レイヤーの切り替え、ノードの絞り込み、更新、位置追跡にすばやくアクセスできます。 コンパスをタップすると北を上に向け直し、位置ボタンをタップすると現在の位置を中央に表示します。 . ", - "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#マップビュー" - },"2284": { - "doc": "マップとウェイポイント", - "title": "ウェイポイント", - "content": "ウェイポイントは、メッシュの全メンバーが見られる、共有された地理的な注目地点です。 . ウェイポイントを作成する . | マップ上の目的の場所を長押しします。 | 名前と、任意で説明を入力します。 | ウェイポイントのアイコン／絵文字を選びます。 | 「送信」をタップしてメッシュに共有します。 | . ウェイポイントはメッセージと同じように宛先を指定します。既定ではプライマリチャンネルにブロードキャストされますが、特定のチャンネルに送ったり、単一のノードへのダイレクトメッセージとして送ったりすることもできます。 . ウェイポイントのプロパティ . | プロパティ | 説明 | . | 名前 | 短い識別子（最大 29 文字） | . | 説明 | 任意の、より詳しい説明 | . | アイコン | マップ上の視覚的なマーカー絵文字 | . | ロック済み | ロックすると、作成者だけが編集・削除できます | . | 有効期限 | 任意の、自動削除する日時 | . | ジオフェンス | 任意の、進入／退出を通知するエリア。詳しくは後述します | . ウェイポイントの有効期限 . ウェイポイントは、自動的に期限切れになるよう設定できます： . | なし（デフォルト）：手動で削除するまでウェイポイントは残ります | 期限付き：特定の日時を指定します。その時刻を過ぎると、ウェイポイントは自動的に削除されます。 集合地点、危険箇所、待ち合わせ場所などの一時的なマーカーに便利です。 | . 期限切れのウェイポイントは、表示が煩雑にならないよう、自動的にマップから隠されます。 有効期限のカウントダウンは、指定した絶対時刻を基準とし、ウェイポイントが作成または受信されてからの経過時間ではありません。 . ウェイポイントのジオフェンス . どのウェイポイントにもジオフェンス（通知エリア）を設定できます。これにより、ノードがそのエリアに進入または退出したときに、あなたや他のメンバーに通知が届きます： . | プリセットのチップからジオフェンスの半径を設定する（無効にするにはオフ）か、「マップ上でエリアを設定」をタップして、任意の四角形のエリアを描画します。 | エリアを設定したら、「進入時に通知」や「退出時に通知」を切り替えます。 | 任意で「お気に入りのみ」を有効にすると、通知をお気に入りのノードに限定できます。 | . ウェイポイント（およびそのジオフェンス）はメッシュ全体にブロードキャストされるため、デフォルトでは作成者だけに通知されます。 他の人がジオフェンス付きのウェイポイントを共有した場合、その詳細ビューに「通過を通知する」というオプトインが表示され、あなたも進入／退出の通知を受け取れます。 . ウェイポイントを管理する . | マップ上のウェイポイントをタップすると、その詳細と座標を表示します | 自分が作成したウェイポイントを編集または削除できます | ロックされたウェイポイントは、他のノードから変更・削除できません。元の作成者だけが変更できます | ロックされていないウェイポイントは、どのメッシュメンバーでも編集できます | . ", - "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#ウェイポイント" - },"2285": { - "doc": "マップとウェイポイント", - "title": "マップレイヤー", - "content": "マップのレイヤーアイコンをタップすると「マップレイヤーの管理」が開き、.kml、.kmz、または GeoJSON 形式の独自のオーバーレイをインポートできます。Meshtastic でファイルを開くか、別のアプリからアプリに共有することでインポートします。 インポートしたレイヤーは、それぞれ表示／非表示を切り替えるトグルと、削除するオプションとともに一覧表示されます。 これは Google Play 版と F-Droid 版の両方で利用できます。 . サイトプランナー . サイトプランナーは、送信機の RF カバレッジを推定し、色分けされたオーバーレイとしてマップに描画します。 マップの操作から開くか、ノードの詳細ページから「カバレッジを推定」で開きます（位置が判明しているノードでのみ表示されます）。 送信機（位置、周波数、送信出力、アンテナ利得と高さ）、受信機（感度、高さ）、シミュレーションのオプション（最大範囲、高解像度の地形、カラーパレット）を設定してから、推定を実行します。 マップレイヤーと同様に、サイトプランナーも Google Play 版と F-Droid 版の両方で動作します。 . ", - "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#マップレイヤー" - },"2286": { - "doc": "マップとウェイポイント", - "title": "位置の共有", - "content": "位置の共有を有効にする . ノードは、次のいずれかに基づいて GPS 位置を共有します： . | 固定間隔： 一定間隔で位置をブロードキャストします | スマート位置： 移動がしきい値を超えたときにブロードキャストします | 手動： 明示的に要求されたときのみ共有します | . 位置の動作は「設定 → 位置」で設定します。 . プライバシーに関する注意 . 🔒 プライバシー： 位置データは、チャンネル上のすべてのノードにブロードキャストされます。 位置を共有したくない場合は、設定で GPS 位置を無効にするか、固定／ダミーの位置を使用してください。 . ", - "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#位置の共有" - },"2287": { - "doc": "マップとウェイポイント", - "title": "マップソース", - "content": "ベースマップはアプリの版によって異なります。Google Play 版は Google マップを、F-Droid 版とデスクトップ版は OpenStreetMap を使用します。 ベースマップの上に、オーバーレイまたは代替として、追加のタイルソースを利用できます： . | 衛星画像（利用可能な場合） | オフラインタイル（オフラインで使うためにマップのエリアをダウンロード） | . ", - "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#マップソース" - },"2288": { - "doc": "マップとウェイポイント", - "title": "関連トピック", - "content": ". | ノード：ノードリストの表示と絞り込み | ノードメトリクス：各ノードの信号品質と位置履歴 | 探索：メッシュのトポロジーを把握するためのルート追跡と隣接ノード情報 | 単位とロケール：距離と座標の表示形式 | . ", - "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#関連トピック" - },"2289": { - "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" - },"2290": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#map-view", - - "relUrl": "/ca-rES/user/map-and-waypoints.html#map-view" - },"2291": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#waypoints", - - "relUrl": "/ca-rES/user/map-and-waypoints.html#waypoints" - },"2292": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#map-layers", - - "relUrl": "/ca-rES/user/map-and-waypoints.html#map-layers" - },"2293": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/ca-rES/user/map-and-waypoints.html#position-sharing" - },"2294": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#map-sources", - - "relUrl": "/ca-rES/user/map-and-waypoints.html#map-sources" - },"2295": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2296": { - "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" - },"2297": { - "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" - },"2298": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#map-view", - - "relUrl": "/sr-rLatn/user/map-and-waypoints.html#map-view" - },"2299": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#waypoints", - - "relUrl": "/sr-rLatn/user/map-and-waypoints.html#waypoints" - },"2300": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#map-layers", - - "relUrl": "/sr-rLatn/user/map-and-waypoints.html#map-layers" - },"2301": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/sr-rLatn/user/map-and-waypoints.html#position-sharing" - },"2302": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#map-sources", - - "relUrl": "/sr-rLatn/user/map-and-waypoints.html#map-sources" - },"2303": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2304": { - "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" - },"2305": { - "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" - },"2306": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#map-view", - - "relUrl": "/ko-rKR/user/map-and-waypoints.html#map-view" - },"2307": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#waypoints", - - "relUrl": "/ko-rKR/user/map-and-waypoints.html#waypoints" - },"2308": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#map-layers", - - "relUrl": "/ko-rKR/user/map-and-waypoints.html#map-layers" - },"2309": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/ko-rKR/user/map-and-waypoints.html#position-sharing" - },"2310": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#map-sources", - - "relUrl": "/ko-rKR/user/map-and-waypoints.html#map-sources" - },"2311": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2312": { - "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" - },"2313": { - "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" - },"2314": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#map-view", - - "relUrl": "/ro-rRO/user/map-and-waypoints.html#map-view" - },"2315": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#waypoints", - - "relUrl": "/ro-rRO/user/map-and-waypoints.html#waypoints" - },"2316": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#map-layers", - - "relUrl": "/ro-rRO/user/map-and-waypoints.html#map-layers" - },"2317": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/ro-rRO/user/map-and-waypoints.html#position-sharing" - },"2318": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#map-sources", - - "relUrl": "/ro-rRO/user/map-and-waypoints.html#map-sources" - },"2319": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2320": { - "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" - },"2321": { - "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" - },"2322": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#map-view", - - "relUrl": "/ga-rIE/user/map-and-waypoints.html#map-view" - },"2323": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#waypoints", - - "relUrl": "/ga-rIE/user/map-and-waypoints.html#waypoints" - },"2324": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#map-layers", - - "relUrl": "/ga-rIE/user/map-and-waypoints.html#map-layers" - },"2325": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/ga-rIE/user/map-and-waypoints.html#position-sharing" - },"2326": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#map-sources", - - "relUrl": "/ga-rIE/user/map-and-waypoints.html#map-sources" - },"2327": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2328": { - "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" - },"2329": { - "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" - },"2330": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#map-view", - - "relUrl": "/iw-rIL/user/map-and-waypoints.html#map-view" - },"2331": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#waypoints", - - "relUrl": "/iw-rIL/user/map-and-waypoints.html#waypoints" - },"2332": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#map-layers", - - "relUrl": "/iw-rIL/user/map-and-waypoints.html#map-layers" - },"2333": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/iw-rIL/user/map-and-waypoints.html#position-sharing" - },"2334": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#map-sources", - - "relUrl": "/iw-rIL/user/map-and-waypoints.html#map-sources" - },"2335": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2336": { - "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" - },"2337": { - "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" - },"2338": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#map-view", - - "relUrl": "/sv-rSE/user/map-and-waypoints.html#map-view" - },"2339": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#waypoints", - - "relUrl": "/sv-rSE/user/map-and-waypoints.html#waypoints" - },"2340": { - "doc": "Map & Waypoints", - "title": "Kartlager", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#kartlager", - - "relUrl": "/sv-rSE/user/map-and-waypoints.html#kartlager" - },"2341": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/sv-rSE/user/map-and-waypoints.html#position-sharing" - },"2342": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#map-sources", - - "relUrl": "/sv-rSE/user/map-and-waypoints.html#map-sources" - },"2343": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2344": { - "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" - },"2345": { - "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" - },"2346": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#map-view", - - "relUrl": "/ht-rHT/user/map-and-waypoints.html#map-view" - },"2347": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#waypoints", - - "relUrl": "/ht-rHT/user/map-and-waypoints.html#waypoints" - },"2348": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#map-layers", - - "relUrl": "/ht-rHT/user/map-and-waypoints.html#map-layers" - },"2349": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/ht-rHT/user/map-and-waypoints.html#position-sharing" - },"2350": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#map-sources", - - "relUrl": "/ht-rHT/user/map-and-waypoints.html#map-sources" - },"2351": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2352": { - "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" - },"2353": { - "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" - },"2354": { - "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ä — valitse sijaintipainike keskittääksesi oman sijaintisi | Radion napautus — avaa radion tiedot napauttamalla merkkiä | . Kelluva työkalupalkki tarjoaa nopean pääsyn kompassiin, tasojen vaihtoon, suodattimiin, päivitykseen ja sijainnin seurantaan. Napauta kompassia suunnan palauttamiseksi pohjoiseen tai sijaintipainiketta keskittääksesi oman sijaintisi. ", - "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ä" - },"2355": { - "doc": "Kartta ja reittipisteet", - "title": "Reittipisteet", - "content": "Reittipisteet ovat jaettuja maantieteellisiä kiinnostavia kohteita, jotka kaikki mesh-verkon jäsenet voivat nähdä. Reittipisteen luominen . | Paina karttaa pitkään haluamassasi sijainnissa. | Anna nimi ja valinnainen kuvaus. | Valitse reittipisteelle kuvake tai emoji. | Napauta Lähetä jakaaksesi sen verkkoon. | . Reittipisteet osoitetaan kuten viestit: oletuksena ne lähetetään yleislähetyksenä ensisijaisella kanavalla, mutta reittipiste voidaan lähettää myös tietyllä kanavalla tai suoraviestinä yhdelle radiolle. 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 aluerajaus saapumis- ja poistumisilmoituksille — katso alla | . 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. Jos joku jakaa kanssasi aluerajauksen sisältävän reittipisteen, sen tiedoissa voit ottaa käyttöön Ilmoita aluerajan ylityksistä -asetuksen, jolloin saat myös ilmoitukset alueelle saapumisesta ja sieltä poistumisesta. Reittipisteiden hallinta . | Napauta reittipistettä kartalla nähdäksesi sen tiedot ja koordinaatit | Muokkaa tai poista luomiasi reittipisteitä | Lukitut reittipisteet eivät ole muiden radioiden muokattavissa tai poistettavissa — vain alkuperäisen merkin luonut voi muuttaa niitä | Lukitsemattomia reittipisteitä voi muokata kuka tahansa mesh-verkon jäsen | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#reittipisteet", - - "relUrl": "/fi-rFI/user/map-and-waypoints.html#reittipisteet" - },"2356": { - "doc": "Kartta ja reittipisteet", - "title": "Karttatasot", - "content": "Napauta kartan karttatasokuvaketta avataksesi Hallitse karttatasoja -näkymän, jossa voit tuoda omia karttatasojasi .kml-, .kmz- tai GeoJSON-muodossa joko avaamalla tiedoston Meshtasticissa tai jakamalla sen sovellukseen toisesta sovelluksesta. Tuodut karttatasot näkyvät luettelossa, jossa voit näyttää tai piilottaa ne sekä poistaa ne. Tämä on käytettävissä sekä Google Play- että F-Droid-versioissa. 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. Karttatasojen tavoin myös Site Planner on käytettävissä sekä Google Play- että F-Droid-versioissa. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#karttatasot", - - "relUrl": "/fi-rFI/user/map-and-waypoints.html#karttatasot" - },"2357": { - "doc": "Kartta ja reittipisteet", - "title": "Sijainnin jakaminen", - "content": "Sijainnin jakamisen käyttöönotto . Radiosi jakaa GPS-sijaintinsa seuraavilla tavoilla: . | Kiinteä väli — sijainti lähetetään säännöllisin väliajoin | Älykäs sijainti — sijainti lähetetään, kun liike ylittää kynnyksen | Manuaalinen — sijainti jaetaan vain erikseen pyydettäessä | . Määritä sijaintikäyttäytyminen kohdassa Asetukset → Sijainti. 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. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#sijainnin-jakaminen", - - "relUrl": "/fi-rFI/user/map-and-waypoints.html#sijainnin-jakaminen" - },"2358": { - "doc": "Kartta ja reittipisteet", - "title": "Karttalähteet", - "content": "Kartan pohja riippuu sovellusversiosta: Google Play -versio käyttää Google Mapsia, kun taas F-Droid- ja työpöytäversiot käyttävät OpenStreetMapia. Pohjakartan lisäksi käytettävissä on muita karttatasoja peitekerroksina tai vaihtoehtoisina karttoina: . | Satelliittikuvat (jos saatavilla) | Offline-kartat (lataa alueet offline-käyttöä varten) | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#karttal%C3%A4hteet", - - "relUrl": "/fi-rFI/user/map-and-waypoints.html#karttalähteet" - },"2359": { - "doc": "Kartta ja reittipisteet", - "title": "Aiheeseen liittyvät aiheet", - "content": ". | Radiot — tarkastele ja suodata radiolistaa | Radion mittarit — signaalin laatu ja sijaintihistoria yksittäisille radioille | Haku — reitinselvitys ja naapuritiedot mesh-verkon ymmärtämiseen | 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" - },"2360": { - "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" - },"2361": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#map-view", - - "relUrl": "/gl-rES/user/map-and-waypoints.html#map-view" - },"2362": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#waypoints", - - "relUrl": "/gl-rES/user/map-and-waypoints.html#waypoints" - },"2363": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#map-layers", - - "relUrl": "/gl-rES/user/map-and-waypoints.html#map-layers" - },"2364": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/gl-rES/user/map-and-waypoints.html#position-sharing" - },"2365": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#map-sources", - - "relUrl": "/gl-rES/user/map-and-waypoints.html#map-sources" - },"2366": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2367": { - "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" - },"2368": { - "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" - },"2369": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#map-view", - - "relUrl": "/uk-rUA/user/map-and-waypoints.html#map-view" - },"2370": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#waypoints", - - "relUrl": "/uk-rUA/user/map-and-waypoints.html#waypoints" - },"2371": { - "doc": "Map & Waypoints", - "title": "Шари мапи", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "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#шари-мапи" - },"2372": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/uk-rUA/user/map-and-waypoints.html#position-sharing" - },"2373": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#map-sources", - - "relUrl": "/uk-rUA/user/map-and-waypoints.html#map-sources" - },"2374": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2375": { - "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" - },"2376": { "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" - },"2377": { + },"2275": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#map-view", "relUrl": "/de-rDE/user/map-and-waypoints.html#map-view" - },"2378": { + },"2276": { "doc": "Map & Waypoints", "title": "Waypoints", "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#waypoints", "relUrl": "/de-rDE/user/map-and-waypoints.html#waypoints" - },"2379": { + },"2277": { "doc": "Map & Waypoints", "title": "Kartenebenen", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#kartenebenen", "relUrl": "/de-rDE/user/map-and-waypoints.html#kartenebenen" - },"2380": { + },"2278": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#position-sharing", "relUrl": "/de-rDE/user/map-and-waypoints.html#position-sharing" - },"2381": { + },"2279": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#map-sources", "relUrl": "/de-rDE/user/map-and-waypoints.html#map-sources" - },"2382": { + },"2280": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2383": { + },"2281": { "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" - },"2384": { + },"2282": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/hr-rHR/user/map-and-waypoints.html#map--waypoints" - },"2385": { + "relUrl": "/ca-rES/user/map-and-waypoints.html#map--waypoints" + },"2283": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#map-view", - "relUrl": "/hr-rHR/user/map-and-waypoints.html#map-view" - },"2386": { + "relUrl": "/ca-rES/user/map-and-waypoints.html#map-view" + },"2284": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#waypoints", - "relUrl": "/hr-rHR/user/map-and-waypoints.html#waypoints" - },"2387": { + "relUrl": "/ca-rES/user/map-and-waypoints.html#waypoints" + },"2285": { "doc": "Map & Waypoints", "title": "Map Layers", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#map-layers", + "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#map-layers", - "relUrl": "/hr-rHR/user/map-and-waypoints.html#map-layers" - },"2388": { + "relUrl": "/ca-rES/user/map-and-waypoints.html#map-layers" + },"2286": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#position-sharing", - "relUrl": "/hr-rHR/user/map-and-waypoints.html#position-sharing" - },"2389": { + "relUrl": "/ca-rES/user/map-and-waypoints.html#position-sharing" + },"2287": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#map-sources", - "relUrl": "/hr-rHR/user/map-and-waypoints.html#map-sources" - },"2390": { + "relUrl": "/ca-rES/user/map-and-waypoints.html#map-sources" + },"2288": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#related-topics", - "relUrl": "/hr-rHR/user/map-and-waypoints.html#related-topics" - },"2391": { + "relUrl": "/ca-rES/user/map-and-waypoints.html#related-topics" + },"2289": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html", - "relUrl": "/hr-rHR/user/map-and-waypoints.html" - },"2392": { - "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" - },"2393": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#map-view", - - "relUrl": "/lt-rLT/user/map-and-waypoints.html#map-view" - },"2394": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#waypoints", - - "relUrl": "/lt-rLT/user/map-and-waypoints.html#waypoints" - },"2395": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#map-layers", - - "relUrl": "/lt-rLT/user/map-and-waypoints.html#map-layers" - },"2396": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/lt-rLT/user/map-and-waypoints.html#position-sharing" - },"2397": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#map-sources", - - "relUrl": "/lt-rLT/user/map-and-waypoints.html#map-sources" - },"2398": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2399": { - "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" - },"2400": { - "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" - },"2401": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#map-view", - - "relUrl": "/en/user/map-and-waypoints.html#map-view" - },"2402": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#waypoints", - - "relUrl": "/en/user/map-and-waypoints.html#waypoints" - },"2403": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#map-layers", - - "relUrl": "/en/user/map-and-waypoints.html#map-layers" - },"2404": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/en/user/map-and-waypoints.html#position-sharing" - },"2405": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#map-sources", - - "relUrl": "/en/user/map-and-waypoints.html#map-sources" - },"2406": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2407": { - "doc": "Map & Waypoints", - "title": "Map & Waypoints", - "content": " ", - "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html", - - "relUrl": "/en/user/map-and-waypoints.html" - },"2408": { - "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" - },"2409": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#map-view", - - "relUrl": "/hu-rHU/user/map-and-waypoints.html#map-view" - },"2410": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#waypoints", - - "relUrl": "/hu-rHU/user/map-and-waypoints.html#waypoints" - },"2411": { - "doc": "Map & Waypoints", - "title": "Térképrétegek", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "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" - },"2412": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/hu-rHU/user/map-and-waypoints.html#position-sharing" - },"2413": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#map-sources", - - "relUrl": "/hu-rHU/user/map-and-waypoints.html#map-sources" - },"2414": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2415": { - "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" - },"2416": { - "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" - },"2417": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#map-view", - - "relUrl": "/bg-rBG/user/map-and-waypoints.html#map-view" - },"2418": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#waypoints", - - "relUrl": "/bg-rBG/user/map-and-waypoints.html#waypoints" - },"2419": { - "doc": "Map & Waypoints", - "title": "Слоеве на картата", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "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#слоеве-на-картата" - },"2420": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/bg-rBG/user/map-and-waypoints.html#position-sharing" - },"2421": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#map-sources", - - "relUrl": "/bg-rBG/user/map-and-waypoints.html#map-sources" - },"2422": { - "doc": "Map & Waypoints", - "title": "Свързани теми", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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#свързани-теми" - },"2423": { - "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" - },"2424": { - "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" - },"2425": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#map-view", - - "relUrl": "/sl-rSI/user/map-and-waypoints.html#map-view" - },"2426": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#waypoints", - - "relUrl": "/sl-rSI/user/map-and-waypoints.html#waypoints" - },"2427": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#map-layers", - - "relUrl": "/sl-rSI/user/map-and-waypoints.html#map-layers" - },"2428": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/sl-rSI/user/map-and-waypoints.html#position-sharing" - },"2429": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#map-sources", - - "relUrl": "/sl-rSI/user/map-and-waypoints.html#map-sources" - },"2430": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2431": { - "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" - },"2432": { - "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" - },"2433": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#map-view", - - "relUrl": "/pt-rPT/user/map-and-waypoints.html#map-view" - },"2434": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#waypoints", - - "relUrl": "/pt-rPT/user/map-and-waypoints.html#waypoints" - },"2435": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#map-layers", - - "relUrl": "/pt-rPT/user/map-and-waypoints.html#map-layers" - },"2436": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/pt-rPT/user/map-and-waypoints.html#position-sharing" - },"2437": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#map-sources", - - "relUrl": "/pt-rPT/user/map-and-waypoints.html#map-sources" - },"2438": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2439": { - "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" - },"2440": { + "relUrl": "/ca-rES/user/map-and-waypoints.html" + },"2290": { "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" - },"2441": { + },"2291": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#map-view", "relUrl": "/be-rBY/user/map-and-waypoints.html#map-view" - },"2442": { + },"2292": { "doc": "Map & Waypoints", "title": "Waypoints", "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#waypoints", "relUrl": "/be-rBY/user/map-and-waypoints.html#waypoints" - },"2443": { + },"2293": { "doc": "Map & Waypoints", "title": "Map Layers", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#map-layers", "relUrl": "/be-rBY/user/map-and-waypoints.html#map-layers" - },"2444": { + },"2294": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#position-sharing", "relUrl": "/be-rBY/user/map-and-waypoints.html#position-sharing" - },"2445": { + },"2295": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#map-sources", "relUrl": "/be-rBY/user/map-and-waypoints.html#map-sources" - },"2446": { + },"2296": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2447": { + },"2297": { "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" - },"2448": { + },"2298": { + "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" + },"2299": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#map-view", + + "relUrl": "/uk-rUA/user/map-and-waypoints.html#map-view" + },"2300": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#waypoints", + + "relUrl": "/uk-rUA/user/map-and-waypoints.html#waypoints" + },"2301": { + "doc": "Map & Waypoints", + "title": "Шари мапи", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "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#шари-мапи" + },"2302": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/uk-rUA/user/map-and-waypoints.html#position-sharing" + },"2303": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#map-sources", + + "relUrl": "/uk-rUA/user/map-and-waypoints.html#map-sources" + },"2304": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2305": { + "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" + },"2306": { + "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" + },"2307": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#map-view", + + "relUrl": "/zh-rCN/user/map-and-waypoints.html#map-view" + },"2308": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#waypoints", + + "relUrl": "/zh-rCN/user/map-and-waypoints.html#waypoints" + },"2309": { + "doc": "Map & Waypoints", + "title": "地图图层", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "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#地图图层" + },"2310": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/zh-rCN/user/map-and-waypoints.html#position-sharing" + },"2311": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#map-sources", + + "relUrl": "/zh-rCN/user/map-and-waypoints.html#map-sources" + },"2312": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2313": { + "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" + },"2314": { + "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" + },"2315": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#map-view", + + "relUrl": "/bg-rBG/user/map-and-waypoints.html#map-view" + },"2316": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#waypoints", + + "relUrl": "/bg-rBG/user/map-and-waypoints.html#waypoints" + },"2317": { + "doc": "Map & Waypoints", + "title": "Слоеве на картата", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "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#слоеве-на-картата" + },"2318": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/bg-rBG/user/map-and-waypoints.html#position-sharing" + },"2319": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#map-sources", + + "relUrl": "/bg-rBG/user/map-and-waypoints.html#map-sources" + },"2320": { + "doc": "Map & Waypoints", + "title": "Свързани теми", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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#свързани-теми" + },"2321": { + "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" + },"2322": { + "doc": "地圖與航點", + "title": "地圖與航點", + "content": "地圖畫面顯示 mesh 網路上各節點的地理位置，以及已分享的航點。 . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html", + + "relUrl": "/zh-rTW/user/map-and-waypoints.html" + },"2323": { + "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. 地圖控制項 . | 縮放 — 雙指縮放或使用 +/- 按鈕 | 平移 — 拖曳以瀏覽地圖 | 置中 — 點選位置按鈕，使地圖以您的位置為中心 | 點選節點 — 點選節點標記以檢視詳細資訊 | . 浮動工具列提供快速存取羅盤、圖層切換、節點篩選、重新整理及位置追蹤等功能。 點選羅盤可重新對齊正北方向，或點選位置按鈕使地圖以您目前位置為中心。 . ", + "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#地圖檢視" + },"2324": { + "doc": "地圖與航點", + "title": "航點", + "content": "航點是可分享的地理興趣點，mesh 網路上的所有成員均可看見。 . 建立航點 . | 在地圖上的目標位置長按。 | 輸入名稱及選填的說明。 | 為航點選擇圖示或表情符號。 | 點選「傳送」以分享至 mesh 網路。 | . Waypoints are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 航點屬性 . | 屬性 | 描述說明 | . | 名稱 | Short identifier (max 29 characters) | . | 描述說明 | 選填的較長說明 | . | 圖示 | 地圖上的視覺標記表情符號 | . | 鎖定 | 若已鎖定，僅建立者可編輯或刪除 | . | 到期時間 | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see below | . 航點到期設定 . 航點可設定為自動到期： . | 永不到期（預設）— 航點將保留至手動刪除為止 | 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. 管理航點 . | 點選地圖上的航點，可檢視其詳細資訊與座標 | 編輯或刪除您建立的航點 | 已鎖定的航點無法被其他節點修改或刪除 — 僅原始建立者可進行變更 | 未鎖定的航點可由任何 mesh 成員編輯 | . ", + "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#航點" + },"2325": { + "doc": "地圖與航點", + "title": "地圖圖層", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "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#地圖圖層" + },"2326": { + "doc": "地圖與航點", + "title": "位置分享", + "content": "啟用位置分享 . 您的節點依據以下方式分享 GPS 位置： . | 固定間隔 — 依固定時間間隔廣播位置 | 智慧位置 — 移動距離超過閾值時才廣播位置 | 手動 — 僅在明確要求時才分享位置 | . 請在「設定 → 位置」中設定位置行為。 . 隱私注意事項 . 🔒 隱私：位置資料將廣播至您頻道上的所有節點。 若不想分享您的位置，請在設定中停用 GPS 定位，或使用固定／假位置。 . ", + "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#位置分享" + },"2327": { + "doc": "地圖與航點", + "title": "地圖來源", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | 衛星影像（視可用性而定） | 離線圖磚（下載地圖區域以供離線使用） | . ", + "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#地圖來源" + },"2328": { + "doc": "地圖與航點", + "title": "相關主題", + "content": ". | 〔節點〕(nodes) — 檢視與篩選您的節點清單 | 〔節點數據〕(node-metrics) — 各節點的訊號品質與位置歷史記錄 | 〔探索〕(discovery) — 路由追蹤與鄰近節點資訊，用於了解 mesh 網路拓撲 | 〔單位與地區設定〕(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#相關主題" + },"2329": { + "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" + },"2330": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#map-view", + + "relUrl": "/sr-rLatn/user/map-and-waypoints.html#map-view" + },"2331": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#waypoints", + + "relUrl": "/sr-rLatn/user/map-and-waypoints.html#waypoints" + },"2332": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#map-layers", + + "relUrl": "/sr-rLatn/user/map-and-waypoints.html#map-layers" + },"2333": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/sr-rLatn/user/map-and-waypoints.html#position-sharing" + },"2334": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#map-sources", + + "relUrl": "/sr-rLatn/user/map-and-waypoints.html#map-sources" + },"2335": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2336": { + "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" + },"2337": { + "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" + },"2338": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#map-view", + + "relUrl": "/cs-rCZ/user/map-and-waypoints.html#map-view" + },"2339": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#waypoints", + + "relUrl": "/cs-rCZ/user/map-and-waypoints.html#waypoints" + },"2340": { + "doc": "Map & Waypoints", + "title": "Mapové vrstvy", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "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" + },"2341": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/cs-rCZ/user/map-and-waypoints.html#position-sharing" + },"2342": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#map-sources", + + "relUrl": "/cs-rCZ/user/map-and-waypoints.html#map-sources" + },"2343": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2344": { + "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" + },"2345": { + "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" + },"2346": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#map-view", + + "relUrl": "/en/user/map-and-waypoints.html#map-view" + },"2347": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#waypoints", + + "relUrl": "/en/user/map-and-waypoints.html#waypoints" + },"2348": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#map-layers", + + "relUrl": "/en/user/map-and-waypoints.html#map-layers" + },"2349": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/en/user/map-and-waypoints.html#position-sharing" + },"2350": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#map-sources", + + "relUrl": "/en/user/map-and-waypoints.html#map-sources" + },"2351": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2352": { + "doc": "Map & Waypoints", + "title": "Map & Waypoints", + "content": " ", + "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html", + + "relUrl": "/en/user/map-and-waypoints.html" + },"2353": { + "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" + },"2354": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#map-view", + + "relUrl": "/sl-rSI/user/map-and-waypoints.html#map-view" + },"2355": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#waypoints", + + "relUrl": "/sl-rSI/user/map-and-waypoints.html#waypoints" + },"2356": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#map-layers", + + "relUrl": "/sl-rSI/user/map-and-waypoints.html#map-layers" + },"2357": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/sl-rSI/user/map-and-waypoints.html#position-sharing" + },"2358": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#map-sources", + + "relUrl": "/sl-rSI/user/map-and-waypoints.html#map-sources" + },"2359": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2360": { + "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" + },"2361": { + "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" + },"2362": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#map-view", + + "relUrl": "/it-rIT/user/map-and-waypoints.html#map-view" + },"2363": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#waypoints", + + "relUrl": "/it-rIT/user/map-and-waypoints.html#waypoints" + },"2364": { + "doc": "Map & Waypoints", + "title": "Livelli della mappa", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "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" + },"2365": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/it-rIT/user/map-and-waypoints.html#position-sharing" + },"2366": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#map-sources", + + "relUrl": "/it-rIT/user/map-and-waypoints.html#map-sources" + },"2367": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2368": { + "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" + },"2369": { "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" - },"2449": { + },"2370": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html#map-view", "relUrl": "/pt-rBR/user/map-and-waypoints.html#map-view" - },"2450": { + },"2371": { "doc": "Map & Waypoints", "title": "Waypoints", "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html#waypoints", "relUrl": "/pt-rBR/user/map-and-waypoints.html#waypoints" - },"2451": { + },"2372": { "doc": "Map & Waypoints", "title": "Camadas do Mapa", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", "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" - },"2452": { + },"2373": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html#position-sharing", "relUrl": "/pt-rBR/user/map-and-waypoints.html#position-sharing" - },"2453": { + },"2374": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html#map-sources", "relUrl": "/pt-rBR/user/map-and-waypoints.html#map-sources" - },"2454": { + },"2375": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2455": { + },"2376": { "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" - },"2456": { + },"2377": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/el-rGR/user/map-and-waypoints.html#map--waypoints" - },"2457": { + "relUrl": "/is-rIS/user/map-and-waypoints.html#map--waypoints" + },"2378": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#map-view", - "relUrl": "/el-rGR/user/map-and-waypoints.html#map-view" - },"2458": { + "relUrl": "/is-rIS/user/map-and-waypoints.html#map-view" + },"2379": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#waypoints", - "relUrl": "/el-rGR/user/map-and-waypoints.html#waypoints" - },"2459": { + "relUrl": "/is-rIS/user/map-and-waypoints.html#waypoints" + },"2380": { "doc": "Map & Waypoints", "title": "Map Layers", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#map-layers", + "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#map-layers", - "relUrl": "/el-rGR/user/map-and-waypoints.html#map-layers" - },"2460": { + "relUrl": "/is-rIS/user/map-and-waypoints.html#map-layers" + },"2381": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#position-sharing", - "relUrl": "/el-rGR/user/map-and-waypoints.html#position-sharing" - },"2461": { + "relUrl": "/is-rIS/user/map-and-waypoints.html#position-sharing" + },"2382": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#map-sources", - "relUrl": "/el-rGR/user/map-and-waypoints.html#map-sources" - },"2462": { + "relUrl": "/is-rIS/user/map-and-waypoints.html#map-sources" + },"2383": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#related-topics", - "relUrl": "/el-rGR/user/map-and-waypoints.html#related-topics" - },"2463": { + "relUrl": "/is-rIS/user/map-and-waypoints.html#related-topics" + },"2384": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html", - "relUrl": "/el-rGR/user/map-and-waypoints.html" - },"2464": { + "relUrl": "/is-rIS/user/map-and-waypoints.html" + },"2385": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/es-rES/user/map-and-waypoints.html#map--waypoints" - },"2465": { + "relUrl": "/fr-rFR/user/map-and-waypoints.html#map--waypoints" + },"2386": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#map-view", - "relUrl": "/es-rES/user/map-and-waypoints.html#map-view" - },"2466": { + "relUrl": "/fr-rFR/user/map-and-waypoints.html#map-view" + },"2387": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#waypoints", - "relUrl": "/es-rES/user/map-and-waypoints.html#waypoints" - },"2467": { + "relUrl": "/fr-rFR/user/map-and-waypoints.html#waypoints" + },"2388": { "doc": "Map & Waypoints", - "title": "Capas del mapa", + "title": "Couches cartographiques", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#capas-del-mapa", + "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#couches-cartographiques", - "relUrl": "/es-rES/user/map-and-waypoints.html#capas-del-mapa" - },"2468": { + "relUrl": "/fr-rFR/user/map-and-waypoints.html#couches-cartographiques" + },"2389": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#position-sharing", - "relUrl": "/es-rES/user/map-and-waypoints.html#position-sharing" - },"2469": { + "relUrl": "/fr-rFR/user/map-and-waypoints.html#position-sharing" + },"2390": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#map-sources", - "relUrl": "/es-rES/user/map-and-waypoints.html#map-sources" - },"2470": { + "relUrl": "/fr-rFR/user/map-and-waypoints.html#map-sources" + },"2391": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#related-topics", - "relUrl": "/es-rES/user/map-and-waypoints.html#related-topics" - },"2471": { + "relUrl": "/fr-rFR/user/map-and-waypoints.html#related-topics" + },"2392": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html", - "relUrl": "/es-rES/user/map-and-waypoints.html" - },"2472": { + "relUrl": "/fr-rFR/user/map-and-waypoints.html" + },"2393": { "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", + "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/tr-rTR/user/map-and-waypoints.html#map--waypoints" - },"2473": { + "relUrl": "/srp/user/map-and-waypoints.html#map--waypoints" + },"2394": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#map-view", - "relUrl": "/tr-rTR/user/map-and-waypoints.html#map-view" - },"2474": { + "relUrl": "/srp/user/map-and-waypoints.html#map-view" + },"2395": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#waypoints", - "relUrl": "/tr-rTR/user/map-and-waypoints.html#waypoints" - },"2475": { + "relUrl": "/srp/user/map-and-waypoints.html#waypoints" + },"2396": { "doc": "Map & Waypoints", "title": "Map Layers", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#map-layers", + "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#map-layers", - "relUrl": "/tr-rTR/user/map-and-waypoints.html#map-layers" - },"2476": { + "relUrl": "/srp/user/map-and-waypoints.html#map-layers" + },"2397": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#position-sharing", - "relUrl": "/tr-rTR/user/map-and-waypoints.html#position-sharing" - },"2477": { + "relUrl": "/srp/user/map-and-waypoints.html#position-sharing" + },"2398": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#map-sources", - "relUrl": "/tr-rTR/user/map-and-waypoints.html#map-sources" - },"2478": { + "relUrl": "/srp/user/map-and-waypoints.html#map-sources" + },"2399": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#related-topics", - "relUrl": "/tr-rTR/user/map-and-waypoints.html#related-topics" - },"2479": { + "relUrl": "/srp/user/map-and-waypoints.html#related-topics" + },"2400": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html", - "relUrl": "/tr-rTR/user/map-and-waypoints.html" - },"2480": { + "relUrl": "/srp/user/map-and-waypoints.html" + },"2401": { "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", + "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/no-rNO/user/map-and-waypoints.html#map--waypoints" - },"2481": { + "relUrl": "/sk-rSK/user/map-and-waypoints.html#map--waypoints" + },"2402": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#map-view", - "relUrl": "/no-rNO/user/map-and-waypoints.html#map-view" - },"2482": { + "relUrl": "/sk-rSK/user/map-and-waypoints.html#map-view" + },"2403": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#waypoints", - "relUrl": "/no-rNO/user/map-and-waypoints.html#waypoints" - },"2483": { + "relUrl": "/sk-rSK/user/map-and-waypoints.html#waypoints" + },"2404": { "doc": "Map & Waypoints", "title": "Map Layers", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#map-layers", + "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#map-layers", - "relUrl": "/no-rNO/user/map-and-waypoints.html#map-layers" - },"2484": { + "relUrl": "/sk-rSK/user/map-and-waypoints.html#map-layers" + },"2405": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#position-sharing", - "relUrl": "/no-rNO/user/map-and-waypoints.html#position-sharing" - },"2485": { + "relUrl": "/sk-rSK/user/map-and-waypoints.html#position-sharing" + },"2406": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#map-sources", - "relUrl": "/no-rNO/user/map-and-waypoints.html#map-sources" - },"2486": { + "relUrl": "/sk-rSK/user/map-and-waypoints.html#map-sources" + },"2407": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#related-topics", - "relUrl": "/no-rNO/user/map-and-waypoints.html#related-topics" - },"2487": { + "relUrl": "/sk-rSK/user/map-and-waypoints.html#related-topics" + },"2408": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html", - "relUrl": "/no-rNO/user/map-and-waypoints.html" - },"2488": { + "relUrl": "/sk-rSK/user/map-and-waypoints.html" + },"2409": { + "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" + },"2410": { + "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ä — valitse sijaintipainike keskittääksesi oman sijaintisi | Radion napautus — avaa radion tiedot napauttamalla merkkiä | . Kelluva työkalupalkki tarjoaa nopean pääsyn kompassiin, tasojen vaihtoon, suodattimiin, päivitykseen ja sijainnin seurantaan. Napauta kompassia suunnan palauttamiseksi pohjoiseen tai sijaintipainiketta keskittääksesi oman sijaintisi. ", + "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ä" + },"2411": { + "doc": "Kartta ja reittipisteet", + "title": "Reittipisteet", + "content": "Reittipisteet ovat jaettuja maantieteellisiä kiinnostavia kohteita, jotka kaikki mesh-verkon jäsenet voivat nähdä. Reittipisteen luominen . | Paina karttaa pitkään haluamassasi sijainnissa. | Anna nimi ja valinnainen kuvaus. | Valitse reittipisteelle kuvake tai emoji. | Napauta Lähetä jakaaksesi sen verkkoon. | . Reittipisteet osoitetaan kuten viestit: oletuksena ne lähetetään yleislähetyksenä ensisijaisella kanavalla, mutta reittipiste voidaan lähettää myös tietyllä kanavalla tai suoraviestinä yhdelle radiolle. 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 aluerajaus saapumis- ja poistumisilmoituksille — katso alla | . 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. Jos joku jakaa kanssasi aluerajauksen sisältävän reittipisteen, sen tiedoissa voit ottaa käyttöön Ilmoita aluerajan ylityksistä -asetuksen, jolloin saat myös ilmoitukset alueelle saapumisesta ja sieltä poistumisesta. Reittipisteiden hallinta . | Napauta reittipistettä kartalla nähdäksesi sen tiedot ja koordinaatit | Muokkaa tai poista luomiasi reittipisteitä | Lukitut reittipisteet eivät ole muiden radioiden muokattavissa tai poistettavissa — vain alkuperäisen merkin luonut voi muuttaa niitä | Lukitsemattomia reittipisteitä voi muokata kuka tahansa mesh-verkon jäsen | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#reittipisteet", + + "relUrl": "/fi-rFI/user/map-and-waypoints.html#reittipisteet" + },"2412": { + "doc": "Kartta ja reittipisteet", + "title": "Karttatasot", + "content": "Napauta kartan karttatasokuvaketta avataksesi Hallitse karttatasoja -näkymän, jossa voit tuoda omia karttatasojasi .kml-, .kmz- tai GeoJSON-muodossa joko avaamalla tiedoston Meshtasticissa tai jakamalla sen sovellukseen toisesta sovelluksesta. Tuodut karttatasot näkyvät luettelossa, jossa voit näyttää tai piilottaa ne sekä poistaa ne. Tämä on käytettävissä sekä Google Play- että F-Droid-versioissa. 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. Karttatasojen tavoin myös Site Planner on käytettävissä sekä Google Play- että F-Droid-versioissa. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#karttatasot", + + "relUrl": "/fi-rFI/user/map-and-waypoints.html#karttatasot" + },"2413": { + "doc": "Kartta ja reittipisteet", + "title": "Sijainnin jakaminen", + "content": "Sijainnin jakamisen käyttöönotto . Radiosi jakaa GPS-sijaintinsa seuraavilla tavoilla: . | Kiinteä väli — sijainti lähetetään säännöllisin väliajoin | Älykäs sijainti — sijainti lähetetään, kun liike ylittää kynnyksen | Manuaalinen — sijainti jaetaan vain erikseen pyydettäessä | . Määritä sijaintikäyttäytyminen kohdassa Asetukset → Sijainti. 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. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#sijainnin-jakaminen", + + "relUrl": "/fi-rFI/user/map-and-waypoints.html#sijainnin-jakaminen" + },"2414": { + "doc": "Kartta ja reittipisteet", + "title": "Karttalähteet", + "content": "Kartan pohja riippuu sovellusversiosta: Google Play -versio käyttää Google Mapsia, kun taas F-Droid- ja työpöytäversiot käyttävät OpenStreetMapia. Pohjakartan lisäksi käytettävissä on muita karttatasoja peitekerroksina tai vaihtoehtoisina karttoina: . | Satelliittikuvat (jos saatavilla) | Offline-kartat (lataa alueet offline-käyttöä varten) | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#karttal%C3%A4hteet", + + "relUrl": "/fi-rFI/user/map-and-waypoints.html#karttalähteet" + },"2415": { + "doc": "Kartta ja reittipisteet", + "title": "Aiheeseen liittyvät aiheet", + "content": ". | Radiot — tarkastele ja suodata radiolistaa | Radion mittarit — signaalin laatu ja sijaintihistoria yksittäisille radioille | Haku — reitinselvitys ja naapuritiedot mesh-verkon ymmärtämiseen | 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" + },"2416": { "doc": "Карта и путевые точки", "title": "Карта и путевые точки", "content": "Экран карты показывает географическое положение нод твоей mesh-сети, а также общие путевые точки. ", "url": "/Meshtastic-Android/main/ru-rRU/user/map-and-waypoints.html", "relUrl": "/ru-rRU/user/map-and-waypoints.html" - },"2489": { + },"2417": { "doc": "Карта и путевые точки", "title": "Вид карты", "content": "На карте отображаются: . | Расположение нод — цветные маркеры для каждой ноды, передающей свои координаты | Путевые точки — общие точки интереса | Твоё местоположение — твоё текущее местоположение по GPS | . Маркеры нод . Каждая нода, передающая своё местоположение, отображается в виде маркера-бирки с коротким именем ноды. Цвет бирки определяется собственным цветом идентификации ноды (постоянным цветом, получаемым из её номера) — тем же самым, что используется в списке нод, поэтому нода везде выглядит одинаково. Цвет маркера не отображает статус в сети/не в сети. Когда местоположение ноды обновляется в реальном времени, её маркер ненадолго подсвечивается пульсацией. Близко расположенные маркеры группируются в кластеры при уменьшении масштаба. Управление картой . | Масштаб — используйте щипок или кнопки +/- | Перемещение — перетаскивайте карту для исследования | Центрирование — нажмите кнопку местоположения, чтобы отцентрировать карту на твоё местоположение | Нажатие на ноду — коснитесь маркера ноды для просмотра подробностей | . Плавающая панель инструментов предоставляет быстрый доступ к компасу, переключению слоёв, фильтрам нод, обновлению и отслеживанию местоположения. Нажмите на компас, чтобы сориентировать карту на север, или нажмите кнопку местоположения, чтобы отцентрироваться на твоей текущей позиции. ", "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#вид-карты" - },"2490": { + },"2418": { "doc": "Карта и путевые точки", "title": "Путевые точки", "content": "Путевые точки — это общие географические точки интереса, которые видят все участники mesh-сети. Создание путевой точки . | Нажмите и удерживайте карту в нужном месте. | Введите имя и, при желании, описанье. | Выберите значок/эмодзи для путевой точки. | Нажмите “Отправить”, чтобы поделиться с mesh-сетью. | . Путевые точки адресуются так же, как сообщения: по умолчанию они передаются в основном канале, но путевую точку также можно отправить на конкретном канале или как личное сообщение одной ноде. Свойства путевой точки . | Свойство | Описание | . | Имя | Короткий идентификатор (не более 29 символов) | . | Описание | Необязательное более длинное описание | . | Значок | Визуальный эмодзи маркер на карте | . | Заблокировано | Если заблокировано, только создатель может изменить или удалить | . | Истечение срока | Необязательная дата и время автоматического удаления | . | Геозона | Необязательная зона оповещения о входе/выходе — см. ниже | . Истечение срока путевой точки . Для путевых точек можно настроить автоматическое истечение срока: . | Никогда (по умолчанию) — путевая точка остаётся, пока не будет удалена вручную | По времени — выберите конкретные дату и время; путевая точка будет автоматически удалена, как только это время наступит. Полезно для временных меток, таких как точки сбора, опасности или места встреч. | . Истёкшие путевые точки автоматически скрываются с карты, чтобы не загромождать отображение. Обратный отсчёт до истечения срока основан на заданном тобою абсолютном времени, а не на промежутке с момента создания или получения путевой точки. Геозоны путевых точек . Любая путевая точка может также задавать геозону — область оповещения, — чтобы ты или другие участники получали уведомления, когда нода входит в неё или покидает её: . | Задайте радиус геозоны с помощью готовых вариантов (или “Выкл”, чтобы отключить), либо нажмите “Задать область на карте”, чтобы нарисовать собственную прямоугольную область. | После задания области включите переключатели “Оповещать при входе” и/или “Оповещать при выходе”. | При необходимости включите “Только избранные”, чтобы ограничить оповещения только избранными нодами. | . Поскольку путевые точки (и их геозоны) передаются всей mesh-сети, по умолчанию оповещается только создатель. Если кто-то другой поделился с вами путевой точкой с геозоной, в её подробностях отображается опция “Оповещать меня о пересечениях”, позволяющая тебе также получать оповещения о входе/выходе. Управление путевыми точками . | Нажмите на путевую точку на карте, чтобы просмотреть её сведения и координаты | Редактируйте или удаляйте созданные тобою путевые точки | Заблокированные путевые точки не могут быть изменены или удалены другими нодами — только создатель может их редактировать | Незаблокированные путевые точки может редактировать любой участник mesh-сети | . ", "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#путевые-точки" - },"2491": { + },"2419": { "doc": "Карта и путевые точки", "title": "Слои карты", "content": "Нажмите на значок слоёв на карте, чтобы открыть “Управление слоями карты”, где можно импортировать собственные слои в формате .kml, .kmz или GeoJSON — либо открыв файл с помощью Meshtastic, либо передав его в приложение из другой программы. Импортированные слои отображаются в списке с переключателем для показа/скрытия каждого и возможностью удалить слой. Доступно как в Google Play, так и в F-Droid сборках. Планировщик участков . Планировщик участков оценивает радиочастотное покрытие для передатчика и отображает его на карте в виде цветового наложения. Откройте его с панели управления картой или со страницы сведений о ноде через “Оценку покрытия” (отображается только для нод с известным местоположением). Настройте передатчик (местоположение, частота, мощность передачи, усиление и высота антенны), приёмник (чувствительность, высота) и параметры симуляции (максимальная дальность, рельеф высокого разрешения, цветовая палитра), затем запустите расчёт. Как и слои карты, планировщик участков работает как в Google Play, так и в F-Droid сборках. ", "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#слои-карты" - },"2492": { + },"2420": { "doc": "Карта и путевые точки", "title": "Передача геоданных", "content": "Включение передачи геоданных . Твоя нода передаёт свои GPS-координаты на основе: . | Фиксированный интервал — передача координат через равные промежутки времени | Адаптивная передача — передача при превышении порога движения | Вручную — делиться только по явному запросу | . Настройте поведение передачи геоданных в Настройки → Геоданные. Вопросы приватности . 🔒 Приватность: Данные о местоположении передаются всем нодам на твоём канале. Если ты не хочешь раскрывать своё местоположение, отключите GPS в настройках или используйте фиксированное/фиктивное местоположение. ", "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#передача-геоданных" - },"2493": { + },"2421": { "doc": "Карта и путевые точки", "title": "Источники карт", "content": "Основная карта зависит от варианта сборки: сборки для Google Play используют Google Maps, а сборки F-Droid и настольные — OpenStreetMap. Поверх основной карты доступны дополнительные источники плиток в качестве наложений или альтернатив: . | Спутниковый снимки (где доступно) | Офлайн-плитки (загружайте области карт для использования офлайн) | . ", "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#источники-карт" - },"2494": { + },"2422": { "doc": "Карта и путевые точки", "title": "Связанные темы", "content": ". | Ноды — просмотр и фильтрация списка нод | Метрики нод — качество сигнала и история местоположения для отдельных нод | Обнаружение — трассировка и информация о соседях для понимания топологии mesh-сети | Единицы измерения и регион — форматы отображения расстояний и координат | . ", "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#связанные-темы" + },"2423": { + "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" + },"2424": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#map-view", + + "relUrl": "/ko-rKR/user/map-and-waypoints.html#map-view" + },"2425": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#waypoints", + + "relUrl": "/ko-rKR/user/map-and-waypoints.html#waypoints" + },"2426": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#map-layers", + + "relUrl": "/ko-rKR/user/map-and-waypoints.html#map-layers" + },"2427": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/ko-rKR/user/map-and-waypoints.html#position-sharing" + },"2428": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#map-sources", + + "relUrl": "/ko-rKR/user/map-and-waypoints.html#map-sources" + },"2429": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2430": { + "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" + },"2431": { + "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" + },"2432": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#map-view", + + "relUrl": "/hr-rHR/user/map-and-waypoints.html#map-view" + },"2433": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#waypoints", + + "relUrl": "/hr-rHR/user/map-and-waypoints.html#waypoints" + },"2434": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#map-layers", + + "relUrl": "/hr-rHR/user/map-and-waypoints.html#map-layers" + },"2435": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/hr-rHR/user/map-and-waypoints.html#position-sharing" + },"2436": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#map-sources", + + "relUrl": "/hr-rHR/user/map-and-waypoints.html#map-sources" + },"2437": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2438": { + "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" + },"2439": { + "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" + },"2440": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#map-view", + + "relUrl": "/sq-rAL/user/map-and-waypoints.html#map-view" + },"2441": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#waypoints", + + "relUrl": "/sq-rAL/user/map-and-waypoints.html#waypoints" + },"2442": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#map-layers", + + "relUrl": "/sq-rAL/user/map-and-waypoints.html#map-layers" + },"2443": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/sq-rAL/user/map-and-waypoints.html#position-sharing" + },"2444": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#map-sources", + + "relUrl": "/sq-rAL/user/map-and-waypoints.html#map-sources" + },"2445": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2446": { + "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" + },"2447": { + "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" + },"2448": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#map-view", + + "relUrl": "/no-rNO/user/map-and-waypoints.html#map-view" + },"2449": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#waypoints", + + "relUrl": "/no-rNO/user/map-and-waypoints.html#waypoints" + },"2450": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#map-layers", + + "relUrl": "/no-rNO/user/map-and-waypoints.html#map-layers" + },"2451": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/no-rNO/user/map-and-waypoints.html#position-sharing" + },"2452": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#map-sources", + + "relUrl": "/no-rNO/user/map-and-waypoints.html#map-sources" + },"2453": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2454": { + "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" + },"2455": { + "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" + },"2456": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#map-view", + + "relUrl": "/lt-rLT/user/map-and-waypoints.html#map-view" + },"2457": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#waypoints", + + "relUrl": "/lt-rLT/user/map-and-waypoints.html#waypoints" + },"2458": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#map-layers", + + "relUrl": "/lt-rLT/user/map-and-waypoints.html#map-layers" + },"2459": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/lt-rLT/user/map-and-waypoints.html#position-sharing" + },"2460": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#map-sources", + + "relUrl": "/lt-rLT/user/map-and-waypoints.html#map-sources" + },"2461": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2462": { + "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" + },"2463": { + "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" + },"2464": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#map-view", + + "relUrl": "/ar-rSA/user/map-and-waypoints.html#map-view" + },"2465": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#waypoints", + + "relUrl": "/ar-rSA/user/map-and-waypoints.html#waypoints" + },"2466": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#map-layers", + + "relUrl": "/ar-rSA/user/map-and-waypoints.html#map-layers" + },"2467": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/ar-rSA/user/map-and-waypoints.html#position-sharing" + },"2468": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#map-sources", + + "relUrl": "/ar-rSA/user/map-and-waypoints.html#map-sources" + },"2469": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2470": { + "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" + },"2471": { + "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" + },"2472": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#map-view", + + "relUrl": "/pt-rPT/user/map-and-waypoints.html#map-view" + },"2473": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#waypoints", + + "relUrl": "/pt-rPT/user/map-and-waypoints.html#waypoints" + },"2474": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#map-layers", + + "relUrl": "/pt-rPT/user/map-and-waypoints.html#map-layers" + },"2475": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/pt-rPT/user/map-and-waypoints.html#position-sharing" + },"2476": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#map-sources", + + "relUrl": "/pt-rPT/user/map-and-waypoints.html#map-sources" + },"2477": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2478": { + "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" + },"2479": { + "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" + },"2480": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#map-view", + + "relUrl": "/iw-rIL/user/map-and-waypoints.html#map-view" + },"2481": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#waypoints", + + "relUrl": "/iw-rIL/user/map-and-waypoints.html#waypoints" + },"2482": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#map-layers", + + "relUrl": "/iw-rIL/user/map-and-waypoints.html#map-layers" + },"2483": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/iw-rIL/user/map-and-waypoints.html#position-sharing" + },"2484": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#map-sources", + + "relUrl": "/iw-rIL/user/map-and-waypoints.html#map-sources" + },"2485": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2486": { + "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" + },"2487": { + "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" + },"2488": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#map-view", + + "relUrl": "/el-rGR/user/map-and-waypoints.html#map-view" + },"2489": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#waypoints", + + "relUrl": "/el-rGR/user/map-and-waypoints.html#waypoints" + },"2490": { + "doc": "Map & Waypoints", + "title": "Map Layers", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#map-layers", + + "relUrl": "/el-rGR/user/map-and-waypoints.html#map-layers" + },"2491": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/el-rGR/user/map-and-waypoints.html#position-sharing" + },"2492": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#map-sources", + + "relUrl": "/el-rGR/user/map-and-waypoints.html#map-sources" + },"2493": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2494": { + "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" },"2495": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/nl-rNL/user/map-and-waypoints.html#map--waypoints" + "relUrl": "/ro-rRO/user/map-and-waypoints.html#map--waypoints" },"2496": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#map-view", - "relUrl": "/nl-rNL/user/map-and-waypoints.html#map-view" + "relUrl": "/ro-rRO/user/map-and-waypoints.html#map-view" },"2497": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#waypoints", - "relUrl": "/nl-rNL/user/map-and-waypoints.html#waypoints" + "relUrl": "/ro-rRO/user/map-and-waypoints.html#waypoints" },"2498": { "doc": "Map & Waypoints", "title": "Map Layers", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#map-layers", + "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#map-layers", - "relUrl": "/nl-rNL/user/map-and-waypoints.html#map-layers" + "relUrl": "/ro-rRO/user/map-and-waypoints.html#map-layers" },"2499": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#position-sharing", - "relUrl": "/nl-rNL/user/map-and-waypoints.html#position-sharing" + "relUrl": "/ro-rRO/user/map-and-waypoints.html#position-sharing" },"2500": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#map-sources", - "relUrl": "/nl-rNL/user/map-and-waypoints.html#map-sources" + "relUrl": "/ro-rRO/user/map-and-waypoints.html#map-sources" },"2501": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#related-topics", - "relUrl": "/nl-rNL/user/map-and-waypoints.html#related-topics" + "relUrl": "/ro-rRO/user/map-and-waypoints.html#related-topics" },"2502": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html", - "relUrl": "/nl-rNL/user/map-and-waypoints.html" + "relUrl": "/ro-rRO/user/map-and-waypoints.html" },"2503": { "doc": "Kaart ja teekonnapunktid", "title": "Kaart ja teekonnapunktid", @@ -17572,555 +17572,555 @@ "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/it-rIT/user/map-and-waypoints.html#map--waypoints" + "relUrl": "/ga-rIE/user/map-and-waypoints.html#map--waypoints" },"2511": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#map-view", - "relUrl": "/it-rIT/user/map-and-waypoints.html#map-view" + "relUrl": "/ga-rIE/user/map-and-waypoints.html#map-view" },"2512": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#waypoints", - "relUrl": "/it-rIT/user/map-and-waypoints.html#waypoints" + "relUrl": "/ga-rIE/user/map-and-waypoints.html#waypoints" },"2513": { "doc": "Map & Waypoints", - "title": "Livelli della mappa", + "title": "Map Layers", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#livelli-della-mappa", + "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#map-layers", - "relUrl": "/it-rIT/user/map-and-waypoints.html#livelli-della-mappa" + "relUrl": "/ga-rIE/user/map-and-waypoints.html#map-layers" },"2514": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#position-sharing", - "relUrl": "/it-rIT/user/map-and-waypoints.html#position-sharing" + "relUrl": "/ga-rIE/user/map-and-waypoints.html#position-sharing" },"2515": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#map-sources", - "relUrl": "/it-rIT/user/map-and-waypoints.html#map-sources" + "relUrl": "/ga-rIE/user/map-and-waypoints.html#map-sources" },"2516": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#related-topics", - "relUrl": "/it-rIT/user/map-and-waypoints.html#related-topics" + "relUrl": "/ga-rIE/user/map-and-waypoints.html#related-topics" },"2517": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html", - "relUrl": "/it-rIT/user/map-and-waypoints.html" + "relUrl": "/ga-rIE/user/map-and-waypoints.html" },"2518": { - "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" - },"2519": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#map-view", - - "relUrl": "/ar-rSA/user/map-and-waypoints.html#map-view" - },"2520": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#waypoints", - - "relUrl": "/ar-rSA/user/map-and-waypoints.html#waypoints" - },"2521": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#map-layers", - - "relUrl": "/ar-rSA/user/map-and-waypoints.html#map-layers" - },"2522": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/ar-rSA/user/map-and-waypoints.html#position-sharing" - },"2523": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#map-sources", - - "relUrl": "/ar-rSA/user/map-and-waypoints.html#map-sources" - },"2524": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2525": { - "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" - },"2526": { - "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" - },"2527": { - "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#map-view", - - "relUrl": "/sk-rSK/user/map-and-waypoints.html#map-view" - },"2528": { - "doc": "Map & Waypoints", - "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#waypoints", - - "relUrl": "/sk-rSK/user/map-and-waypoints.html#waypoints" - },"2529": { - "doc": "Map & Waypoints", - "title": "Map Layers", - "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#map-layers", - - "relUrl": "/sk-rSK/user/map-and-waypoints.html#map-layers" - },"2530": { - "doc": "Map & Waypoints", - "title": "Position Sharing", - "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#position-sharing", - - "relUrl": "/sk-rSK/user/map-and-waypoints.html#position-sharing" - },"2531": { - "doc": "Map & Waypoints", - "title": "Map Sources", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#map-sources", - - "relUrl": "/sk-rSK/user/map-and-waypoints.html#map-sources" - },"2532": { - "doc": "Map & Waypoints", - "title": "Related Topics", - "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2533": { - "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" - },"2534": { "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" - },"2535": { + },"2519": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#map-view", "relUrl": "/pl-rPL/user/map-and-waypoints.html#map-view" - },"2536": { + },"2520": { "doc": "Map & Waypoints", "title": "Waypoints", "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#waypoints", "relUrl": "/pl-rPL/user/map-and-waypoints.html#waypoints" - },"2537": { + },"2521": { "doc": "Map & Waypoints", "title": "Warstwy map", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#warstwy-map", "relUrl": "/pl-rPL/user/map-and-waypoints.html#warstwy-map" - },"2538": { + },"2522": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#position-sharing", "relUrl": "/pl-rPL/user/map-and-waypoints.html#position-sharing" - },"2539": { + },"2523": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#map-sources", "relUrl": "/pl-rPL/user/map-and-waypoints.html#map-sources" - },"2540": { + },"2524": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" - },"2541": { + },"2525": { "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" - },"2542": { - "doc": "地圖與航點", - "title": "地圖與航點", - "content": "地圖畫面顯示 mesh 網路上各節點的地理位置，以及已分享的航點。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html", + },"2526": { + "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": "/zh-rTW/user/map-and-waypoints.html" - },"2543": { - "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. 地圖控制項 . | 縮放 — 雙指縮放或使用 +/- 按鈕 | 平移 — 拖曳以瀏覽地圖 | 置中 — 點選位置按鈕，使地圖以您的位置為中心 | 點選節點 — 點選節點標記以檢視詳細資訊 | . 浮動工具列提供快速存取羅盤、圖層切換、節點篩選、重新整理及位置追蹤等功能。 點選羅盤可重新對齊正北方向，或點選位置按鈕使地圖以您目前位置為中心。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html#%E5%9C%B0%E5%9C%96%E6%AA%A2%E8%A6%96", + "relUrl": "/nl-rNL/user/map-and-waypoints.html#map--waypoints" + },"2527": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#map-view", - "relUrl": "/zh-rTW/user/map-and-waypoints.html#地圖檢視" - },"2544": { - "doc": "地圖與航點", - "title": "航點", - "content": "航點是可分享的地理興趣點，mesh 網路上的所有成員均可看見。 . 建立航點 . | 在地圖上的目標位置長按。 | 輸入名稱及選填的說明。 | 為航點選擇圖示或表情符號。 | 點選「傳送」以分享至 mesh 網路。 | . Waypoints are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 航點屬性 . | 屬性 | 描述說明 | . | 名稱 | Short identifier (max 29 characters) | . | 描述說明 | 選填的較長說明 | . | 圖示 | 地圖上的視覺標記表情符號 | . | 鎖定 | 若已鎖定，僅建立者可編輯或刪除 | . | 到期時間 | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see below | . 航點到期設定 . 航點可設定為自動到期： . | 永不到期（預設）— 航點將保留至手動刪除為止 | 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. 管理航點 . | 點選地圖上的航點，可檢視其詳細資訊與座標 | 編輯或刪除您建立的航點 | 已鎖定的航點無法被其他節點修改或刪除 — 僅原始建立者可進行變更 | 未鎖定的航點可由任何 mesh 成員編輯 | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html#%E8%88%AA%E9%BB%9E", + "relUrl": "/nl-rNL/user/map-and-waypoints.html#map-view" + },"2528": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#waypoints", - "relUrl": "/zh-rTW/user/map-and-waypoints.html#航點" - },"2545": { - "doc": "地圖與航點", - "title": "地圖圖層", + "relUrl": "/nl-rNL/user/map-and-waypoints.html#waypoints" + },"2529": { + "doc": "Map & Waypoints", + "title": "Map Layers", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html#%E5%9C%B0%E5%9C%96%E5%9C%96%E5%B1%A4", + "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#map-layers", - "relUrl": "/zh-rTW/user/map-and-waypoints.html#地圖圖層" + "relUrl": "/nl-rNL/user/map-and-waypoints.html#map-layers" + },"2530": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/nl-rNL/user/map-and-waypoints.html#position-sharing" + },"2531": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#map-sources", + + "relUrl": "/nl-rNL/user/map-and-waypoints.html#map-sources" + },"2532": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2533": { + "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" + },"2534": { + "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" + },"2535": { + "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#map-view", + + "relUrl": "/sv-rSE/user/map-and-waypoints.html#map-view" + },"2536": { + "doc": "Map & Waypoints", + "title": "Waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#waypoints", + + "relUrl": "/sv-rSE/user/map-and-waypoints.html#waypoints" + },"2537": { + "doc": "Map & Waypoints", + "title": "Kartlager", + "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#kartlager", + + "relUrl": "/sv-rSE/user/map-and-waypoints.html#kartlager" + },"2538": { + "doc": "Map & Waypoints", + "title": "Position Sharing", + "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#position-sharing", + + "relUrl": "/sv-rSE/user/map-and-waypoints.html#position-sharing" + },"2539": { + "doc": "Map & Waypoints", + "title": "Map Sources", + "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#map-sources", + + "relUrl": "/sv-rSE/user/map-and-waypoints.html#map-sources" + },"2540": { + "doc": "Map & Waypoints", + "title": "Related Topics", + "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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" + },"2541": { + "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" + },"2542": { + "doc": "マップとウェイポイント", + "title": "マップとウェイポイント", + "content": "マップ画面には、メッシュ上のノードの地理的な位置が、共有されたウェイポイントとともに表示されます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/map-and-waypoints.html", + + "relUrl": "/ja-rJP/user/map-and-waypoints.html" + },"2543": { + "doc": "マップとウェイポイント", + "title": "マップビュー", + "content": "マップには次のものが表示されます： . | ノードの位置： 位置を報告している各ノードの色付きマーカー | ウェイポイント： 共有された注目地点 | 自分の位置： 現在の GPS 位置 | . ノードのマーカー . 位置を報告している各ノードは、そのノードの短縮名を表示するノードチップマーカーとして表示されます。 チップは、そのノード固有のアイデンティティカラー（ノード番号から導かれる一定の色）で色付けされます。ノードリストで使われるのと同じチップなので、どこでも同じ見た目になります。 マーカーの色は、オンライン／オフラインの状態を表しません。 ノードの位置がライブで更新されると、そのマーカーが短く脈打つように点滅します。 縮小すると、近くのマーカーはまとめて表示（クラスタリング）されます。 . マップの操作 . | ズーム： ピンチ操作、または +/− ボタンを使います | 移動： ドラッグして見て回ります | 中央に配置： 位置ボタンを選ぶと、自分の位置を中央に表示します | ノードのタップ： ノードのマーカーをタップすると詳細を表示します | . フローティングツールバーから、コンパス、レイヤーの切り替え、ノードの絞り込み、更新、位置追跡にすばやくアクセスできます。 コンパスをタップすると北を上に向け直し、位置ボタンをタップすると現在の位置を中央に表示します。 . ", + "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#マップビュー" + },"2544": { + "doc": "マップとウェイポイント", + "title": "ウェイポイント", + "content": "ウェイポイントは、メッシュの全メンバーが見られる、共有された地理的な注目地点です。 . ウェイポイントを作成する . | マップ上の目的の場所を長押しします。 | 名前と、任意で説明を入力します。 | ウェイポイントのアイコン／絵文字を選びます。 | 「送信」をタップしてメッシュに共有します。 | . ウェイポイントはメッセージと同じように宛先を指定します。既定ではプライマリチャンネルにブロードキャストされますが、特定のチャンネルに送ったり、単一のノードへのダイレクトメッセージとして送ったりすることもできます。 . ウェイポイントのプロパティ . | プロパティ | 説明 | . | 名前 | 短い識別子（最大 29 文字） | . | 説明 | 任意の、より詳しい説明 | . | アイコン | マップ上の視覚的なマーカー絵文字 | . | ロック済み | ロックすると、作成者だけが編集・削除できます | . | 有効期限 | 任意の、自動削除する日時 | . | ジオフェンス | 任意の、進入／退出を通知するエリア。詳しくは後述します | . ウェイポイントの有効期限 . ウェイポイントは、自動的に期限切れになるよう設定できます： . | なし（デフォルト）：手動で削除するまでウェイポイントは残ります | 期限付き：特定の日時を指定します。その時刻を過ぎると、ウェイポイントは自動的に削除されます。 集合地点、危険箇所、待ち合わせ場所などの一時的なマーカーに便利です。 | . 期限切れのウェイポイントは、表示が煩雑にならないよう、自動的にマップから隠されます。 有効期限のカウントダウンは、指定した絶対時刻を基準とし、ウェイポイントが作成または受信されてからの経過時間ではありません。 . ウェイポイントのジオフェンス . どのウェイポイントにもジオフェンス（通知エリア）を設定できます。これにより、ノードがそのエリアに進入または退出したときに、あなたや他のメンバーに通知が届きます： . | プリセットのチップからジオフェンスの半径を設定する（無効にするにはオフ）か、「マップ上でエリアを設定」をタップして、任意の四角形のエリアを描画します。 | エリアを設定したら、「進入時に通知」や「退出時に通知」を切り替えます。 | 任意で「お気に入りのみ」を有効にすると、通知をお気に入りのノードに限定できます。 | . ウェイポイント（およびそのジオフェンス）はメッシュ全体にブロードキャストされるため、デフォルトでは作成者だけに通知されます。 他の人がジオフェンス付きのウェイポイントを共有した場合、その詳細ビューに「通過を通知する」というオプトインが表示され、あなたも進入／退出の通知を受け取れます。 . ウェイポイントを管理する . | マップ上のウェイポイントをタップすると、その詳細と座標を表示します | 自分が作成したウェイポイントを編集または削除できます | ロックされたウェイポイントは、他のノードから変更・削除できません。元の作成者だけが変更できます | ロックされていないウェイポイントは、どのメッシュメンバーでも編集できます | . ", + "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#ウェイポイント" + },"2545": { + "doc": "マップとウェイポイント", + "title": "マップレイヤー", + "content": "マップのレイヤーアイコンをタップすると「マップレイヤーの管理」が開き、.kml、.kmz、または GeoJSON 形式の独自のオーバーレイをインポートできます。Meshtastic でファイルを開くか、別のアプリからアプリに共有することでインポートします。 インポートしたレイヤーは、それぞれ表示／非表示を切り替えるトグルと、削除するオプションとともに一覧表示されます。 これは Google Play 版と F-Droid 版の両方で利用できます。 . サイトプランナー . サイトプランナーは、送信機の RF カバレッジを推定し、色分けされたオーバーレイとしてマップに描画します。 マップの操作から開くか、ノードの詳細ページから「カバレッジを推定」で開きます（位置が判明しているノードでのみ表示されます）。 送信機（位置、周波数、送信出力、アンテナ利得と高さ）、受信機（感度、高さ）、シミュレーションのオプション（最大範囲、高解像度の地形、カラーパレット）を設定してから、推定を実行します。 マップレイヤーと同様に、サイトプランナーも Google Play 版と F-Droid 版の両方で動作します。 . ", + "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#マップレイヤー" },"2546": { - "doc": "地圖與航點", - "title": "位置分享", - "content": "啟用位置分享 . 您的節點依據以下方式分享 GPS 位置： . | 固定間隔 — 依固定時間間隔廣播位置 | 智慧位置 — 移動距離超過閾值時才廣播位置 | 手動 — 僅在明確要求時才分享位置 | . 請在「設定 → 位置」中設定位置行為。 . 隱私注意事項 . 🔒 隱私：位置資料將廣播至您頻道上的所有節點。 若不想分享您的位置，請在設定中停用 GPS 定位，或使用固定／假位置。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html#%E4%BD%8D%E7%BD%AE%E5%88%86%E4%BA%AB", + "doc": "マップとウェイポイント", + "title": "位置の共有", + "content": "位置の共有を有効にする . ノードは、次のいずれかに基づいて GPS 位置を共有します： . | 固定間隔： 一定間隔で位置をブロードキャストします | スマート位置： 移動がしきい値を超えたときにブロードキャストします | 手動： 明示的に要求されたときのみ共有します | . 位置の動作は「設定 → 位置」で設定します。 . プライバシーに関する注意 . 🔒 プライバシー： 位置データは、チャンネル上のすべてのノードにブロードキャストされます。 位置を共有したくない場合は、設定で GPS 位置を無効にするか、固定／ダミーの位置を使用してください。 . ", + "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": "/zh-rTW/user/map-and-waypoints.html#位置分享" + "relUrl": "/ja-rJP/user/map-and-waypoints.html#位置の共有" },"2547": { - "doc": "地圖與航點", - "title": "地圖來源", - "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | 衛星影像（視可用性而定） | 離線圖磚（下載地圖區域以供離線使用） | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html#%E5%9C%B0%E5%9C%96%E4%BE%86%E6%BA%90", + "doc": "マップとウェイポイント", + "title": "マップソース", + "content": "ベースマップはアプリの版によって異なります。Google Play 版は Google マップを、F-Droid 版とデスクトップ版は OpenStreetMap を使用します。 ベースマップの上に、オーバーレイまたは代替として、追加のタイルソースを利用できます： . | 衛星画像（利用可能な場合） | オフラインタイル（オフラインで使うためにマップのエリアをダウンロード） | . ", + "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": "/zh-rTW/user/map-and-waypoints.html#地圖來源" + "relUrl": "/ja-rJP/user/map-and-waypoints.html#マップソース" },"2548": { - "doc": "地圖與航點", - "title": "相關主題", - "content": ". | 〔節點〕(nodes) — 檢視與篩選您的節點清單 | 〔節點數據〕(node-metrics) — 各節點的訊號品質與位置歷史記錄 | 〔探索〕(discovery) — 路由追蹤與鄰近節點資訊，用於了解 mesh 網路拓撲 | 〔單位與地區設定〕(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", + "doc": "マップとウェイポイント", + "title": "関連トピック", + "content": ". | ノード：ノードリストの表示と絞り込み | ノードメトリクス：各ノードの信号品質と位置履歴 | 探索：メッシュのトポロジーを把握するためのルート追跡と隣接ノード情報 | 単位とロケール：距離と座標の表示形式 | . ", + "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": "/zh-rTW/user/map-and-waypoints.html#相關主題" + "relUrl": "/ja-rJP/user/map-and-waypoints.html#関連トピック" },"2549": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/cs-rCZ/user/map-and-waypoints.html#map--waypoints" + "relUrl": "/hu-rHU/user/map-and-waypoints.html#map--waypoints" },"2550": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#map-view", - "relUrl": "/cs-rCZ/user/map-and-waypoints.html#map-view" + "relUrl": "/hu-rHU/user/map-and-waypoints.html#map-view" },"2551": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#waypoints", - "relUrl": "/cs-rCZ/user/map-and-waypoints.html#waypoints" + "relUrl": "/hu-rHU/user/map-and-waypoints.html#waypoints" },"2552": { "doc": "Map & Waypoints", - "title": "Mapové vrstvy", + "title": "Térképrétegek", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#mapov%C3%A9-vrstvy", + "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#t%C3%A9rk%C3%A9pr%C3%A9tegek", - "relUrl": "/cs-rCZ/user/map-and-waypoints.html#mapové-vrstvy" + "relUrl": "/hu-rHU/user/map-and-waypoints.html#térképrétegek" },"2553": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#position-sharing", - "relUrl": "/cs-rCZ/user/map-and-waypoints.html#position-sharing" + "relUrl": "/hu-rHU/user/map-and-waypoints.html#position-sharing" },"2554": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#map-sources", - "relUrl": "/cs-rCZ/user/map-and-waypoints.html#map-sources" + "relUrl": "/hu-rHU/user/map-and-waypoints.html#map-sources" },"2555": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#related-topics", - "relUrl": "/cs-rCZ/user/map-and-waypoints.html#related-topics" + "relUrl": "/hu-rHU/user/map-and-waypoints.html#related-topics" },"2556": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html", - "relUrl": "/cs-rCZ/user/map-and-waypoints.html" + "relUrl": "/hu-rHU/user/map-and-waypoints.html" },"2557": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/fr-rFR/user/map-and-waypoints.html#map--waypoints" + "relUrl": "/ht-rHT/user/map-and-waypoints.html#map--waypoints" },"2558": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#map-view", - "relUrl": "/fr-rFR/user/map-and-waypoints.html#map-view" + "relUrl": "/ht-rHT/user/map-and-waypoints.html#map-view" },"2559": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#waypoints", - "relUrl": "/fr-rFR/user/map-and-waypoints.html#waypoints" + "relUrl": "/ht-rHT/user/map-and-waypoints.html#waypoints" },"2560": { "doc": "Map & Waypoints", - "title": "Couches cartographiques", + "title": "Map Layers", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#couches-cartographiques", + "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#map-layers", - "relUrl": "/fr-rFR/user/map-and-waypoints.html#couches-cartographiques" + "relUrl": "/ht-rHT/user/map-and-waypoints.html#map-layers" },"2561": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#position-sharing", - "relUrl": "/fr-rFR/user/map-and-waypoints.html#position-sharing" + "relUrl": "/ht-rHT/user/map-and-waypoints.html#position-sharing" },"2562": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#map-sources", - "relUrl": "/fr-rFR/user/map-and-waypoints.html#map-sources" + "relUrl": "/ht-rHT/user/map-and-waypoints.html#map-sources" },"2563": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#related-topics", - "relUrl": "/fr-rFR/user/map-and-waypoints.html#related-topics" + "relUrl": "/ht-rHT/user/map-and-waypoints.html#related-topics" },"2564": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html", - "relUrl": "/fr-rFR/user/map-and-waypoints.html" + "relUrl": "/ht-rHT/user/map-and-waypoints.html" },"2565": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/zh-rCN/user/map-and-waypoints.html#map--waypoints" + "relUrl": "/gl-rES/user/map-and-waypoints.html#map--waypoints" },"2566": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#map-view", - "relUrl": "/zh-rCN/user/map-and-waypoints.html#map-view" + "relUrl": "/gl-rES/user/map-and-waypoints.html#map-view" },"2567": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#waypoints", - "relUrl": "/zh-rCN/user/map-and-waypoints.html#waypoints" + "relUrl": "/gl-rES/user/map-and-waypoints.html#waypoints" },"2568": { "doc": "Map & Waypoints", - "title": "地图图层", + "title": "Map Layers", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#%E5%9C%B0%E5%9B%BE%E5%9B%BE%E5%B1%82", + "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#map-layers", - "relUrl": "/zh-rCN/user/map-and-waypoints.html#地图图层" + "relUrl": "/gl-rES/user/map-and-waypoints.html#map-layers" },"2569": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#position-sharing", - "relUrl": "/zh-rCN/user/map-and-waypoints.html#position-sharing" + "relUrl": "/gl-rES/user/map-and-waypoints.html#position-sharing" },"2570": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#map-sources", - "relUrl": "/zh-rCN/user/map-and-waypoints.html#map-sources" + "relUrl": "/gl-rES/user/map-and-waypoints.html#map-sources" },"2571": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#related-topics", - "relUrl": "/zh-rCN/user/map-and-waypoints.html#related-topics" + "relUrl": "/gl-rES/user/map-and-waypoints.html#related-topics" },"2572": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html", - "relUrl": "/zh-rCN/user/map-and-waypoints.html" + "relUrl": "/gl-rES/user/map-and-waypoints.html" },"2573": { "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/srp/user/map-and-waypoints.html#map--waypoints" + "relUrl": "/tr-rTR/user/map-and-waypoints.html#map--waypoints" },"2574": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#map-view", - "relUrl": "/srp/user/map-and-waypoints.html#map-view" + "relUrl": "/tr-rTR/user/map-and-waypoints.html#map-view" },"2575": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#waypoints", - "relUrl": "/srp/user/map-and-waypoints.html#waypoints" + "relUrl": "/tr-rTR/user/map-and-waypoints.html#waypoints" },"2576": { "doc": "Map & Waypoints", "title": "Map Layers", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#map-layers", + "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#map-layers", - "relUrl": "/srp/user/map-and-waypoints.html#map-layers" + "relUrl": "/tr-rTR/user/map-and-waypoints.html#map-layers" },"2577": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#position-sharing", - "relUrl": "/srp/user/map-and-waypoints.html#position-sharing" + "relUrl": "/tr-rTR/user/map-and-waypoints.html#position-sharing" },"2578": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#map-sources", - "relUrl": "/srp/user/map-and-waypoints.html#map-sources" + "relUrl": "/tr-rTR/user/map-and-waypoints.html#map-sources" },"2579": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#related-topics", - "relUrl": "/srp/user/map-and-waypoints.html#related-topics" + "relUrl": "/tr-rTR/user/map-and-waypoints.html#related-topics" },"2580": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html", - "relUrl": "/srp/user/map-and-waypoints.html" + "relUrl": "/tr-rTR/user/map-and-waypoints.html" },"2581": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#map--waypoints", - "relUrl": "/sq-rAL/user/map-and-waypoints.html#map--waypoints" + "relUrl": "/es-rES/user/map-and-waypoints.html#map--waypoints" },"2582": { "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 — select the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#map-view", + "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#map-view", - "relUrl": "/sq-rAL/user/map-and-waypoints.html#map-view" + "relUrl": "/es-rES/user/map-and-waypoints.html#map-view" },"2583": { "doc": "Map & Waypoints", "title": "Waypoints", - "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#waypoints", + "content": "Waypoints are shared geographic points of interest that all mesh members can see. Creating a Waypoint . | Long-press on 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 are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node. 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 below | . 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 on the map to view its details and coordinates | Edit or delete waypoints you created | Locked waypoints cannot be modified or deleted by other nodes — only the original creator can change them | Unlocked waypoints can be edited by any mesh member | . ", + "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#waypoints", - "relUrl": "/sq-rAL/user/map-and-waypoints.html#waypoints" + "relUrl": "/es-rES/user/map-and-waypoints.html#waypoints" },"2584": { "doc": "Map & Waypoints", - "title": "Map Layers", + "title": "Capas del mapa", "content": "Tap the layers icon on the map to open Manage Map Layers, where you can import your own overlays in .kml, .kmz, or GeoJSON format — either by opening a file with Meshtastic or sharing it into the app from another app. Imported layers are listed with a toggle to show/hide each one and an option to remove it. This is available on both the Google Play and F-Droid builds. 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. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#map-layers", + "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#capas-del-mapa", - "relUrl": "/sq-rAL/user/map-and-waypoints.html#map-layers" + "relUrl": "/es-rES/user/map-and-waypoints.html#capas-del-mapa" },"2585": { "doc": "Map & Waypoints", "title": "Position Sharing", "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Fixed interval — broadcast position at regular intervals | Smart position — broadcast when movement exceeds a threshold | Manual — only share when explicitly requested | . Configure position behavior in Settings → Position. Privacy Considerations . 🔒 Privacy: Position data is broadcast to all nodes on your channel. If you don’t want your location shared, disable GPS position in settings or use a fixed/fake position. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#position-sharing", + "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#position-sharing", - "relUrl": "/sq-rAL/user/map-and-waypoints.html#position-sharing" + "relUrl": "/es-rES/user/map-and-waypoints.html#position-sharing" },"2586": { "doc": "Map & Waypoints", "title": "Map Sources", "content": "The base map depends on your app flavor: Google Play builds use Google Maps, while F-Droid and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives: . | Satellite imagery (where available) | Offline tiles (download map areas for offline use) | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#map-sources", + "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#map-sources", - "relUrl": "/sq-rAL/user/map-and-waypoints.html#map-sources" + "relUrl": "/es-rES/user/map-and-waypoints.html#map-sources" },"2587": { "doc": "Map & Waypoints", "title": "Related Topics", "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | 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", + "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#related-topics", - "relUrl": "/sq-rAL/user/map-and-waypoints.html#related-topics" + "relUrl": "/es-rES/user/map-and-waypoints.html#related-topics" },"2588": { "doc": "Map & Waypoints", "title": "Map & Waypoints", "content": " ", - "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html", + "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html", - "relUrl": "/sq-rAL/user/map-and-waypoints.html" + "relUrl": "/es-rES/user/map-and-waypoints.html" },"2589": { "doc": "Measurement & Formatting", "title": "Measurement & Formatting", @@ -18192,1405 +18192,1405 @@ "relUrl": "/en/developer/measurement.html" },"2599": { - "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" - },"2600": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Lýsing | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#channels", - - "relUrl": "/is-rIS/user/messages-and-channels.html#channels" - },"2601": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2602": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2603": { - "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" - },"2604": { - "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" - },"2605": { - "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" - },"2606": { - "doc": "メッセージとチャンネル", - "title": "メッセージとチャンネル", - "content": "Meshtastic は、チャンネルブロードキャストとダイレクトメッセージの 2 つの通信モードをサポートしています。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/messages-and-channels.html", - - "relUrl": "/ja-rJP/user/messages-and-channels.html" - },"2607": { - "doc": "メッセージとチャンネル", - "title": "チャンネル", - "content": "チャンネルは、共有された通信グループです。 同じチャンネル鍵を設定したすべてのノードが、そのチャンネルでメッセージを読み書きできます。 . デフォルトチャンネル . すべての Meshtastic デバイスには、デフォルトの LongFast チャンネルが用意されています。 これは、一般的なメッシュ通信に使われる暗号化されていないチャンネルです。 . チャンネルのセキュリティ . チャンネルは複数の暗号化レベルに対応しています： . | アイコン | セキュリティレベル | 説明 | . | 🔒 | PSK（256 ビット AES） | 強力な事前共有鍵で完全に暗号化されます。 一致する鍵を持つノードだけがメッセージを読めます。 | . | 🔐 | PSK（128 ビット AES） | より短い鍵で暗号化されます。 ほとんどの用途で安全ですが、機密性の高いデータには 256 ビットが推奨されます。 | . | 🔓 | デフォルト／オープン | よく知られたデフォルトの鍵を使用します。 同じプリセットのあらゆる Meshtastic デバイスが、これらのメッセージを読めます。 | . | ⚠️ | 非セキュア＋位置情報 | GPS 位置情報も一斉送信するオープンチャンネルです。 公開メッシュでは注意して使用してください。 | . 🔒 セキュリティのヒント： プライベートな通信には、必ず固有の PSK を設定してください。 デフォルトチャンネルは、新規ユーザーがメッシュを見つけられるよう意図的にオープンになっています。ただし、機密性の高い内容には別途、暗号化されたチャンネルを作成してください。 . チャンネルを追加する . | 「設定 → チャンネル」に移動します。 | 「チャンネルを追加」をタップするか、QR コードをスキャンします。 | チャンネル名と暗号化鍵を設定します。 | アクセスが必要な相手に、チャンネルの URL／QR コードを共有します。 | . チャンネルをタップすると、その詳細と共有オプションが表示されます。 . ", - "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#チャンネル" - },"2608": { - "doc": "メッセージとチャンネル", - "title": "ダイレクトメッセージ", - "content": "ダイレクトメッセージ（DM）は、特定の 2 つのノード間で行われる、ポイントツーポイントの暗号化通信です。 . ダイレクトメッセージを送信する . | 「メッセージ」タブを開きます。 | 連絡先リストからノードを選択するか、ノードリストでノードをタップします。 | メッセージを入力し、「送信」をタップします。 | . メッセージの状態 . ステータスラベルは、自分が送信したメッセージの下にのみ表示されます（他のユーザーからの受信メッセージにはステータスラベルは表示されません）： . | 状態 | 意味 | . | 送信中… | キューに入っているか、すでに無線機に渡された状態で、まだどちらとも確定していません（キュー内と送信中のどちらも同じ表示になります） | . | 受信者に配信済み | ダイレクトメッセージで最も確実な確認です。受信確認が返ってきています | . | メッシュに配信済み | チャンネルブロードキャストでは、メッセージがメッシュに届いたことを示します（ブロードキャストには受信者ごとの確認応答はありません） | . | 中継済み、受信者による確認なし | ダイレクトメッセージでは警告色で表示されます。メッセージは中継されましたが、まだ受信確認が返ってきていません | . | SF++ チェーン経由でルーティング中… | Store & Forward Plus Plus チェーンによってルーティング／バッファリングされています | . | SF++ チェーンで確認済み | SF++ チェーン経由で配信が確認されました | . | エラー | 配信に失敗しました。具体的な理由はステータスをタップして確認してください（下記の「配信エラー」を参照） | . 配信エラー . メッセージの配信に失敗すると、エラーインジケーターが何が問題だったかを示します： . | エラー | 意味 | 対処方法 | . | ルートなし | 宛先ノードへの経路が存在しません | 受信者がオフラインか、メッシュの範囲外の可能性があります。 時間をおくか、距離を縮めてください。 | . | NAK を受信 | 次のホップのノードが中継を拒否しました | 中継ノードが混雑している可能性があります。 しばらく待ってから再試行してください。 | . | タイムアウト | 再試行の時間内に受信確認がありませんでした | 受信者がちょうど範囲外にいる可能性があります。 ホップ数上限を増やすか、より良い場所に移動してみてください。 | . | No radio interface | 送信に使える無線インターフェースがありません | Check that your radio is connected and available. | . | メッシュへの配信に失敗しました | すべての再試行を使い切りました | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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. | . 💡 ヒント： ほとんどの配信エラーは自然に解消します。 ノードに断続的に到達できる場合、メッシュは再試行します。 「ルートなし」エラーが続く場合は、中間のルーターノードがオンラインになっているか確認してください。 . ", - "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#ダイレクトメッセージ" - },"2609": { - "doc": "メッセージとチャンネル", - "title": "メッセージの機能", - "content": "クイックチャット . すばやくやり取りするための、あらかじめ設定されたメッセージです： . | メッセージ入力欄のクイックチャットボタンから利用できます | 組み込みの定型文またはカスタムメッセージから選べます | クイックチャットのメッセージは「設定 → クイックチャット」でカスタマイズできます | 入力が難しい場面（手袋の着用、小さな画面、急いでいるとき）に便利です | . 各クイックチャット項目には、短い名前（ボタンのラベル）、挿入されるメッセージ、そして即時送信トグルがあります。有効にすると、ボタンをタップした時点で、メッセージが入力欄に置かれて編集できる状態になるのではなく、すぐに送信されます： . チャンネルリストには、各チャンネルが最新メッセージのプレビューとともに表示されます。 . メッセージを検索する . チャット画面から、どの会話でもその全履歴を直接検索できます： . | 会話（チャンネルまたはダイレクトメッセージ）を開きます。 | 上部バーの検索アイコンをタップします。 | 「メッセージを検索…」欄に入力します。 検索は入力に応じて、その会話に保存されているすべてのメッセージを対象に実行されます。 | N／M の結果カウンターと前へ／次への矢印を使って、一致箇所間を移動できます。一致箇所は会話内でハイライト表示されます。 | . 💡 ヒント： 検索は全文検索で、開いた会話の中だけを対象とします。他のチャンネルや連絡先をまたいで検索することはありません。 デバイスにすでに保存されているメッセージを対象に照合するため、完全にオフラインで動作します。 . メッセージの吹き出し . メッセージはチャットの吹き出しとして表示され、送信メッセージは右側、受信メッセージは左側に並びます。 各吹き出しには、送信者・タイムスタンプ・配信状況が表示されます。 返信付きのメッセージでは、応答の上に元メッセージの引用プレビューが表示されます。 . テキストの書式 . メッセージは、軽量なインライン Markdown に対応しています。 受信したメッセージは、記法の文字が取り除かれた状態でスタイルが適用されて表示されます： . | 種別 | 記法 | 表示結果 | . | 太字 | **bold** | 太字 | . | 斜体 | *italic* | 斜体 | . | 取り消し線 | ~~strike~~ | 取り消し線 | . | インラインコード | `code` | 等幅の code | . | リンク | [label](https://example.com) | タップできるラベル | . メッセージを作成するときは、入力欄にフォーカスして 3 文字以上入力すると、入力欄の下に書式ツールバーが表示されます。 テキストを選択してスタイルをタップすると、そのテキストが囲まれます（もう一度タップすると解除されます）。選択していない場合は、空のペアが挿入され、カーソルがマーカーの間に置かれます。 リンクボタンをタップすると、URL を入力するダイアログが開きます。 入力中は下書きに書式が適用されて表示されますが、内部のテキストは Markdown の文字を保持しています。 . 💡 ヒント： 書式はメッシュ上ではそのままの文字として送られます。iOS が送信するのと同じバイト列です。 Markdown に対応していないクライアント（古いアプリや、素のファームウェアのクライアント）では、** や ~~ の文字がそのまま表示されます。 URL、メールアドレス、電話番号は、Markdown を使うかどうかにかかわらず、引き続き自動的にリンクになります。 . メンション . メッセージ作成中に @ を入力するとノードにメンションできます。入力に応じて、一致する連絡先がピッカーに提案されます。 受信メッセージでは、メンションはノード名を表示したハイライト付きのチップとして現れます。タップすると、そのノードの詳細ページに直接移動できます。 . リアクション . 絵文字でメッセージにリアクションできます： . | メッセージを長押しすると操作メニューが開きます | 「リアクションを追加」をタップして絵文字を選びます | リアクションはメッセージの吹き出しの下に表示されます | 複数のユーザーが同じメッセージにリアクションできます | 自分のメッセージにも、他の人のメッセージにもリアクションできます | . 💡 ヒント： リアクションは軽量で、通常のテキストメッセージに比べてメッシュの帯域をほとんど消費しません。 . メッセージの操作 . 任意のメッセージを長押しすると、次の操作を利用できます： . | コピー： メッセージのテキストをクリップボードにコピーします | 返信： そのメッセージを引用して返信します | リアクション： 絵文字のリアクションを追加します | 翻訳： 受信メッセージをデバイスの言語に翻訳し、原文と翻訳を切り替えます（Google Play 版のみ。オンデバイス翻訳を使用します） | 削除： 自分が送信したメッセージを削除します（端末内での削除） | . メッセージの優先度 . メッセージは優先度に基づいてキューに入れられ、送信されます： . | 緊急／警報メッセージ（最高） | ダイレクトメッセージ | チャンネルブロードキャスト（最低） | . メッセージの制限 . | 最大長： 200 バイト（ASCII テキストで約 200 文字） | 200 バイトの上限はアプリ内の入力欄に適用されます。メッシュのペイロード上限自体は約 233 バイトのため、他の送信元（アプリ機能や Android Auto など）からのメッセージは、これより少し長い場合があります | レート制限： メッシュは電波利用時間の公平性を確保するため、大量のメッセージは制限されることがあります | 配信： 受信確認がない場合、メッセージは自動的に再送されます | . ", - "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#メッセージの機能" - },"2610": { - "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#ベストプラクティス" - },"2611": { - "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#関連トピック" - },"2612": { - "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" - },"2613": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Descripció | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#channels", - - "relUrl": "/ca-rES/user/messages-and-channels.html#channels" - },"2614": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Temps esgotat | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2615": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2616": { - "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" - },"2617": { - "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" - },"2618": { - "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" - },"2619": { - "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" - },"2620": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Иконица | Security Level | Опис | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "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#канали" - },"2621": { - "doc": "Messages & Channels", - "title": "Директне поруке", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Isteklo vreme | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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#директне-поруке" - },"2622": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2623": { - "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" - },"2624": { - "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" - },"2625": { - "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" - },"2626": { - "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" - },"2627": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | 설명 | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "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#채널" - },"2628": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | 시간 초과 | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2629": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2630": { - "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" - },"2631": { - "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" - },"2632": { - "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" - },"2633": { - "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" - },"2634": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Securitate canal . Channels support multiple encryption levels: . | Icon | Security Level | Descriere | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html#canale", - - "relUrl": "/ro-rRO/user/messages-and-channels.html#canale" - },"2635": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Eroare | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Expirat | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2636": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2637": { - "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" - },"2638": { - "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" - },"2639": { - "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" - },"2640": { - "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" - },"2641": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Cur síos | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html#channels", - - "relUrl": "/ga-rIE/user/messages-and-channels.html#channels" - },"2642": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Earráid | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Am tráth | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2643": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2644": { - "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" - },"2645": { - "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" - },"2646": { - "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" - },"2647": { - "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" - },"2648": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | תיאור | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/messages-and-channels.html#channels", - - "relUrl": "/iw-rIL/user/messages-and-channels.html#channels" - },"2649": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | שגיאה | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2650": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2651": { - "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" - },"2652": { - "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" - },"2653": { - "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" - },"2654": { - "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" - },"2655": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Kanalsäkerhet . Channels support multiple encryption levels: . | Icon | Security Level | Beskrivning | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/messages-and-channels.html#kanaler", - - "relUrl": "/sv-rSE/user/messages-and-channels.html#kanaler" - },"2656": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Fel | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2657": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2658": { - "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" - },"2659": { - "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" - },"2660": { - "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" - },"2661": { - "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" - },"2662": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Deskripsyon | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#channels", - - "relUrl": "/ht-rHT/user/messages-and-channels.html#channels" - },"2663": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erè | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Tan pase | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2664": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2665": { - "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" - },"2666": { - "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" - },"2667": { - "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" - },"2668": { - "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" - },"2669": { - "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-laitteessa on oletuksena LongFast-kanava. Tämä on salaamaton kanava yleiseen mesh-viestintään. Kanavan turvallisuus . Kanavat tukevat useita salaustasoja: . | Ikoni | Suojaustaso | Kuvaus | . | 🔒 | PSK (256-bittinen AES) | Täysin salattu vahvalla esijaetulla avaimella. Vain samaa avainta käyttävät radiot voivat lukea viestejä. | . | 🔐 | PSK (128-bittinen AES) | Salattu lyhyemmällä avaimella. Useimmille käyttötapauksille turvallinen, mutta 256-bittinen on suositeltu arkaluontoiseen dataan. | . | 🔓 | Oletus / avoin | Käyttää tunnettua oletusavainta. Kaikki Meshtastic-radiot samalla esiasetuksella voivat lukea nämä viestit. | . | ⚠️ | Turvaton + sijainti | Avoin kanava, joka lähettää myös GPS-sijaintisi. Käytä varoen julkisissa verkoissa. | . 🔒 Tietoturvavinkki: Käytä aina yksilöllistä PSK-avainta yksityiseen viestintään. 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 . | Siirry kohtaan Asetukset → Kanavat. | Napauta Lisää kanava tai skannaa QR-koodi. | Määritä kanavan nimi ja salausavain. | Jaa kanavan URL tai QR-koodi muille, jotka tarvitsevat pääsyn. | . Napauttamalla kanavaa näet sen tiedot ja jakovaihtoehdot. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/messages-and-channels.html#kanavat", - - "relUrl": "/fi-rFI/user/messages-and-channels.html#kanavat" - },"2670": { - "doc": "Viestit ja kanavat", - "title": "Yksityisviestit", - "content": "Yksityisviestit (DM) ovat kahden radion välistä päästä päähän salattua viestintää. Yksityisviestin lähettäminen . | Avaa Viestit-välilehti. | Valitse radion yhteystiedoista tai napauta radiota radiolistasta. | Kirjoita viesti ja napauta Lähetä. | . 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 siirretty radiolle, mutta lopullista tilaa ei ole vielä vahvistettu (jonossa ja lähetetään näyttävät molemmat tämän saman tekstin) | . | 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 | Toimitus epäonnistui — napauta tilaa nähdäksesi tarkemman syyn (katso alla kohta 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. | . | Hylkäyskuittaus vastaanotettu (NAK) | Seuraavan hypyn radio kieltäytyi välittämästä | Välittäjä-radio voi olla ruuhkautunut. Odota ja yritä uudelleen. | . | Aikakatkaisu | Ei kuittausta uudelleenyritysten aikana | Vastaanottaja voi olla kantaman ulkopuolella. Yritä nostaa hyppyrajaa tai siirtyä parempaan paikkaan. | . | 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 | Uudelleenyritysten enimmäismäärä saavutettu | Siirry lähemmäs, paranna signaalia tai odota, että mesh-verkon olosuhteet paranevat. | . | 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. Jos “Ei reittiä” -virhe toistuu, tarkista että välissä olevat reitittävät radiot ovat verkossa. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/messages-and-channels.html#yksityisviestit", - - "relUrl": "/fi-rFI/user/messages-and-channels.html#yksityisviestit" - },"2671": { - "doc": "Viestit ja kanavat", - "title": "Viestiominaisuudet", - "content": "Pikachatti . Valmiiksi määritetyt viestit nopeaan viestintään: . | Käytettävissä viestikentän Pikachatti-painikkeen kautta | Valitse valmiista sisäänrakennetuista viesteistä tai omista viesteistä | Muokkaa pikachatti-viestejä kohdassa Asetukset → Pikachatti | Hyödyllinen, kun kirjoittaminen on hankalaa (hanskat, pieni näyttö, kiire) | . Jokaisella pikaviestillä on lyhyt Nimi (painikkeen teksti), lisättävä Viesti sekä Lähetä heti -kytkin. Kun se on käytössä, painikkeen napauttaminen lähettää viestin välittömästi sen sijaan, että se lisättäisiin muokattavaksi syöttökenttään: . Kanavalista näyttää jokaisen kanavan ja sen viimeisimmän viestin esikatselun. 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 luonnoksen muotoilu näkyy kentässä, vaikka taustalla oleva teksti säilyttää 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: . | Pitkä painallus viestissä avaa toimintovalikon | Napauta Lisää reaktio valitaksesi 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. Viestitoiminnot . Pitkä painallus missä tahansa viestissä avaa: . | Kopioi — kopioi viestin teksti leikepöydälle | Vastaa — lainaa viesti vastaukseesi | Reagoi — lisää emoji-reaktio | Käännä — kääntää vastaanotetun viestin laitteesi kielelle ja mahdollistaa vaihtamisen alkuperäisen ja käännetyn tekstin välillä (vain Google Play -versiossa; käyttää laitteella toimivaa käännöstä) | Poista — poista lähettämäsi viesti (paikallinen poisto) | . Viestien prioriteetti . Viestit jonotetaan ja lähetetään prioriteetin mukaan: . | Hätä ja hälytysviestit (korkein) | Suoraviestit | Kanavaviestit (alin prioriteetti) | . Viestirajoitukset . | Enimmäispituus: 200 tavua (noin 200 merkkiä ASCII-tekstille) | 200 tavun rajoitus koskee vain sovelluksen viestinkirjoituskenttää. Mesh-verkon viestin enimmäiskoko on noin 233 tavua, joten muilta lähettäjiltä (esimerkiksi sovellustoiminnoista tai Android Autosta) tulevat viestit voivat olla hieman pidempiä | 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" - },"2672": { - "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" - },"2673": { - "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" - },"2674": { - "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" - },"2675": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Descrición | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html#channels", - - "relUrl": "/gl-rES/user/messages-and-channels.html#channels" - },"2676": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2677": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2678": { - "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" - },"2679": { - "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" - },"2680": { - "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" - },"2681": { - "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" - },"2682": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Безпека каналу . Channels support multiple encryption levels: . | Icon | Security Level | Опис | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "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#канали" - },"2683": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Таймаут | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2684": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2685": { - "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" - },"2686": { - "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" - },"2687": { - "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" - },"2688": { "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" - },"2689": { + },"2600": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Kanalsicherheit . Channels support multiple encryption levels: . | Symbol | Security Level | Beschreibung | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", "url": "/Meshtastic-Android/main/de-rDE/user/messages-and-channels.html#kan%C3%A4le", "relUrl": "/de-rDE/user/messages-and-channels.html#kanäle" - },"2690": { + },"2601": { "doc": "Messages & Channels", "title": "Direktnachrichten", "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Zeitlimit erreicht | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2691": { + },"2602": { "doc": "Messages & Channels", "title": "Message Features", "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Jeder Quick-Chat-Eintrag besteht aus einem kurzen Namen (der Schaltflächenbeschriftung), der einzufügenden Nachricht und einer Option zum Sofortigen Senden: Ist diese aktiviert, wird die Nachricht beim Tippen auf die Schaltfläche sofort versendet, anstatt zur Bearbeitung in das Eingabefeld eingefügt zu werden. The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2692": { + },"2603": { "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" - },"2693": { + },"2604": { "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" - },"2694": { + },"2605": { "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" - },"2695": { + },"2606": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#messages--channels", - "relUrl": "/hr-rHR/user/messages-and-channels.html#messages--channels" - },"2696": { + "relUrl": "/ca-rES/user/messages-and-channels.html#messages--channels" + },"2607": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Opis | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/messages-and-channels.html#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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Descripció | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#channels", - "relUrl": "/hr-rHR/user/messages-and-channels.html#channels" - },"2697": { + "relUrl": "/ca-rES/user/messages-and-channels.html#channels" + },"2608": { "doc": "Messages & Channels", "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Temps esgotat | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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": "/hr-rHR/user/messages-and-channels.html#direct-messages" - },"2698": { + "relUrl": "/ca-rES/user/messages-and-channels.html#direct-messages" + },"2609": { "doc": "Messages & Channels", "title": "Message Features", "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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", + "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#message-features", - "relUrl": "/hr-rHR/user/messages-and-channels.html#message-features" - },"2699": { + "relUrl": "/ca-rES/user/messages-and-channels.html#message-features" + },"2610": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#best-practices", - "relUrl": "/hr-rHR/user/messages-and-channels.html#best-practices" - },"2700": { + "relUrl": "/ca-rES/user/messages-and-channels.html#best-practices" + },"2611": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#related-topics", - "relUrl": "/hr-rHR/user/messages-and-channels.html#related-topics" - },"2701": { + "relUrl": "/ca-rES/user/messages-and-channels.html#related-topics" + },"2612": { "doc": "Messages & Channels", "title": "Messages & Channels", "content": " ", - "url": "/Meshtastic-Android/main/hr-rHR/user/messages-and-channels.html", + "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html", - "relUrl": "/hr-rHR/user/messages-and-channels.html" - },"2702": { - "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" - },"2703": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Aprašymas | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/messages-and-channels.html#channels", - - "relUrl": "/lt-rLT/user/messages-and-channels.html#channels" - },"2704": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Klaida | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Baigėsi laikas | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2705": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2706": { - "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" - },"2707": { - "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" - },"2708": { - "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" - },"2709": { - "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" - },"2710": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Description | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/en/user/messages-and-channels.html#channels", - - "relUrl": "/en/user/messages-and-channels.html#channels" - },"2711": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2712": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2713": { - "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" - },"2714": { - "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" - },"2715": { - "doc": "Messages & Channels", - "title": "Messages & Channels", - "content": " ", - "url": "/Meshtastic-Android/main/en/user/messages-and-channels.html", - - "relUrl": "/en/user/messages-and-channels.html" - },"2716": { - "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" - },"2717": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Csatorna biztonság . Channels support multiple encryption levels: . | Icon | Security Level | Leírás | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html#csatorn%C3%A1k", - - "relUrl": "/hu-rHU/user/messages-and-channels.html#csatornák" - },"2718": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Hiba | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Időtúllépés | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2719": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2720": { - "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" - },"2721": { - "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" - },"2722": { - "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" - },"2723": { - "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#съобщения--канали" - },"2724": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Сигурност на канала . Channels support multiple encryption levels: . | Икона | Security Level | Описание | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "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#канали" - },"2725": { - "doc": "Съобщения & Канали", - "title": "Директни съобщения", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Грешка | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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#директни-съобщения" - },"2726": { - "doc": "Съобщения & Канали", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2727": { - "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#най-добри-практики" - },"2728": { - "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" - },"2729": { - "doc": "Съобщения & Канали", - "title": "Съобщения & Канали", - "content": " ", - "url": "/Meshtastic-Android/main/bg-rBG/user/messages-and-channels.html", - - "relUrl": "/bg-rBG/user/messages-and-channels.html" - },"2730": { - "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" - },"2731": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Opis | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/messages-and-channels.html#channels", - - "relUrl": "/sl-rSI/user/messages-and-channels.html#channels" - },"2732": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Napaka | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Časovna omejitev | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2733": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2734": { - "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" - },"2735": { - "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" - },"2736": { - "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" - },"2737": { - "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" - },"2738": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Descrição | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/messages-and-channels.html#canal", - - "relUrl": "/pt-rPT/user/messages-and-channels.html#canal" - },"2739": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erros | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2740": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2741": { - "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" - },"2742": { - "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" - },"2743": { - "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" - },"2744": { + "relUrl": "/ca-rES/user/messages-and-channels.html" + },"2613": { "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" - },"2745": { + },"2614": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Апісанне | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", "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#каналы" - },"2746": { + },"2615": { "doc": "Messages & Channels", "title": "Direct Messages", "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Памылка | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Скончыўся час чакання | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2747": { + },"2616": { "doc": "Messages & Channels", "title": "Message Features", "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2748": { + },"2617": { "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" - },"2749": { + },"2618": { "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" - },"2750": { + },"2619": { "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" - },"2751": { + },"2620": { + "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" + },"2621": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Безпека каналу . Channels support multiple encryption levels: . | Icon | Security Level | Опис | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "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#канали" + },"2622": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Таймаут | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2623": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2624": { + "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" + },"2625": { + "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" + },"2626": { + "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" + },"2627": { + "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" + },"2628": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. 频道安全 . Channels support multiple encryption levels: . | 图标 | Security Level | 说明 | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "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#频道" + },"2629": { + "doc": "Messages & Channels", + "title": "私聊", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | 超时 | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | 发送至MESH失败 | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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#私聊" + },"2630": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2631": { + "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" + },"2632": { + "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" + },"2633": { + "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" + },"2634": { + "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#съобщения--канали" + },"2635": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Сигурност на канала . Channels support multiple encryption levels: . | Икона | Security Level | Описание | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "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#канали" + },"2636": { + "doc": "Съобщения & Канали", + "title": "Директни съобщения", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Грешка | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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#директни-съобщения" + },"2637": { + "doc": "Съобщения & Канали", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2638": { + "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#най-добри-практики" + },"2639": { + "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" + },"2640": { + "doc": "Съобщения & Канали", + "title": "Съобщения & Канали", + "content": " ", + "url": "/Meshtastic-Android/main/bg-rBG/user/messages-and-channels.html", + + "relUrl": "/bg-rBG/user/messages-and-channels.html" + },"2641": { + "doc": "訊息與頻道", + "title": "訊息與頻道", + "content": "Meshtastic 支援兩種通訊模式：頻道廣播與私訊。 . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/messages-and-channels.html", + + "relUrl": "/zh-rTW/user/messages-and-channels.html" + },"2642": { + "doc": "訊息與頻道", + "title": "頻道", + "content": "頻道是共享的通訊群組。 所有設定相同頻道金鑰的節點均可在該頻道上讀取與傳送訊息。 . 預設頻道 . 每台 Meshtastic 裝置均內建預設的 LongFast 頻道。 此為未加密頻道，供一般 mesh 網路通訊使用。 . 頻道安全性 . 頻道支援多種加密等級： . | 圖示 | 安全等級 | 描述說明 | . | 🔒 | PSK（256 位元 AES） | 使用強力預共享金鑰進行完整加密。 僅持有相符金鑰的節點可讀取訊息。 | . | 🔐 | PSK（128 位元 AES） | 使用較短的金鑰進行加密。 適用於大多數情境，但敏感資料建議使用 256 位元加密。 | . | 🔓 | 預設／開放 | 使用眾所周知的預設金鑰。 使用相同預設值的任何 Meshtastic 裝置均可讀取這些訊息。 | . | ⚠️ | 不安全 + 位置 | 開放頻道，同時廣播您的 GPS 位置。 在公開 mesh 網路中使用時請謹慎。 | . 🔒 安全提示：私人通訊請務必設定專屬的 PSK。 預設頻道刻意設計為開放，以便新使用者能探索 mesh 網路 — 但對於任何敏感內容，請另行建立獨立的加密頻道。 . 新增頻道 . | 前往「設定 → 頻道」。 | 點選「新增頻道」或掃描 QR Code。 | 設定頻道名稱與加密金鑰。設定頻道名稱與加密金鑰。 | 將頻道網址或 QR Code 分享給需要加入的人。 | . 點選頻道可查看其詳細資訊與分享選項。 . ", + "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#頻道" + },"2643": { + "doc": "訊息與頻道", + "title": "私訊", + "content": "私訊（DM）是兩個特定節點之間的點對點加密通訊。 . 傳送私訊 . | 開啟「訊息」頁籤。 | 從聯絡人清單中選取節點，或在節點清單中點選節點。 | 輸入訊息後點選「傳送」。 | . 訊息狀態 . 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 (queued and en-route both show this same text) | . | 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 below) | . 傳遞錯誤 . 當訊息傳遞失敗時，錯誤指示器將顯示問題原因： . | 錯誤 | 含義 | 處理方式 | . | 無路由 | 無法找到通往目標節點的路徑 | 收件者可能已離線或超出 mesh 網路範圍。 請稍後再試，或靠近對方後重新傳送。 | . | 收到 NAK | 下一個跳躍點節點拒絕轉送 | 中繼節點可能發生壅塞。 請稍候後重試。 | . | Timeout - 超時 | 在重試時間內未收到確認回應 | 收件者可能剛好超出訊號範圍。 請嘗試提高跳躍限制，或移動至訊號較佳的位置。 | . | No radio interface | 無可用的無線電介面進行傳送 | Check that your radio is connected and available. | . | Failed to deliver to mesh | 所有重試次數均已用盡 | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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 網路將自動重試。 若持續出現「無路由」錯誤，請確認中間的路由器節點是否在線。 . ", + "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#私訊" + },"2644": { + "doc": "訊息與頻道", + "title": "訊息功能", + "content": "快速聊天 . 預先設定的訊息，可快速進行通訊： . | 透過訊息輸入區的快速聊天按鈕開啟 | 從內建短語或自訂訊息中選取 | 在「設定 → 快速聊天」中自訂快速聊天訊息 | 適用於不便打字的情況（戴手套、螢幕過小、緊急狀況） | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . 頻道清單會顯示每個頻道及其最新訊息預覽。 . 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 draft styles live in the field while the underlying text keeps its 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. 訊息回應 . 以表情符號對訊息作出回應： . | 長按訊息以開啟動作選單 | 點選「新增回應」以選擇表情符號 | 訊息回應顯示於訊息泡泡下方 | 多位使用者可對同一則訊息作出回應 | 可對自己或他人的訊息作出回應 | . 💡 提示：訊息回應非常輕量 — 相較於完整文字訊息，佔用極少的 mesh 網路頻寬。 . 訊息動作 . 長按任意訊息可使用以下功能： . | 複製 — 將訊息文字複製至剪貼簿 | 回覆 — 在回覆中引用該訊息 | 回應 — 新增表情符號回應 | 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) | 刪除 — 移除您傳送的訊息（僅限本機刪除） | . 訊息優先順序 . 訊息依優先順序排入佇列並傳送： . | 緊急／警示訊息（最高） | 私訊 | 頻道廣播（最低） | . 訊息限制 . | 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 or Android Auto) 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#訊息功能" + },"2645": { + "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#最佳實踐" + },"2646": { + "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#相關主題" + },"2647": { + "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" + },"2648": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Иконица | Security Level | Опис | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "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#канали" + },"2649": { + "doc": "Messages & Channels", + "title": "Директне поруке", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Isteklo vreme | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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#директне-поруке" + },"2650": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2651": { + "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" + },"2652": { + "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" + },"2653": { + "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" + },"2654": { + "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" + },"2655": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Zabezpečení kanálu . Channels support multiple encryption levels: . | Icon | Security Level | Popis | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/messages-and-channels.html#kan%C3%A1ly", + + "relUrl": "/cs-rCZ/user/messages-and-channels.html#kanály" + },"2656": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Chyba | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Vypršel čas spojení | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Nepodařilo se doručit do mesh sítě | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2657": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2658": { + "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" + },"2659": { + "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" + },"2660": { + "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" + },"2661": { + "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" + },"2662": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Description | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/en/user/messages-and-channels.html#channels", + + "relUrl": "/en/user/messages-and-channels.html#channels" + },"2663": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2664": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2665": { + "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" + },"2666": { + "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" + },"2667": { + "doc": "Messages & Channels", + "title": "Messages & Channels", + "content": " ", + "url": "/Meshtastic-Android/main/en/user/messages-and-channels.html", + + "relUrl": "/en/user/messages-and-channels.html" + },"2668": { + "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" + },"2669": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Opis | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/messages-and-channels.html#channels", + + "relUrl": "/sl-rSI/user/messages-and-channels.html#channels" + },"2670": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Napaka | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Časovna omejitev | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2671": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2672": { + "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" + },"2673": { + "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" + },"2674": { + "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" + },"2675": { + "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" + },"2676": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Sicurezza del canale . Channels support multiple encryption levels: . | Icon | Security Level | Descrizione | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/it-rIT/user/messages-and-channels.html#canali", + + "relUrl": "/it-rIT/user/messages-and-channels.html#canali" + },"2677": { + "doc": "Messages & Channels", + "title": "Messaggi Diretti", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Errori | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Consegna alla mesh non riuscita | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2678": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2679": { + "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" + },"2680": { + "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" + },"2681": { + "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" + },"2682": { "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" - },"2752": { + },"2683": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Segurança do Canal . Channels support multiple encryption levels: . | Icon | Security Level | Descrição | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", "url": "/Meshtastic-Android/main/pt-rBR/user/messages-and-channels.html#canais", "relUrl": "/pt-rBR/user/messages-and-channels.html#canais" - },"2753": { + },"2684": { "doc": "Messages & Channels", "title": "Direct Messages", "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Tempo esgotado | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2754": { + },"2685": { "doc": "Messages & Channels", "title": "Message Features", "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2755": { + },"2686": { "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" - },"2756": { + },"2687": { "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" - },"2757": { + },"2688": { "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" - },"2758": { + },"2689": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#messages--channels", - "relUrl": "/el-rGR/user/messages-and-channels.html#messages--channels" - },"2759": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Περιγραφή | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "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#κανάλια" - },"2760": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Σφάλμα | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Λήξη χρονικού ορίου | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2761": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2762": { - "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" - },"2763": { - "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" - },"2764": { - "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" - },"2765": { - "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" - },"2766": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Seguridad del canal . Channels support multiple encryption levels: . | Icon | Security Level | Descripción | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html#canales", - - "relUrl": "/es-rES/user/messages-and-channels.html#canales" - },"2767": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Tiempo agotado | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2768": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2769": { - "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" - },"2770": { - "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" - },"2771": { - "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" - },"2772": { - "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" - },"2773": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Açıklaması | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html#kanallar", - - "relUrl": "/tr-rTR/user/messages-and-channels.html#kanallar" - },"2774": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Hata | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Zaman Aşımı | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2775": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2776": { - "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" - },"2777": { - "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" - },"2778": { - "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" - },"2779": { - "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" - },"2780": { + "relUrl": "/is-rIS/user/messages-and-channels.html#messages--channels" + },"2690": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Beskrivelse | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/no-rNO/user/messages-and-channels.html#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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Lýsing | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#channels", - "relUrl": "/no-rNO/user/messages-and-channels.html#channels" - },"2781": { + "relUrl": "/is-rIS/user/messages-and-channels.html#channels" + },"2691": { "doc": "Messages & Channels", "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Feil | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Tidsavbrudd | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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": "/no-rNO/user/messages-and-channels.html#direct-messages" - },"2782": { + "relUrl": "/is-rIS/user/messages-and-channels.html#direct-messages" + },"2692": { "doc": "Messages & Channels", "title": "Message Features", "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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", + "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#message-features", - "relUrl": "/no-rNO/user/messages-and-channels.html#message-features" - },"2783": { + "relUrl": "/is-rIS/user/messages-and-channels.html#message-features" + },"2693": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#best-practices", - "relUrl": "/no-rNO/user/messages-and-channels.html#best-practices" - },"2784": { + "relUrl": "/is-rIS/user/messages-and-channels.html#best-practices" + },"2694": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#related-topics", - "relUrl": "/no-rNO/user/messages-and-channels.html#related-topics" - },"2785": { + "relUrl": "/is-rIS/user/messages-and-channels.html#related-topics" + },"2695": { "doc": "Messages & Channels", "title": "Messages & Channels", "content": " ", - "url": "/Meshtastic-Android/main/no-rNO/user/messages-and-channels.html", + "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html", - "relUrl": "/no-rNO/user/messages-and-channels.html" - },"2786": { + "relUrl": "/is-rIS/user/messages-and-channels.html" + },"2696": { + "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" + },"2697": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Sécurité du canal . Channels support multiple encryption levels: . | Icon | Security Level | Description | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/messages-and-channels.html#canaux", + + "relUrl": "/fr-rFR/user/messages-and-channels.html#canaux" + },"2698": { + "doc": "Messages & Channels", + "title": "Messages directs", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erreur | Meaning | What to Do | . | Pas de route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Délai d’expiration | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2699": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2700": { + "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" + },"2701": { + "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" + },"2702": { + "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" + },"2703": { + "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" + },"2704": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Иконица | Security Level | Опис | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "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#канали" + },"2705": { + "doc": "Messages & Channels", + "title": "Директне поруке", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Временско ограничење | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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#директне-поруке" + },"2706": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2707": { + "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" + },"2708": { + "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" + },"2709": { + "doc": "Messages & Channels", + "title": "Messages & Channels", + "content": " ", + "url": "/Meshtastic-Android/main/srp/user/messages-and-channels.html", + + "relUrl": "/srp/user/messages-and-channels.html" + },"2710": { + "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" + },"2711": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Popis | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/messages-and-channels.html#kan%C3%A1le", + + "relUrl": "/sk-rSK/user/messages-and-channels.html#kanále" + },"2712": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Chyba | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Časový limit | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2713": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2714": { + "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" + },"2715": { + "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" + },"2716": { + "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" + },"2717": { + "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" + },"2718": { + "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-laitteessa on oletuksena LongFast-kanava. Tämä on salaamaton kanava yleiseen mesh-viestintään. Kanavan turvallisuus . Kanavat tukevat useita salaustasoja: . | Ikoni | Suojaustaso | Kuvaus | . | 🔒 | PSK (256-bittinen AES) | Täysin salattu vahvalla esijaetulla avaimella. Vain samaa avainta käyttävät radiot voivat lukea viestejä. | . | 🔐 | PSK (128-bittinen AES) | Salattu lyhyemmällä avaimella. Useimmille käyttötapauksille turvallinen, mutta 256-bittinen on suositeltu arkaluontoiseen dataan. | . | 🔓 | Oletus / avoin | Käyttää tunnettua oletusavainta. Kaikki Meshtastic-radiot samalla esiasetuksella voivat lukea nämä viestit. | . | ⚠️ | Turvaton + sijainti | Avoin kanava, joka lähettää myös GPS-sijaintisi. Käytä varoen julkisissa verkoissa. | . 🔒 Tietoturvavinkki: Käytä aina yksilöllistä PSK-avainta yksityiseen viestintään. 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 . | Siirry kohtaan Asetukset → Kanavat. | Napauta Lisää kanava tai skannaa QR-koodi. | Määritä kanavan nimi ja salausavain. | Jaa kanavan URL tai QR-koodi muille, jotka tarvitsevat pääsyn. | . Napauttamalla kanavaa näet sen tiedot ja jakovaihtoehdot. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/messages-and-channels.html#kanavat", + + "relUrl": "/fi-rFI/user/messages-and-channels.html#kanavat" + },"2719": { + "doc": "Viestit ja kanavat", + "title": "Yksityisviestit", + "content": "Yksityisviestit (DM) ovat kahden radion välistä päästä päähän salattua viestintää. Yksityisviestin lähettäminen . | Avaa Viestit-välilehti. | Valitse radion yhteystiedoista tai napauta radiota radiolistasta. | Kirjoita viesti ja napauta Lähetä. | . 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 siirretty radiolle, mutta lopullista tilaa ei ole vielä vahvistettu (jonossa ja lähetetään näyttävät molemmat tämän saman tekstin) | . | 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 | Toimitus epäonnistui — napauta tilaa nähdäksesi tarkemman syyn (katso alla kohta 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. | . | Hylkäyskuittaus vastaanotettu (NAK) | Seuraavan hypyn radio kieltäytyi välittämästä | Välittäjä-radio voi olla ruuhkautunut. Odota ja yritä uudelleen. | . | Aikakatkaisu | Ei kuittausta uudelleenyritysten aikana | Vastaanottaja voi olla kantaman ulkopuolella. Yritä nostaa hyppyrajaa tai siirtyä parempaan paikkaan. | . | 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 | Uudelleenyritysten enimmäismäärä saavutettu | Siirry lähemmäs, paranna signaalia tai odota, että mesh-verkon olosuhteet paranevat. | . | 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. Jos “Ei reittiä” -virhe toistuu, tarkista että välissä olevat reitittävät radiot ovat verkossa. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/messages-and-channels.html#yksityisviestit", + + "relUrl": "/fi-rFI/user/messages-and-channels.html#yksityisviestit" + },"2720": { + "doc": "Viestit ja kanavat", + "title": "Viestiominaisuudet", + "content": "Pikachatti . Valmiiksi määritetyt viestit nopeaan viestintään: . | Käytettävissä viestikentän Pikachatti-painikkeen kautta | Valitse valmiista sisäänrakennetuista viesteistä tai omista viesteistä | Muokkaa pikachatti-viestejä kohdassa Asetukset → Pikachatti | Hyödyllinen, kun kirjoittaminen on hankalaa (hanskat, pieni näyttö, kiire) | . Jokaisella pikaviestillä on lyhyt Nimi (painikkeen teksti), lisättävä Viesti sekä Lähetä heti -kytkin. Kun se on käytössä, painikkeen napauttaminen lähettää viestin välittömästi sen sijaan, että se lisättäisiin muokattavaksi syöttökenttään: . Kanavalista näyttää jokaisen kanavan ja sen viimeisimmän viestin esikatselun. 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 luonnoksen muotoilu näkyy kentässä, vaikka taustalla oleva teksti säilyttää 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: . | Pitkä painallus viestissä avaa toimintovalikon | Napauta Lisää reaktio valitaksesi 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. Viestitoiminnot . Pitkä painallus missä tahansa viestissä avaa: . | Kopioi — kopioi viestin teksti leikepöydälle | Vastaa — lainaa viesti vastaukseesi | Reagoi — lisää emoji-reaktio | Käännä — kääntää vastaanotetun viestin laitteesi kielelle ja mahdollistaa vaihtamisen alkuperäisen ja käännetyn tekstin välillä (vain Google Play -versiossa; käyttää laitteella toimivaa käännöstä) | Poista — poista lähettämäsi viesti (paikallinen poisto) | . Viestien prioriteetti . Viestit jonotetaan ja lähetetään prioriteetin mukaan: . | Hätä ja hälytysviestit (korkein) | Suoraviestit | Kanavaviestit (alin prioriteetti) | . Viestirajoitukset . | Enimmäispituus: 200 tavua (noin 200 merkkiä ASCII-tekstille) | 200 tavun rajoitus koskee vain sovelluksen viestinkirjoituskenttää. Mesh-verkon viestin enimmäiskoko on noin 233 tavua, joten muilta lähettäjiltä (esimerkiksi sovellustoiminnoista tai Android Autosta) tulevat viestit voivat olla hieman pidempiä | 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" + },"2721": { + "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" + },"2722": { + "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" + },"2723": { "doc": "Сообщения и каналы", "title": "Сообщения и каналы", "content": "Meshtastic поддерживает два режима связи: вещание по каналам и личные сообщения. ", "url": "/Meshtastic-Android/main/ru-rRU/user/messages-and-channels.html", "relUrl": "/ru-rRU/user/messages-and-channels.html" - },"2787": { + },"2724": { "doc": "Сообщения и каналы", "title": "Каналы", "content": "Каналы - это общие группы для связи. Все узлы, настроенные с одинаковым ключом канала, могут читать и отправлять сообщения в этом канале. Канал по умолчанию . Каждое устройство Meshtastic имеет канал LongFast по умолчанию. Это незашифрованный канал, используемый для общей связи в ячеистой сети. Безопасность канала . Каналы поддерживают несколько уровней шифрования: . | Иконка | Уровень безопасности | Описание | . | 🔒 | PSK (256-bit AES) | Полностью зашифрован надёжным предварительно согласованным ключом. Только узлы с соответствующим ключом могут читать сообщения. | . | 🔐 | PSK (128-bit AES) | Зашифрован более коротким ключом. Безопасен для большинства задач, но 256-битное шифрование предпочтительнее для конфиденциальных данных. | . | 🔓 | По умолчанию / Открытый | Использует общеизвестный ключ по умолчанию. Любое устройство Meshtastic с той же пред установкой может читать эти сообщения. | . | ⚠️ | Незащищённый + Местоположение | Открытый канал, который также передаёт ваше GPS-местоположение. Используйте с осторожностью в общественных ячеистых сетях. | . 🔒 Совет по безопасности: Всегда настраивайте уникальный PSK для личных сообщений. Канал по умолчанию намеренно открыт, чтобы новые пользователи могли обнаружить mesh-сеть — но вам следует создать отдельный зашифрованный канал для любой конфиденциальной информации. Добавление канала . | Перейдите в Настройки → Каналы. | Нажмите Добавить канал или сканируйте QR-код. | Настройте имя канала и ключ шифрования. | Поделитесь URL-адресом/QR-кодом канала с теми, кому нужен доступ. | . При нажатии на канал отображаются его сведения и опции для отправки приглашения. ", "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#каналы" - },"2788": { + },"2725": { "doc": "Сообщения и каналы", "title": "Личные сообщения", "content": "Личные сообщения (DMs) — это зашифрованная связь точка - к - точке между двумя конкретными узлами. Отправка личного сообщения . | Откройте вкладку Сообщения. | Выберите ноду из списка контактов или нажмите на ноду в списке нод. | Введите сообщение и нажмите “Отправить”. | . Состояние сообщения . Метка статуса отображается только под твоими исходящими сообщениями (входящие сообщения от других не имеют метки статуса): . | Состояние | Значение | . | Отправка… | В очереди или уже передано на радио, результат ещё не определён (для статусов “в очереди” и “в пути»” отображается одинаковый текст) | . | Доставлено получателю | Самое надёжное подтверждение для личного сообщения — получено подтверждение о доставке | . | Отправлено в сеть | Для широковещательного сообщения в канале — сообщение достигло mesh-сети (у широковещательных сообщений нет подтверждений для каждого получателя) | . | Передано, не подтверждено получателем | Для личного сообщения, отображается предупреждающим цветом — сообщение было ретранслировано, но подтверждение ещё не получено | . | Маршрутизация по SF++ цепочке… | Находится в процессе маршрутизации/буферизации в цепочке Store & Forward Plus Plus | . | Подтверждено в цепочке SF++ | Подтверждена доставка через цепочку SF++ | . | Ошибки | Ошибка доставки — нажмите на статус, чтобы узнать конкретную причину (см. раздел «Ошибки доставки» ниже) | . Ошибки доставки . Когда сообщение не удаётся доставить, индикатор ошибки показывает, что пошло не так: . | Ошибки | Значение | Что делать | . | Нет маршрута | Путь к целевой ноде отсутствует | Получатель может быть не в сети или вне зоны действия mesh-сети. Повторите попытку позже или подойдите ближе. | . | Получен NAK | Следующая нода отказалась ретранслировать | Ретранслирующая нода может быть перегружена. Подождите и повторите попытку. | . | Время ожидания истекло | Нет подтверждения в пределах окна повторных попыток | Получатель, возможно, находится сразу за пределами зоны досягаемости. Попробуйте увеличить лимит хопов или переместиться в место с лучшим сигналом. | . | No radio interface | Нет доступного радиоинтерфейса для отправки | Check that your radio is connected and available. | . | Не удалось доставить в сеть | Все попытки повторной отправки исчерпаны | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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. | . 💡 Совет: Большинство ошибок доставки разрешаются сами собой. Если нода доступна с перебоями, mesh-сеть будет повторять попытки. При постоянных ошибках «Нет маршрута» проверьте, что промежуточные ноды-роутеры находятся в сети. ", "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#личные-сообщения" - },"2789": { + },"2726": { "doc": "Сообщения и каналы", "title": "Функции сообщений", "content": "Быстрый чат . Заранее подготовленные сообщения для быстрой связи: . | Доступ через кнопку “Быстрый чат” в области ввода сообщения | Выберите из встроенных фраз или собственных сообщений | Настройте сообщения быстрого чата в Настройки → Быстрый чат | Полезно, когда набирать текст неудобно (перчатки, маленький экран, срочность) | . Каждая запись быстрого чата имеет короткое Имя (надпись на кнопке), Сообщение, которое она вставляет, и переключатель “Отправить сразу” — когда он включён, нажатие кнопки немедленно отправляет сообщение, а не помещает его в поле ввода для редактирования: . Список каналов показывает каждый канал с предпросмотром последнего сообщения. Поиск сообщений . Ты можешь искать по всей истории любой переписки прямо на экране чата: . | Откройте переписку (канал или личное сообщение). | Нажмите значок поиска в верхней панели. | Введите текст в поле “Поиск сообщений…”. Поиск выполняется по мере твоего ввода по всем сохранённым сообщениям в этой переписке. | Используйте счётчик результатов N / M и стрелки вперёд / назад для перехода между совпадениями, которые подсвечиваются в переписке. | . 💡 Совет: Поиск полнотекстовый и ограничивается перепиской, из которого ты его открыл — он не ищет по другим каналам или контактам. Он сопоставляет текст с сообщениями, уже сохранёнными на твоём устройстве, поэтому работает полностью офлайн. Пузырьки сообщения . Сообщения отображаются в виде пузырьков чата — отправленные справа, полученные слева. В каждом пузырьке отображаются отправитель, время и статус доставки. Сообщения с ответами содержат цитируемый предпросмотр исходного сообщения над ответом. Форматирование текста . Сообщения поддерживают облегчённую встроенную разметку Markdown. Полученные сообщения отображают оформление со скрытыми символами синтаксиса: . | Тип | Синтаксис | Отображается как | . | Жирный | **жирный** | жирный | . | Курсив | *курсив* | курсив | . | Зачёркнутый | ~~зачёркнутый~~ | зачёркнутый | . | Встроенный код | `код` | моноширинный код | . | Ссылка | [текст](https://example.com) | нажимаемая ссылка | . При создании сообщения установите фокус на поле ввода и введите не менее трёх символов — под полем появится панель форматирования. Выделите текст и нажмите на стиль, чтобы применить его (повторное нажатие убирает форматирование); если текст не выделен, будет вставлена пустая пара символов разметки, а курсор окажется между ними. Кнопка вставки ссылки открывает диалог для ввода URL-адреса. В процессе твоего набора черновые стили отображаются в поле, но в самом тексте сохраняются символы Markdown. 💡 Совет: Форматирование передаётся по mesh-сети как есть — теми же байтами, что и iOS. Клиенты, не поддерживающие Markdown (старые приложения, простые клиенты на прошивке), отобразят сырые символы **/~~. URL-адреса, адреса электронной почты и номера телефонов всё равно автоматически становятся ссылками независимо от того, используете ли вы Markdown. Упоминания . Введите @ при написании сообщения, чтобы упомянуть ноду — по мере твоего ввода будет появляться список подходящих контактов. В полученном сообщении упоминание отображается как выделенный элемент с именем ноды; нажмите на него, чтобы сразу перейти на страницу сведений о ноде. Реакции . Реагируйте на сообщения с помощью эмодзи: . | Нажмите и удерживайте сообщение, чтобы открыть меню действий | Нажмите “Добавить реакцию”, чтобы выбрать эмодзи | Реакции появляются под пузырьком сообщения | Несколько пользователей могут отреагировать на одно и то же сообщение | Реагируйте на свои сообщения или сообщения других | . 💡 Совет: Реакции очень лёгкие — они потребляют гораздо меньше трафика mesh-сети по сравнению с полными текстовыми сообщениями. Действия с сообщениями . Нажмите и удерживайте любое сообщение, чтобы получить доступ к: . | Копировать — скопировать текст сообщения в буфер обмена | Ответить — процитировать сообщение в твоём ответе | Реагировать — добавить реакцию-эмодзи | Перевести — перевести полученное сообщение на язык твоего устройства и переключаться между оригиналом и переводом (только в сборке Google Play; используется встроенный перевод) | Удалить — удалить отправленное тобою сообщение (локальное удаление) | . Приоритет сообщений . Сообщения ставятся в очередь и передаются в соответствии с приоритетом: . | Экстренные/аварийные сообщения (наивысший) | Личные сообщения | Широковещательные сообщения в канале (самый низкий) | . Ограничения сообщений . | Максимальная длина: 200 байт (примерно 200 символов для текста в ASCII) | Ограничение в 200 байт применяется к встроенному редактору сообщений — сам лимит полезной нагрузки в mesh-сети составляет ~233 байта, поэтому сообщения от других отправителей (например, App Functions или Android Auto) могут быть немного длиннее | Ограничение скорости: 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#функции-сообщений" - },"2790": { + },"2727": { "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#рекомендации" - },"2791": { + },"2728": { "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#связанные-темы" + },"2729": { + "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" + },"2730": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | 설명 | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "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#채널" + },"2731": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | 시간 초과 | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2732": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2733": { + "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" + },"2734": { + "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" + },"2735": { + "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" + },"2736": { + "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" + },"2737": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Opis | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/messages-and-channels.html#channels", + + "relUrl": "/hr-rHR/user/messages-and-channels.html#channels" + },"2738": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2739": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2740": { + "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" + },"2741": { + "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" + },"2742": { + "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" + },"2743": { + "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" + },"2744": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Përshkrimi | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/messages-and-channels.html#channels", + + "relUrl": "/sq-rAL/user/messages-and-channels.html#channels" + },"2745": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Gabim | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Koha e skaduar | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2746": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2747": { + "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" + },"2748": { + "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" + },"2749": { + "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" + },"2750": { + "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" + },"2751": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Beskrivelse | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/no-rNO/user/messages-and-channels.html#channels", + + "relUrl": "/no-rNO/user/messages-and-channels.html#channels" + },"2752": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Feil | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Tidsavbrudd | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2753": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2754": { + "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" + },"2755": { + "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" + },"2756": { + "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" + },"2757": { + "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" + },"2758": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Aprašymas | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/messages-and-channels.html#channels", + + "relUrl": "/lt-rLT/user/messages-and-channels.html#channels" + },"2759": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Klaida | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Baigėsi laikas | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2760": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2761": { + "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" + },"2762": { + "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" + },"2763": { + "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" + },"2764": { + "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" + },"2765": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | الوصف | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "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#القنوات" + },"2766": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | غلط | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | استغرق وقت طويل | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2767": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2768": { + "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" + },"2769": { + "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" + },"2770": { + "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" + },"2771": { + "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" + },"2772": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Descrição | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/messages-and-channels.html#canal", + + "relUrl": "/pt-rPT/user/messages-and-channels.html#canal" + },"2773": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erros | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2774": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2775": { + "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" + },"2776": { + "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" + },"2777": { + "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" + },"2778": { + "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" + },"2779": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | תיאור | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/messages-and-channels.html#channels", + + "relUrl": "/iw-rIL/user/messages-and-channels.html#channels" + },"2780": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | שגיאה | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2781": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2782": { + "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" + },"2783": { + "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" + },"2784": { + "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" + },"2785": { + "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" + },"2786": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Περιγραφή | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "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#κανάλια" + },"2787": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Σφάλμα | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Λήξη χρονικού ορίου | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2788": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2789": { + "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" + },"2790": { + "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" + },"2791": { + "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" },"2792": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html#messages--channels", - "relUrl": "/nl-rNL/user/messages-and-channels.html#messages--channels" + "relUrl": "/ro-rRO/user/messages-and-channels.html#messages--channels" },"2793": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Beschrijving | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/messages-and-channels.html#kanalen", + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Securitate canal . Channels support multiple encryption levels: . | Icon | Security Level | Descriere | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html#canale", - "relUrl": "/nl-rNL/user/messages-and-channels.html#kanalen" + "relUrl": "/ro-rRO/user/messages-and-channels.html#canale" },"2794": { "doc": "Messages & Channels", "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Foutmelding | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Time-Out | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Eroare | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Expirat | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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": "/nl-rNL/user/messages-and-channels.html#direct-messages" + "relUrl": "/ro-rRO/user/messages-and-channels.html#direct-messages" },"2795": { "doc": "Messages & Channels", "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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": "/nl-rNL/user/messages-and-channels.html#message-features" + "relUrl": "/ro-rRO/user/messages-and-channels.html#message-features" },"2796": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html#best-practices", - "relUrl": "/nl-rNL/user/messages-and-channels.html#best-practices" + "relUrl": "/ro-rRO/user/messages-and-channels.html#best-practices" },"2797": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html#related-topics", - "relUrl": "/nl-rNL/user/messages-and-channels.html#related-topics" + "relUrl": "/ro-rRO/user/messages-and-channels.html#related-topics" },"2798": { "doc": "Messages & Channels", "title": "Messages & Channels", "content": " ", - "url": "/Meshtastic-Android/main/nl-rNL/user/messages-and-channels.html", + "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html", - "relUrl": "/nl-rNL/user/messages-and-channels.html" + "relUrl": "/ro-rRO/user/messages-and-channels.html" },"2799": { "doc": "Sõnumid ja kanalid", "title": "Sõnumid ja kanalid", @@ -19637,2718 +19637,2718 @@ "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html#messages--channels", - "relUrl": "/it-rIT/user/messages-and-channels.html#messages--channels" + "relUrl": "/ga-rIE/user/messages-and-channels.html#messages--channels" },"2806": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Sicurezza del canale . Channels support multiple encryption levels: . | Icon | Security Level | Descrizione | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/it-rIT/user/messages-and-channels.html#canali", + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Cur síos | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html#channels", - "relUrl": "/it-rIT/user/messages-and-channels.html#canali" + "relUrl": "/ga-rIE/user/messages-and-channels.html#channels" },"2807": { "doc": "Messages & Channels", - "title": "Messaggi Diretti", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Errori | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Consegna alla mesh non riuscita | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Earráid | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Am tráth | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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": "/it-rIT/user/messages-and-channels.html#messaggi-diretti" + "relUrl": "/ga-rIE/user/messages-and-channels.html#direct-messages" },"2808": { "doc": "Messages & Channels", "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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": "/it-rIT/user/messages-and-channels.html#message-features" + "relUrl": "/ga-rIE/user/messages-and-channels.html#message-features" },"2809": { "doc": "Messages & Channels", - "title": "Buone pratiche", + "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/it-rIT/user/messages-and-channels.html#buone-pratiche", + "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html#best-practices", - "relUrl": "/it-rIT/user/messages-and-channels.html#buone-pratiche" + "relUrl": "/ga-rIE/user/messages-and-channels.html#best-practices" },"2810": { "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html#related-topics", - "relUrl": "/it-rIT/user/messages-and-channels.html#related-topics" + "relUrl": "/ga-rIE/user/messages-and-channels.html#related-topics" },"2811": { "doc": "Messages & Channels", "title": "Messages & Channels", "content": " ", - "url": "/Meshtastic-Android/main/it-rIT/user/messages-and-channels.html", + "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html", - "relUrl": "/it-rIT/user/messages-and-channels.html" + "relUrl": "/ga-rIE/user/messages-and-channels.html" },"2812": { - "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" - },"2813": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | الوصف | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "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#القنوات" - },"2814": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | غلط | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | استغرق وقت طويل | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2815": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2816": { - "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" - },"2817": { - "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" - },"2818": { - "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" - },"2819": { - "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" - },"2820": { - "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Popis | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/messages-and-channels.html#kan%C3%A1le", - - "relUrl": "/sk-rSK/user/messages-and-channels.html#kanále" - },"2821": { - "doc": "Messages & Channels", - "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Chyba | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Časový limit | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2822": { - "doc": "Messages & Channels", - "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2823": { - "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" - },"2824": { - "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" - },"2825": { - "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" - },"2826": { "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" - },"2827": { + },"2813": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Bezpieczeństwo kanału . Channels support multiple encryption levels: . | Icon | Security Level | Opis | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", "url": "/Meshtastic-Android/main/pl-rPL/user/messages-and-channels.html#kana%C5%82y", "relUrl": "/pl-rPL/user/messages-and-channels.html#kanały" - },"2828": { + },"2814": { "doc": "Messages & Channels", "title": "Bezpośrednie Wiadomości", "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Limit czasu | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" - },"2829": { + },"2815": { "doc": "Messages & Channels", "title": "Message Features", "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" - },"2830": { + },"2816": { "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" - },"2831": { + },"2817": { "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" - },"2832": { + },"2818": { "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" + },"2819": { + "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" + },"2820": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Beschrijving | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/messages-and-channels.html#kanalen", + + "relUrl": "/nl-rNL/user/messages-and-channels.html#kanalen" + },"2821": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Foutmelding | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Time-Out | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2822": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2823": { + "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" + },"2824": { + "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" + },"2825": { + "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" + },"2826": { + "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" + },"2827": { + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Kanalsäkerhet . Channels support multiple encryption levels: . | Icon | Security Level | Beskrivning | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/messages-and-channels.html#kanaler", + + "relUrl": "/sv-rSE/user/messages-and-channels.html#kanaler" + },"2828": { + "doc": "Messages & Channels", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Fel | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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" + },"2829": { + "doc": "Messages & Channels", + "title": "Message Features", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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" + },"2830": { + "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" + },"2831": { + "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" + },"2832": { + "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" },"2833": { - "doc": "訊息與頻道", - "title": "訊息與頻道", - "content": "Meshtastic 支援兩種通訊模式：頻道廣播與私訊。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/messages-and-channels.html", + "doc": "メッセージとチャンネル", + "title": "メッセージとチャンネル", + "content": "Meshtastic は、チャンネルブロードキャストとダイレクトメッセージの 2 つの通信モードをサポートしています。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/messages-and-channels.html", - "relUrl": "/zh-rTW/user/messages-and-channels.html" + "relUrl": "/ja-rJP/user/messages-and-channels.html" },"2834": { - "doc": "訊息與頻道", - "title": "頻道", - "content": "頻道是共享的通訊群組。 所有設定相同頻道金鑰的節點均可在該頻道上讀取與傳送訊息。 . 預設頻道 . 每台 Meshtastic 裝置均內建預設的 LongFast 頻道。 此為未加密頻道，供一般 mesh 網路通訊使用。 . 頻道安全性 . 頻道支援多種加密等級： . | 圖示 | 安全等級 | 描述說明 | . | 🔒 | PSK（256 位元 AES） | 使用強力預共享金鑰進行完整加密。 僅持有相符金鑰的節點可讀取訊息。 | . | 🔐 | PSK（128 位元 AES） | 使用較短的金鑰進行加密。 適用於大多數情境，但敏感資料建議使用 256 位元加密。 | . | 🔓 | 預設／開放 | 使用眾所周知的預設金鑰。 使用相同預設值的任何 Meshtastic 裝置均可讀取這些訊息。 | . | ⚠️ | 不安全 + 位置 | 開放頻道，同時廣播您的 GPS 位置。 在公開 mesh 網路中使用時請謹慎。 | . 🔒 安全提示：私人通訊請務必設定專屬的 PSK。 預設頻道刻意設計為開放，以便新使用者能探索 mesh 網路 — 但對於任何敏感內容，請另行建立獨立的加密頻道。 . 新增頻道 . | 前往「設定 → 頻道」。 | 點選「新增頻道」或掃描 QR Code。 | 設定頻道名稱與加密金鑰。設定頻道名稱與加密金鑰。 | 將頻道網址或 QR Code 分享給需要加入的人。 | . 點選頻道可查看其詳細資訊與分享選項。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/messages-and-channels.html#%E9%A0%BB%E9%81%93", + "doc": "メッセージとチャンネル", + "title": "チャンネル", + "content": "チャンネルは、共有された通信グループです。 同じチャンネル鍵を設定したすべてのノードが、そのチャンネルでメッセージを読み書きできます。 . デフォルトチャンネル . すべての Meshtastic デバイスには、デフォルトの LongFast チャンネルが用意されています。 これは、一般的なメッシュ通信に使われる暗号化されていないチャンネルです。 . チャンネルのセキュリティ . チャンネルは複数の暗号化レベルに対応しています： . | アイコン | セキュリティレベル | 説明 | . | 🔒 | PSK（256 ビット AES） | 強力な事前共有鍵で完全に暗号化されます。 一致する鍵を持つノードだけがメッセージを読めます。 | . | 🔐 | PSK（128 ビット AES） | より短い鍵で暗号化されます。 ほとんどの用途で安全ですが、機密性の高いデータには 256 ビットが推奨されます。 | . | 🔓 | デフォルト／オープン | よく知られたデフォルトの鍵を使用します。 同じプリセットのあらゆる Meshtastic デバイスが、これらのメッセージを読めます。 | . | ⚠️ | 非セキュア＋位置情報 | GPS 位置情報も一斉送信するオープンチャンネルです。 公開メッシュでは注意して使用してください。 | . 🔒 セキュリティのヒント： プライベートな通信には、必ず固有の PSK を設定してください。 デフォルトチャンネルは、新規ユーザーがメッシュを見つけられるよう意図的にオープンになっています。ただし、機密性の高い内容には別途、暗号化されたチャンネルを作成してください。 . チャンネルを追加する . | 「設定 → チャンネル」に移動します。 | 「チャンネルを追加」をタップするか、QR コードをスキャンします。 | チャンネル名と暗号化鍵を設定します。 | アクセスが必要な相手に、チャンネルの URL／QR コードを共有します。 | . チャンネルをタップすると、その詳細と共有オプションが表示されます。 . ", + "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": "/zh-rTW/user/messages-and-channels.html#頻道" + "relUrl": "/ja-rJP/user/messages-and-channels.html#チャンネル" },"2835": { - "doc": "訊息與頻道", - "title": "私訊", - "content": "私訊（DM）是兩個特定節點之間的點對點加密通訊。 . 傳送私訊 . | 開啟「訊息」頁籤。 | 從聯絡人清單中選取節點，或在節點清單中點選節點。 | 輸入訊息後點選「傳送」。 | . 訊息狀態 . 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 (queued and en-route both show this same text) | . | 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 below) | . 傳遞錯誤 . 當訊息傳遞失敗時，錯誤指示器將顯示問題原因： . | 錯誤 | 含義 | 處理方式 | . | 無路由 | 無法找到通往目標節點的路徑 | 收件者可能已離線或超出 mesh 網路範圍。 請稍後再試，或靠近對方後重新傳送。 | . | 收到 NAK | 下一個跳躍點節點拒絕轉送 | 中繼節點可能發生壅塞。 請稍候後重試。 | . | Timeout - 超時 | 在重試時間內未收到確認回應 | 收件者可能剛好超出訊號範圍。 請嘗試提高跳躍限制，或移動至訊號較佳的位置。 | . | No radio interface | 無可用的無線電介面進行傳送 | Check that your radio is connected and available. | . | Failed to deliver to mesh | 所有重試次數均已用盡 | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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 網路將自動重試。 若持續出現「無路由」錯誤，請確認中間的路由器節點是否在線。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/messages-and-channels.html#%E7%A7%81%E8%A8%8A", + "doc": "メッセージとチャンネル", + "title": "ダイレクトメッセージ", + "content": "ダイレクトメッセージ（DM）は、特定の 2 つのノード間で行われる、ポイントツーポイントの暗号化通信です。 . ダイレクトメッセージを送信する . | 「メッセージ」タブを開きます。 | 連絡先リストからノードを選択するか、ノードリストでノードをタップします。 | メッセージを入力し、「送信」をタップします。 | . メッセージの状態 . ステータスラベルは、自分が送信したメッセージの下にのみ表示されます（他のユーザーからの受信メッセージにはステータスラベルは表示されません）： . | 状態 | 意味 | . | 送信中… | キューに入っているか、すでに無線機に渡された状態で、まだどちらとも確定していません（キュー内と送信中のどちらも同じ表示になります） | . | 受信者に配信済み | ダイレクトメッセージで最も確実な確認です。受信確認が返ってきています | . | メッシュに配信済み | チャンネルブロードキャストでは、メッセージがメッシュに届いたことを示します（ブロードキャストには受信者ごとの確認応答はありません） | . | 中継済み、受信者による確認なし | ダイレクトメッセージでは警告色で表示されます。メッセージは中継されましたが、まだ受信確認が返ってきていません | . | SF++ チェーン経由でルーティング中… | Store & Forward Plus Plus チェーンによってルーティング／バッファリングされています | . | SF++ チェーンで確認済み | SF++ チェーン経由で配信が確認されました | . | エラー | 配信に失敗しました。具体的な理由はステータスをタップして確認してください（下記の「配信エラー」を参照） | . 配信エラー . メッセージの配信に失敗すると、エラーインジケーターが何が問題だったかを示します： . | エラー | 意味 | 対処方法 | . | ルートなし | 宛先ノードへの経路が存在しません | 受信者がオフラインか、メッシュの範囲外の可能性があります。 時間をおくか、距離を縮めてください。 | . | NAK を受信 | 次のホップのノードが中継を拒否しました | 中継ノードが混雑している可能性があります。 しばらく待ってから再試行してください。 | . | タイムアウト | 再試行の時間内に受信確認がありませんでした | 受信者がちょうど範囲外にいる可能性があります。 ホップ数上限を増やすか、より良い場所に移動してみてください。 | . | No radio interface | 送信に使える無線インターフェースがありません | Check that your radio is connected and available. | . | メッシュへの配信に失敗しました | すべての再試行を使い切りました | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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. | . 💡 ヒント： ほとんどの配信エラーは自然に解消します。 ノードに断続的に到達できる場合、メッシュは再試行します。 「ルートなし」エラーが続く場合は、中間のルーターノードがオンラインになっているか確認してください。 . ", + "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": "/zh-rTW/user/messages-and-channels.html#私訊" + "relUrl": "/ja-rJP/user/messages-and-channels.html#ダイレクトメッセージ" },"2836": { - "doc": "訊息與頻道", - "title": "訊息功能", - "content": "快速聊天 . 預先設定的訊息，可快速進行通訊： . | 透過訊息輸入區的快速聊天按鈕開啟 | 從內建短語或自訂訊息中選取 | 在「設定 → 快速聊天」中自訂快速聊天訊息 | 適用於不便打字的情況（戴手套、螢幕過小、緊急狀況） | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . 頻道清單會顯示每個頻道及其最新訊息預覽。 . 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 draft styles live in the field while the underlying text keeps its 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. 訊息回應 . 以表情符號對訊息作出回應： . | 長按訊息以開啟動作選單 | 點選「新增回應」以選擇表情符號 | 訊息回應顯示於訊息泡泡下方 | 多位使用者可對同一則訊息作出回應 | 可對自己或他人的訊息作出回應 | . 💡 提示：訊息回應非常輕量 — 相較於完整文字訊息，佔用極少的 mesh 網路頻寬。 . 訊息動作 . 長按任意訊息可使用以下功能： . | 複製 — 將訊息文字複製至剪貼簿 | 回覆 — 在回覆中引用該訊息 | 回應 — 新增表情符號回應 | 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) | 刪除 — 移除您傳送的訊息（僅限本機刪除） | . 訊息優先順序 . 訊息依優先順序排入佇列並傳送： . | 緊急／警示訊息（最高） | 私訊 | 頻道廣播（最低） | . 訊息限制 . | 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 or Android Auto) 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", + "doc": "メッセージとチャンネル", + "title": "メッセージの機能", + "content": "クイックチャット . すばやくやり取りするための、あらかじめ設定されたメッセージです： . | メッセージ入力欄のクイックチャットボタンから利用できます | 組み込みの定型文またはカスタムメッセージから選べます | クイックチャットのメッセージは「設定 → クイックチャット」でカスタマイズできます | 入力が難しい場面（手袋の着用、小さな画面、急いでいるとき）に便利です | . 各クイックチャット項目には、短い名前（ボタンのラベル）、挿入されるメッセージ、そして即時送信トグルがあります。有効にすると、ボタンをタップした時点で、メッセージが入力欄に置かれて編集できる状態になるのではなく、すぐに送信されます： . チャンネルリストには、各チャンネルが最新メッセージのプレビューとともに表示されます。 . メッセージを検索する . チャット画面から、どの会話でもその全履歴を直接検索できます： . | 会話（チャンネルまたはダイレクトメッセージ）を開きます。 | 上部バーの検索アイコンをタップします。 | 「メッセージを検索…」欄に入力します。 検索は入力に応じて、その会話に保存されているすべてのメッセージを対象に実行されます。 | N／M の結果カウンターと前へ／次への矢印を使って、一致箇所間を移動できます。一致箇所は会話内でハイライト表示されます。 | . 💡 ヒント： 検索は全文検索で、開いた会話の中だけを対象とします。他のチャンネルや連絡先をまたいで検索することはありません。 デバイスにすでに保存されているメッセージを対象に照合するため、完全にオフラインで動作します。 . メッセージの吹き出し . メッセージはチャットの吹き出しとして表示され、送信メッセージは右側、受信メッセージは左側に並びます。 各吹き出しには、送信者・タイムスタンプ・配信状況が表示されます。 返信付きのメッセージでは、応答の上に元メッセージの引用プレビューが表示されます。 . テキストの書式 . メッセージは、軽量なインライン Markdown に対応しています。 受信したメッセージは、記法の文字が取り除かれた状態でスタイルが適用されて表示されます： . | 種別 | 記法 | 表示結果 | . | 太字 | **bold** | 太字 | . | 斜体 | *italic* | 斜体 | . | 取り消し線 | ~~strike~~ | 取り消し線 | . | インラインコード | `code` | 等幅の code | . | リンク | [label](https://example.com) | タップできるラベル | . メッセージを作成するときは、入力欄にフォーカスして 3 文字以上入力すると、入力欄の下に書式ツールバーが表示されます。 テキストを選択してスタイルをタップすると、そのテキストが囲まれます（もう一度タップすると解除されます）。選択していない場合は、空のペアが挿入され、カーソルがマーカーの間に置かれます。 リンクボタンをタップすると、URL を入力するダイアログが開きます。 入力中は下書きに書式が適用されて表示されますが、内部のテキストは Markdown の文字を保持しています。 . 💡 ヒント： 書式はメッシュ上ではそのままの文字として送られます。iOS が送信するのと同じバイト列です。 Markdown に対応していないクライアント（古いアプリや、素のファームウェアのクライアント）では、** や ~~ の文字がそのまま表示されます。 URL、メールアドレス、電話番号は、Markdown を使うかどうかにかかわらず、引き続き自動的にリンクになります。 . メンション . メッセージ作成中に @ を入力するとノードにメンションできます。入力に応じて、一致する連絡先がピッカーに提案されます。 受信メッセージでは、メンションはノード名を表示したハイライト付きのチップとして現れます。タップすると、そのノードの詳細ページに直接移動できます。 . リアクション . 絵文字でメッセージにリアクションできます： . | メッセージを長押しすると操作メニューが開きます | 「リアクションを追加」をタップして絵文字を選びます | リアクションはメッセージの吹き出しの下に表示されます | 複数のユーザーが同じメッセージにリアクションできます | 自分のメッセージにも、他の人のメッセージにもリアクションできます | . 💡 ヒント： リアクションは軽量で、通常のテキストメッセージに比べてメッシュの帯域をほとんど消費しません。 . メッセージの操作 . 任意のメッセージを長押しすると、次の操作を利用できます： . | コピー： メッセージのテキストをクリップボードにコピーします | 返信： そのメッセージを引用して返信します | リアクション： 絵文字のリアクションを追加します | 翻訳： 受信メッセージをデバイスの言語に翻訳し、原文と翻訳を切り替えます（Google Play 版のみ。オンデバイス翻訳を使用します） | 削除： 自分が送信したメッセージを削除します（端末内での削除） | . メッセージの優先度 . メッセージは優先度に基づいてキューに入れられ、送信されます： . | 緊急／警報メッセージ（最高） | ダイレクトメッセージ | チャンネルブロードキャスト（最低） | . メッセージの制限 . | 最大長： 200 バイト（ASCII テキストで約 200 文字） | 200 バイトの上限はアプリ内の入力欄に適用されます。メッシュのペイロード上限自体は約 233 バイトのため、他の送信元（アプリ機能や Android Auto など）からのメッセージは、これより少し長い場合があります | レート制限： メッシュは電波利用時間の公平性を確保するため、大量のメッセージは制限されることがあります | 配信： 受信確認がない場合、メッセージは自動的に再送されます | . ", + "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": "/zh-rTW/user/messages-and-channels.html#訊息功能" + "relUrl": "/ja-rJP/user/messages-and-channels.html#メッセージの機能" },"2837": { - "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", + "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": "/zh-rTW/user/messages-and-channels.html#最佳實踐" + "relUrl": "/ja-rJP/user/messages-and-channels.html#ベストプラクティス" },"2838": { - "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", + "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": "/zh-rTW/user/messages-and-channels.html#相關主題" + "relUrl": "/ja-rJP/user/messages-and-channels.html#関連トピック" },"2839": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html#messages--channels", - "relUrl": "/cs-rCZ/user/messages-and-channels.html#messages--channels" + "relUrl": "/hu-rHU/user/messages-and-channels.html#messages--channels" },"2840": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Zabezpečení kanálu . Channels support multiple encryption levels: . | Icon | Security Level | Popis | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/messages-and-channels.html#kan%C3%A1ly", + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Csatorna biztonság . Channels support multiple encryption levels: . | Icon | Security Level | Leírás | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html#csatorn%C3%A1k", - "relUrl": "/cs-rCZ/user/messages-and-channels.html#kanály" + "relUrl": "/hu-rHU/user/messages-and-channels.html#csatornák" },"2841": { "doc": "Messages & Channels", "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Chyba | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Vypršel čas spojení | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Nepodařilo se doručit do mesh sítě | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Hiba | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Időtúllépés | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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": "/cs-rCZ/user/messages-and-channels.html#direct-messages" + "relUrl": "/hu-rHU/user/messages-and-channels.html#direct-messages" },"2842": { "doc": "Messages & Channels", "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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": "/cs-rCZ/user/messages-and-channels.html#message-features" + "relUrl": "/hu-rHU/user/messages-and-channels.html#message-features" },"2843": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html#best-practices", - "relUrl": "/cs-rCZ/user/messages-and-channels.html#best-practices" + "relUrl": "/hu-rHU/user/messages-and-channels.html#best-practices" },"2844": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html#related-topics", - "relUrl": "/cs-rCZ/user/messages-and-channels.html#related-topics" + "relUrl": "/hu-rHU/user/messages-and-channels.html#related-topics" },"2845": { "doc": "Messages & Channels", "title": "Messages & Channels", "content": " ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/messages-and-channels.html", + "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html", - "relUrl": "/cs-rCZ/user/messages-and-channels.html" + "relUrl": "/hu-rHU/user/messages-and-channels.html" },"2846": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#messages--channels", - "relUrl": "/fr-rFR/user/messages-and-channels.html#messages--channels" + "relUrl": "/ht-rHT/user/messages-and-channels.html#messages--channels" },"2847": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Sécurité du canal . Channels support multiple encryption levels: . | Icon | Security Level | Description | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/messages-and-channels.html#canaux", + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Deskripsyon | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#channels", - "relUrl": "/fr-rFR/user/messages-and-channels.html#canaux" + "relUrl": "/ht-rHT/user/messages-and-channels.html#channels" },"2848": { "doc": "Messages & Channels", - "title": "Messages directs", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erreur | Meaning | What to Do | . | Pas de route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Délai d’expiration | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erè | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Tan pase | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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": "/fr-rFR/user/messages-and-channels.html#messages-directs" + "relUrl": "/ht-rHT/user/messages-and-channels.html#direct-messages" },"2849": { "doc": "Messages & Channels", "title": "Message Features", "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#message-features", - "relUrl": "/fr-rFR/user/messages-and-channels.html#message-features" + "relUrl": "/ht-rHT/user/messages-and-channels.html#message-features" },"2850": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#best-practices", - "relUrl": "/fr-rFR/user/messages-and-channels.html#best-practices" + "relUrl": "/ht-rHT/user/messages-and-channels.html#best-practices" },"2851": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#related-topics", - "relUrl": "/fr-rFR/user/messages-and-channels.html#related-topics" + "relUrl": "/ht-rHT/user/messages-and-channels.html#related-topics" },"2852": { "doc": "Messages & Channels", "title": "Messages & Channels", "content": " ", - "url": "/Meshtastic-Android/main/fr-rFR/user/messages-and-channels.html", + "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html", - "relUrl": "/fr-rFR/user/messages-and-channels.html" + "relUrl": "/ht-rHT/user/messages-and-channels.html" },"2853": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html#messages--channels", - "relUrl": "/zh-rCN/user/messages-and-channels.html#messages--channels" + "relUrl": "/gl-rES/user/messages-and-channels.html#messages--channels" },"2854": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. 频道安全 . Channels support multiple encryption levels: . | 图标 | Security Level | 说明 | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/messages-and-channels.html#%E9%A2%91%E9%81%93", + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Descrición | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html#channels", - "relUrl": "/zh-rCN/user/messages-and-channels.html#频道" + "relUrl": "/gl-rES/user/messages-and-channels.html#channels" },"2855": { "doc": "Messages & Channels", - "title": "私聊", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | 超时 | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | 发送至MESH失败 | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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": "/zh-rCN/user/messages-and-channels.html#私聊" + "relUrl": "/gl-rES/user/messages-and-channels.html#direct-messages" },"2856": { "doc": "Messages & Channels", "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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": "/zh-rCN/user/messages-and-channels.html#message-features" + "relUrl": "/gl-rES/user/messages-and-channels.html#message-features" },"2857": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html#best-practices", - "relUrl": "/zh-rCN/user/messages-and-channels.html#best-practices" + "relUrl": "/gl-rES/user/messages-and-channels.html#best-practices" },"2858": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html#related-topics", - "relUrl": "/zh-rCN/user/messages-and-channels.html#related-topics" + "relUrl": "/gl-rES/user/messages-and-channels.html#related-topics" },"2859": { "doc": "Messages & Channels", "title": "Messages & Channels", "content": " ", - "url": "/Meshtastic-Android/main/zh-rCN/user/messages-and-channels.html", + "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html", - "relUrl": "/zh-rCN/user/messages-and-channels.html" + "relUrl": "/gl-rES/user/messages-and-channels.html" },"2860": { "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html#messages--channels", - "relUrl": "/srp/user/messages-and-channels.html#messages--channels" + "relUrl": "/tr-rTR/user/messages-and-channels.html#messages--channels" },"2861": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Иконица | Security Level | Опис | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/srp/user/messages-and-channels.html#%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D0%B8", + "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Açıklaması | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html#kanallar", - "relUrl": "/srp/user/messages-and-channels.html#канали" + "relUrl": "/tr-rTR/user/messages-and-channels.html#kanallar" },"2862": { "doc": "Messages & Channels", - "title": "Директне поруке", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Временско ограничење | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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", + "title": "Direct Messages", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Hata | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Zaman Aşımı | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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": "/srp/user/messages-and-channels.html#директне-поруке" + "relUrl": "/tr-rTR/user/messages-and-channels.html#direct-messages" },"2863": { "doc": "Messages & Channels", "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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": "/srp/user/messages-and-channels.html#message-features" + "relUrl": "/tr-rTR/user/messages-and-channels.html#message-features" },"2864": { "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html#best-practices", - "relUrl": "/srp/user/messages-and-channels.html#best-practices" + "relUrl": "/tr-rTR/user/messages-and-channels.html#best-practices" },"2865": { "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html#related-topics", - "relUrl": "/srp/user/messages-and-channels.html#related-topics" + "relUrl": "/tr-rTR/user/messages-and-channels.html#related-topics" },"2866": { "doc": "Messages & Channels", "title": "Messages & Channels", "content": " ", - "url": "/Meshtastic-Android/main/srp/user/messages-and-channels.html", + "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html", - "relUrl": "/srp/user/messages-and-channels.html" + "relUrl": "/tr-rTR/user/messages-and-channels.html" },"2867": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html#messages--channels", - "relUrl": "/sq-rAL/user/messages-and-channels.html#messages--channels" + "relUrl": "/es-rES/user/messages-and-channels.html#messages--channels" },"2868": { "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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Channel Security . Channels support multiple encryption levels: . | Icon | Security Level | Përshkrimi | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/messages-and-channels.html#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 device comes with a default LongFast channel. This is an unencrypted channel used for general mesh communication. Seguridad del canal . Channels support multiple encryption levels: . | Icon | Security Level | Descripción | . | 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. | . | 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. | . | 🔓 | Default / Open | Uses the well-known default key. Any Meshtastic device on the same preset can read these messages. | . | ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. | . 🔒 Security Tip: Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive. Adding a Channel . | Navigate to Settings → Channels. | Tap Add Channel or scan a QR code. | Configure the channel name and encryption key. | Share the channel URL/QR code with others who need access. | . Tapping a channel shows its details and sharing options. ", + "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html#canales", - "relUrl": "/sq-rAL/user/messages-and-channels.html#channels" + "relUrl": "/es-rES/user/messages-and-channels.html#canales" },"2869": { "doc": "Messages & Channels", "title": "Direct Messages", - "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Gabim | Meaning | What to Do | . | No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Koha e skaduar | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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", + "content": "Direct messages (DMs) are point-to-point encrypted communications between two specific nodes. Sending a Direct Message . | Open the Messages tab. | Select a node from your contacts list or tap a node in the node list. | Type your message and tap Send. | . 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 (queued and en-route both show this same text) | . | 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 below) | . 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. | . | Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. | . | Tiempo agotado | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. | . | 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": "/sq-rAL/user/messages-and-channels.html#direct-messages" + "relUrl": "/es-rES/user/messages-and-channels.html#direct-messages" },"2870": { "doc": "Messages & Channels", "title": "Message Features", - "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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", + "content": "Quick Chat . Pre-configured messages for rapid communication: . | Access via the Quick Chat button in the message input area | Choose from built-in phrases or custom messages | Customize quick chat messages in Settings → Quick Chat | Useful when typing is impractical (gloves, small screen, urgent) | . Each quick chat entry has a short Name (the button label), the Message it inserts, and an Instantly send toggle — when enabled, tapping the button sends the message immediately instead of placing it in the input field for editing: . The channel list shows each channel with its latest message preview. 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 draft styles live in the field while the underlying text keeps its 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: . | Long-press a message to open the actions menu | Tap Add Reaction to choose an emoji | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Message Actions . Long-press any message to access: . | Copy — copy message text to clipboard | Reply — quote the message in your response | React — add an emoji reaction | 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) | Delete — remove a message you sent (local deletion) | . Message Priority . Messages are queued and transmitted based on priority: . | Emergency/alert messages (highest) | Direct messages | Channel broadcasts (lowest) | . 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 or Android Auto) 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": "/sq-rAL/user/messages-and-channels.html#message-features" + "relUrl": "/es-rES/user/messages-and-channels.html#message-features" },"2871": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html#best-practices", - "relUrl": "/sq-rAL/user/messages-and-channels.html#best-practices" + "relUrl": "/es-rES/user/messages-and-channels.html#best-practices" },"2872": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html#related-topics", - "relUrl": "/sq-rAL/user/messages-and-channels.html#related-topics" + "relUrl": "/es-rES/user/messages-and-channels.html#related-topics" },"2873": { "doc": "Messages & Channels", "title": "Messages & Channels", "content": " ", - "url": "/Meshtastic-Android/main/sq-rAL/user/messages-and-channels.html", + "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html", - "relUrl": "/sq-rAL/user/messages-and-channels.html" + "relUrl": "/es-rES/user/messages-and-channels.html" },"2874": { - "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" - },"2875": { - "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" - },"2876": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#how-it-works", - - "relUrl": "/is-rIS/user/mqtt.html#how-it-works" - },"2877": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Lýsing | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"2878": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#map-reporting", - - "relUrl": "/is-rIS/user/mqtt.html#map-reporting" - },"2879": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Lýsing | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/is-rIS/user/mqtt.html#uplink-vs-downlink" - },"2880": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Lýsing | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#message-formats", - - "relUrl": "/is-rIS/user/mqtt.html#message-formats" - },"2881": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#encryption--privacy", - - "relUrl": "/is-rIS/user/mqtt.html#encryption--privacy" - },"2882": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#best-practices", - - "relUrl": "/is-rIS/user/mqtt.html#best-practices" - },"2883": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#troubleshooting", - - "relUrl": "/is-rIS/user/mqtt.html#troubleshooting" - },"2884": { - "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" - },"2885": { - "doc": "MQTT", - "title": "MQTT", - "content": "MQTT は、Meshtastic のメッシュネットワークをインターネットに橋渡しし、無線の到達範囲を超えた長距離通信を可能にします。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html", - - "relUrl": "/ja-rJP/user/mqtt.html" - },"2886": { - "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#概要" - },"2887": { - "doc": "MQTT", - "title": "仕組み", - "content": "[自分のノード] → 無線 → [WiFi 付きゲートウェイノード] → MQTT サーバー → [リモートゲートウェイ] → 無線 → [リモートノード] . インターネットに接続されたゲートウェイノード（WiFi または Ethernet）が、メッシュのメッセージを MQTT トピックに公開します。 同じトピックを購読しているリモートのゲートウェイが、それらのメッセージを自分のローカルメッシュに取り込みます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E4%BB%95%E7%B5%84%E3%81%BF", - - "relUrl": "/ja-rJP/user/mqtt.html#仕組み" - },"2888": { - "doc": "MQTT", - "title": "設定", - "content": "MQTT を有効にする . | 「設定 → モジュール設定 → MQTT」に移動します。 | MQTT モジュールを有効にします。 | サーバーへの接続を設定します： | . | 設定項目 | 説明 | デフォルト | . | サーバーアドレス | MQTT サーバーのホスト名 | mqtt.meshtastic.org | . | ユーザー名 | サーバーの認証 | meshdev | . | パスワード | サーバーの認証 | large4cats | . | ルートトピック | メッセージのベーストピック | msh | . | 暗号化 | MQTT ペイロードを暗号化 | 有効 | . | JSON 出力 | ⚠️ 非推奨：JSON パケットのサポートはファームウェアから削除されました。このフィールドは無視されます | 無効 | . | TLS | サーバーへのセキュアな接続 | 無効 | . | マップ報告 | 公開マップに位置を報告 | 無効 | . このスマートフォンでの MQTT プロキシ . ノード自体がインターネットに接続できない場合、接続中のスマートフォンを MQTT ゲートウェイとして使えます。モジュール設定で「MQTT」と「クライアントへのプロキシを有効化」を有効にすると、アプリがスマートフォンのインターネット接続を通じて、無線機とサーバーの間で MQTT の通信を中継します。 . MQTT 設定画面の上部にある「このスマートフォンでの MQTT プロキシ」トグルは、この中継が現在動作しているかどうかを示し、デバイスの MQTT 設定を編集して保存し直すことなく、すぐに停止（または再開）できます。 . デフォルトの Meshtastic サーバー . コミュニティが mqtt.meshtastic.org で公開サーバーを運用しています。 これは一般的な利用やテストを目的としています。 . ℹ️ 注意： mqtt.meshtastic.org への接続は、TLS のトグルがオフでも常に TLS（ポート 8883）を使用します。 それ以外のサーバーでは、TLS は有効にした場合にのみ使用されます（TLS ありはポート 8883、なしは 1883）。 . 🔒 プライバシー： 公開サーバー上のメッセージは、購読している誰もが読めます。 プライベートな通信には、必ずチャンネルの暗号化を使用してください。 . プライベートサーバー . プライバシーと制御を高めるために、独自の 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#設定" - },"2889": { - "doc": "MQTT", - "title": "マップ報告", - "content": "マップ報告を有効にすると、ノードは自分の位置を Meshtastic のコミュニティマップに公開します： . | meshmap.net や、同様のコミュニティマップサービスで表示されます | 共有されるのは位置とノード情報のみです | 位置を公開したくない場合は、これを無効にしてください | . ", - "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#マップ報告" - },"2890": { - "doc": "MQTT", - "title": "アップリンクとダウンリンク", - "content": "| 方向 | 説明 | . | アップリンク | メッシュ → MQTT サーバーへのメッセージ | . | ダウンリンク | MQTT サーバー → メッシュへのメッセージ | . メッセージの流れと電波利用時間を制御するため、どの方向を有効にするかをチャンネルごとに設定します。 . ", - "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#アップリンクとダウンリンク" - },"2891": { - "doc": "MQTT", - "title": "メッセージ形式", - "content": "MQTT は protobuf のメッセージ形式を使用します： . | 形式 | 説明 | 用途 | . | Protobuf | バイナリの Meshtastic protobuf エンコード | ノード間のメッシュ橋渡し | . ⚠️ 注意： JSON 出力のサポートはファームウェアから削除されました。 json_enabled の設定は、以前との互換性のためにアプリ上には表示されますが、現在のファームウェアバージョンには影響しません。 . ", - "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#メッセージ形式" - },"2892": { - "doc": "MQTT", - "title": "暗号化とプライバシー", - "content": "階層化された暗号化モデルを理解する： . | チャンネルの暗号化は、MQTT の前にメッシュ上で行われます。 チャンネルに PSK が設定されている場合、MQTT ペイロードはすでに暗号化されています。サーバーや購読者には暗号文しか見えません。 | MQTT の暗号化（モジュールの設定）は、サーバーへの転送のために追加の暗号化レイヤーを加えます。 これはメタデータやルーティング情報を保護します。 | TLS はサーバーへの TCP 接続自体を暗号化し、ネットワークレベルの盗聴を防ぎます。 | . 🔒 重要： デフォルトの公開チャンネルは、よく知られた鍵を使用しています。 デフォルトチャンネルで 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#暗号化とプライバシー" - },"2893": { - "doc": "MQTT", - "title": "ベストプラクティス", - "content": ". | MQTT に橋渡しするチャンネルでは、チャンネルレベルの暗号化（PSK）を使用します | インターネットに接続できないノードでは MQTT を有効にしないでください（バッファリングしてメモリを浪費します） | 機密性の高い運用にはプライベートサーバーを使用します | 混雑した 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#ベストプラクティス" - },"2894": { - "doc": "MQTT", - "title": "トラブルシューティング", - "content": "MQTT が接続できない . | WiFi を確認： ゲートウェイノードには、有効なインターネット接続（WiFi または Ethernet）が必要です。 MQTT は LoRa の無線リンク自体では動作しません。 | 認証情報を確認： ユーザー名やパスワードが正しくないと、ほとんどのサーバーでは何も表示されずに失敗します。 末尾のスペースがないか、よく確認してください。 | ファイアウォール： ポート 1883（MQTT）または 8883（MQTT+TLS）が開いている必要があります。 一部のネットワークは、標準外のポートをブロックします。 | DNS 解決： カスタムのサーバーホスト名を使う場合は、ノードがそれを解決できるか確認してください。 サーバーの IP アドレスを直接試してみてください。 | . メッセージが橋渡しされない . | アップリンク／ダウンリンクの設定を確認： アップリンクのみが有効な場合、メッセージはメッシュから MQTT へ流れますが、戻ってきません。 受信側のゲートウェイでダウンリンクを有効にしてください。 | チャンネルの不一致： 両方のゲートウェイが、同じ PSK を持つ同じチャンネルを共有している必要があります。 不一致の場合、メッセージは異なる鍵で暗号化され、判読できないデータとして表示されます。 | トピックの不一致： 両方のゲートウェイが同じルートトピックを使用しているか確認してください。 デフォルトの msh は公開サーバーで機能します。 | . ", - "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#トラブルシューティング" - },"2895": { - "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#関連トピック" - },"2896": { - "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" - },"2897": { - "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" - },"2898": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#how-it-works", - - "relUrl": "/ca-rES/user/mqtt.html#how-it-works" - },"2899": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descripció | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"2900": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#map-reporting", - - "relUrl": "/ca-rES/user/mqtt.html#map-reporting" - },"2901": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Descripció | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/ca-rES/user/mqtt.html#uplink-vs-downlink" - },"2902": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Descripció | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#message-formats", - - "relUrl": "/ca-rES/user/mqtt.html#message-formats" - },"2903": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#encryption--privacy", - - "relUrl": "/ca-rES/user/mqtt.html#encryption--privacy" - },"2904": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#best-practices", - - "relUrl": "/ca-rES/user/mqtt.html#best-practices" - },"2905": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#troubleshooting", - - "relUrl": "/ca-rES/user/mqtt.html#troubleshooting" - },"2906": { - "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" - },"2907": { - "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" - },"2908": { - "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" - },"2909": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#how-it-works", - - "relUrl": "/sr-rLatn/user/mqtt.html#how-it-works" - },"2910": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Опис | Подразумевано | . | Адреса сервера | MQTT broker hostname | mqtt.meshtastic.org | . | Корисничко име | Broker authentication | meshdev | . | Лозинка | Broker authentication | large4cats | . | Корен тема | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Омогућено | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Онемогућено | . | TLS | Secure connection to broker | Онемогућено | . | Map Reporting | Report position to public map | Онемогућено | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"2911": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#map-reporting", - - "relUrl": "/sr-rLatn/user/mqtt.html#map-reporting" - },"2912": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Опис | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/sr-rLatn/user/mqtt.html#uplink-vs-downlink" - },"2913": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Опис | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#message-formats", - - "relUrl": "/sr-rLatn/user/mqtt.html#message-formats" - },"2914": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#encryption--privacy", - - "relUrl": "/sr-rLatn/user/mqtt.html#encryption--privacy" - },"2915": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#best-practices", - - "relUrl": "/sr-rLatn/user/mqtt.html#best-practices" - },"2916": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#troubleshooting", - - "relUrl": "/sr-rLatn/user/mqtt.html#troubleshooting" - },"2917": { - "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" - },"2918": { - "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" - },"2919": { - "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" - },"2920": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#how-it-works", - - "relUrl": "/ko-rKR/user/mqtt.html#how-it-works" - },"2921": { - "doc": "MQTT", - "title": "설정", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | 설명 | 기본값 | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | 사용자명 | Broker authentication | meshdev | . | 비밀번호 | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | 암호화 | Encrypt MQTT payload | 활성화 | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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#설정" - },"2922": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#map-reporting", - - "relUrl": "/ko-rKR/user/mqtt.html#map-reporting" - },"2923": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | 설명 | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/ko-rKR/user/mqtt.html#uplink-vs-downlink" - },"2924": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | 설명 | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#message-formats", - - "relUrl": "/ko-rKR/user/mqtt.html#message-formats" - },"2925": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#encryption--privacy", - - "relUrl": "/ko-rKR/user/mqtt.html#encryption--privacy" - },"2926": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#best-practices", - - "relUrl": "/ko-rKR/user/mqtt.html#best-practices" - },"2927": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#troubleshooting", - - "relUrl": "/ko-rKR/user/mqtt.html#troubleshooting" - },"2928": { - "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" - },"2929": { - "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" - },"2930": { - "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" - },"2931": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#how-it-works", - - "relUrl": "/ro-rRO/user/mqtt.html#how-it-works" - },"2932": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descriere | Prestabilit | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Nume de utilizator | Broker authentication | meshdev | . | Parolă | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Activat | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"2933": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#map-reporting", - - "relUrl": "/ro-rRO/user/mqtt.html#map-reporting" - },"2934": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Descriere | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/ro-rRO/user/mqtt.html#uplink-vs-downlink" - },"2935": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Descriere | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#message-formats", - - "relUrl": "/ro-rRO/user/mqtt.html#message-formats" - },"2936": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#encryption--privacy", - - "relUrl": "/ro-rRO/user/mqtt.html#encryption--privacy" - },"2937": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#best-practices", - - "relUrl": "/ro-rRO/user/mqtt.html#best-practices" - },"2938": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#troubleshooting", - - "relUrl": "/ro-rRO/user/mqtt.html#troubleshooting" - },"2939": { - "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" - },"2940": { - "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" - },"2941": { - "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" - },"2942": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#how-it-works", - - "relUrl": "/ga-rIE/user/mqtt.html#how-it-works" - },"2943": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Cur síos | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"2944": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#map-reporting", - - "relUrl": "/ga-rIE/user/mqtt.html#map-reporting" - },"2945": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Cur síos | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/ga-rIE/user/mqtt.html#uplink-vs-downlink" - },"2946": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Cur síos | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#message-formats", - - "relUrl": "/ga-rIE/user/mqtt.html#message-formats" - },"2947": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#encryption--privacy", - - "relUrl": "/ga-rIE/user/mqtt.html#encryption--privacy" - },"2948": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#best-practices", - - "relUrl": "/ga-rIE/user/mqtt.html#best-practices" - },"2949": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#troubleshooting", - - "relUrl": "/ga-rIE/user/mqtt.html#troubleshooting" - },"2950": { - "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" - },"2951": { - "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" - },"2952": { - "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" - },"2953": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#how-it-works", - - "relUrl": "/iw-rIL/user/mqtt.html#how-it-works" - },"2954": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | תיאור | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"2955": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#map-reporting", - - "relUrl": "/iw-rIL/user/mqtt.html#map-reporting" - },"2956": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | תיאור | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/iw-rIL/user/mqtt.html#uplink-vs-downlink" - },"2957": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | תיאור | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#message-formats", - - "relUrl": "/iw-rIL/user/mqtt.html#message-formats" - },"2958": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#encryption--privacy", - - "relUrl": "/iw-rIL/user/mqtt.html#encryption--privacy" - },"2959": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#best-practices", - - "relUrl": "/iw-rIL/user/mqtt.html#best-practices" - },"2960": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#troubleshooting", - - "relUrl": "/iw-rIL/user/mqtt.html#troubleshooting" - },"2961": { - "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" - },"2962": { - "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" - },"2963": { - "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" - },"2964": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#how-it-works", - - "relUrl": "/sv-rSE/user/mqtt.html#how-it-works" - },"2965": { - "doc": "MQTT", - "title": "Konfiguration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Beskrivning | Förvald | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Användarnamn | Broker authentication | meshdev | . | Lösenord | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Kryptering | Encrypt MQTT payload | Aktiverad | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"2966": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#map-reporting", - - "relUrl": "/sv-rSE/user/mqtt.html#map-reporting" - },"2967": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Beskrivning | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/sv-rSE/user/mqtt.html#uplink-vs-downlink" - },"2968": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Beskrivning | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#message-formats", - - "relUrl": "/sv-rSE/user/mqtt.html#message-formats" - },"2969": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#encryption--privacy", - - "relUrl": "/sv-rSE/user/mqtt.html#encryption--privacy" - },"2970": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#best-practices", - - "relUrl": "/sv-rSE/user/mqtt.html#best-practices" - },"2971": { - "doc": "MQTT", - "title": "Felsökning", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#fels%C3%B6kning", - - "relUrl": "/sv-rSE/user/mqtt.html#felsökning" - },"2972": { - "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" - },"2973": { - "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" - },"2974": { - "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" - },"2975": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#how-it-works", - - "relUrl": "/ht-rHT/user/mqtt.html#how-it-works" - },"2976": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Deskripsyon | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"2977": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#map-reporting", - - "relUrl": "/ht-rHT/user/mqtt.html#map-reporting" - },"2978": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Deskripsyon | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/ht-rHT/user/mqtt.html#uplink-vs-downlink" - },"2979": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Deskripsyon | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#message-formats", - - "relUrl": "/ht-rHT/user/mqtt.html#message-formats" - },"2980": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#encryption--privacy", - - "relUrl": "/ht-rHT/user/mqtt.html#encryption--privacy" - },"2981": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#best-practices", - - "relUrl": "/ht-rHT/user/mqtt.html#best-practices" - },"2982": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#troubleshooting", - - "relUrl": "/ht-rHT/user/mqtt.html#troubleshooting" - },"2983": { - "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" - },"2984": { - "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" - },"2985": { - "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" - },"2986": { - "doc": "MQTT", - "title": "Kuinka se toimii", - "content": "[Oma radiot] → Radio → Gateway-radio WiFi:llä → MQTT-välityspalvelin → Etä-gateway → Radio → Etä-radio . Internet-yhteydellinen gateway-radio (WiFi tai Ethernet) julkaisee mesh-viestit 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" - },"2987": { - "doc": "MQTT", - "title": "Asetukset", - "content": "MQTT:n käyttöönotto . | Siirry kohtaan Asetukset → Moduulin asetukset → MQTT. | Ota MQTT-moduuli käyttöön. | Määritä välityspalvelimen yhteys: | . | Asetus | Kuvaus | Oletus | . | Palvelimen osoite | MQTT-välityspalvelimen osoite | mqtt.meshtastic.org | . | Käyttäjänimi | Välityspalvelimen tunnistautuminen | meshdev | . | Salasana | Välityspalvelimen tunnistautuminen | large4cats | . | Juuriaihe | Viestien perusaihe | msh | . | Salaus | MQTT-viestisisällön salaus | Käytössä | . | JSON Output | ⚠️ Poistettu käytöstä — JSON-pakettituki on poistettu firmwaresta; tämä kenttä jätetään huomiotta | Ei käytössä | . | TLS | Yhteyden suojaaminen välityspalvelimeen | Ei käytössä | . | Karttaraportointi | Sijainnin julkaisu julkiselle kartalle | Ei käytössä | . 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 käyttöön MQTT ja Proxy to client enabled moduulin asetuksista, jolloin sovellus välittää MQTT-liikenteen radion ja välityspalvelimen välillä puhelimen internetyhteyden kautta. MQTT-asetusten yläreunassa oleva MQTT-välityspalvelin tässä puhelimessa -kytkin näyttää, onko tämä välitys käytössä, ja sen avulla voit poistaa sen käytöstä (tai käynnistää sen uudelleen) heti ilman, että laitteen MQTT-asetuksia tarvitsee muokata ja 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. ℹ️ Huomautus: Yhteydet palvelimeen mqtt.meshtastic.org käyttävät aina TLS-salausta (portti 8883), vaikka TLS-kytkin olisi poistettu käytöstä. Kaikkien muiden välityspalvelimien kohdalla TLS-salausta käytetään vain, kun otat sen käyttöön (TLS:llä portti 8883, ilman TLS:ää portti 1883). 🔒 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" - },"2988": { - "doc": "MQTT", - "title": "Karttaraportointi", - "content": "Kun karttajako (Map Reporting) on käytössä, radiosi julkaisee sijaintinsa Meshtastic-yhteisökartalle: . | Näkyvissä osoitteessa meshmap.net ja vastaavissa yhteisökarttapalveluissa | Jaetaan vain sijainti- ja laitetiedot | Poista käytöstä, jos et halua sijaintisi näkyvän julkisesti | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#karttaraportointi", - - "relUrl": "/fi-rFI/user/mqtt.html#karttaraportointi" - },"2989": { - "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 | . Määritä kanavakohtaisesti, mitkä suunnat ovat käytössä viestiliikenteen ja lähetysajan käytön hallintaan. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#l%C3%A4hetys-vs-vastaanotto", - - "relUrl": "/fi-rFI/user/mqtt.html#lähetys-vs-vastaanotto" - },"2990": { - "doc": "MQTT", - "title": "Viestiformaatit", - "content": "MQTT käyttää protobuf-viestimuotoa: . | Muoto | Kuvaus | Käyttötarkoitus | . | Protobuf | Binäärinen Meshtastic protobuf -enkoodaus | Radioiden välinen mesh-siltaus | . ⚠️ Huom: JSON-ulostulotuki on poistettu firmwaresta. json_enabled-asetus näkyy yhä sovelluksessa taaksepäinyhteensopivuuden vuoksi, mutta sillä ei ole vaikutusta nykyisissä firmware-versioissa. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#viestiformaatit", - - "relUrl": "/fi-rFI/user/mqtt.html#viestiformaatit" - },"2991": { - "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. | MQTT-salaus (moduuliasetus) lisää ylimääräisen salauskerroksen matkalla välityspalvelimelle. Tämä suojaa metatietoja ja reititystietoja. | TLS salaa TCP-yhteyden itse välityspalvelimeen estäen verkkotason salakuuntelun. | . 🔒 Tärkeää: julkisella oletuskanavalla 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" - },"2992": { - "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 laitteissa, joilla ei ole internet-yhteyttä (se puskuroidaan ja kuluttaa 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" - },"2993": { - "doc": "MQTT", - "title": "Vianetsintä", - "content": "MQTT ei yhdistä . | Tarkista WiFi — yhdyskäytävän radiolla täytyy olla aktiivinen internet-yhteys (WiFi tai Ethernet). MQTT ei toimi LoRa-radiolinkin kautta. | Tarkista tunnukset — väärä käyttäjänimi tai salasana epäonnistuu useimmilla välityspalvelimilla hiljaisesti Tarkista ylimääräiset välilyönnit | Palomuuri — portti 1883 (MQTT) tai 8883 (MQTT+TLS) täytyy olla auki. Jotkin verkot estävät ei-standardit portit. | 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. | Aihe ei täsmää – varmista, että molemmat yhdyskäytävät käyttävät samaa juuriaihetta (Root Topic). Oletus msh toimii julkisessa välityspalvelimessa. | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#vianetsint%C3%A4", - - "relUrl": "/fi-rFI/user/mqtt.html#vianetsintä" - },"2994": { - "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" - },"2995": { - "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" - },"2996": { - "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" - },"2997": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#how-it-works", - - "relUrl": "/gl-rES/user/mqtt.html#how-it-works" - },"2998": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descrición | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"2999": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#map-reporting", - - "relUrl": "/gl-rES/user/mqtt.html#map-reporting" - },"3000": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Descrición | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/gl-rES/user/mqtt.html#uplink-vs-downlink" - },"3001": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Descrición | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#message-formats", - - "relUrl": "/gl-rES/user/mqtt.html#message-formats" - },"3002": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#encryption--privacy", - - "relUrl": "/gl-rES/user/mqtt.html#encryption--privacy" - },"3003": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#best-practices", - - "relUrl": "/gl-rES/user/mqtt.html#best-practices" - },"3004": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#troubleshooting", - - "relUrl": "/gl-rES/user/mqtt.html#troubleshooting" - },"3005": { - "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" - },"3006": { - "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" - },"3007": { - "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" - },"3008": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#how-it-works", - - "relUrl": "/uk-rUA/user/mqtt.html#how-it-works" - },"3009": { - "doc": "MQTT", - "title": "Налаштування", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Опис | За замовчуванням | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Ім’я користувача | Broker authentication | meshdev | . | Пароль | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Шифрування | Encrypt MQTT payload | Увімкнено | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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#налаштування" - },"3010": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#map-reporting", - - "relUrl": "/uk-rUA/user/mqtt.html#map-reporting" - },"3011": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Опис | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/uk-rUA/user/mqtt.html#uplink-vs-downlink" - },"3012": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Опис | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#message-formats", - - "relUrl": "/uk-rUA/user/mqtt.html#message-formats" - },"3013": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#encryption--privacy", - - "relUrl": "/uk-rUA/user/mqtt.html#encryption--privacy" - },"3014": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#best-practices", - - "relUrl": "/uk-rUA/user/mqtt.html#best-practices" - },"3015": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#troubleshooting", - - "relUrl": "/uk-rUA/user/mqtt.html#troubleshooting" - },"3016": { - "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" - },"3017": { "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" - },"3018": { + },"2875": { "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" - },"3019": { + },"2876": { "doc": "MQTT", "title": "So funktioniert’s", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#so-funktionierts", "relUrl": "/de-rDE/user/mqtt.html#so-funktionierts" - },"3020": { + },"2877": { "doc": "MQTT", "title": "Einstellungen", "content": "MQTT aktivieren . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Einstellung | Beschreibung | Standardwert | . | Serveradresse | MQTT broker hostname | mqtt.meshtastic.org | . | Benutzername | Broker authentication | meshdev | . | Passwort | Broker authentication | large4cats | . | Hauptthema | Base topic for messages | msh | . | Verschlüsselung | Encrypt MQTT payload | Aktiviert | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Deaktiviert | . | TLS | Secure connection to broker | Deaktiviert | . | Map Reporting | Report position to public map | Deaktiviert | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3021": { + },"2878": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#map-reporting", "relUrl": "/de-rDE/user/mqtt.html#map-reporting" - },"3022": { + },"2879": { "doc": "MQTT", "title": "Uplink vs Downlink", "content": "| Direction | Beschreibung | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#uplink-vs-downlink", "relUrl": "/de-rDE/user/mqtt.html#uplink-vs-downlink" - },"3023": { + },"2880": { "doc": "MQTT", "title": "Message Formats", "content": "MQTT uses protobuf message format: . | Format | Beschreibung | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#message-formats", "relUrl": "/de-rDE/user/mqtt.html#message-formats" - },"3024": { + },"2881": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#encryption--privacy", "relUrl": "/de-rDE/user/mqtt.html#encryption--privacy" - },"3025": { + },"2882": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#bew%C3%A4hrte-praktiken", "relUrl": "/de-rDE/user/mqtt.html#bewährte-praktiken" - },"3026": { + },"2883": { "doc": "MQTT", "title": "Fehlerbehebung", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#fehlerbehebung", "relUrl": "/de-rDE/user/mqtt.html#fehlerbehebung" - },"3027": { + },"2884": { "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" - },"3028": { + },"2885": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html", - "relUrl": "/hr-rHR/user/mqtt.html" - },"3029": { + "relUrl": "/ca-rES/user/mqtt.html" + },"2886": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#overview", - "relUrl": "/hr-rHR/user/mqtt.html#overview" - },"3030": { + "relUrl": "/ca-rES/user/mqtt.html#overview" + },"2887": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#how-it-works", + "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#how-it-works", - "relUrl": "/hr-rHR/user/mqtt.html#how-it-works" - },"3031": { + "relUrl": "/ca-rES/user/mqtt.html#how-it-works" + },"2888": { "doc": "MQTT", "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Opis | Zadano | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descripció | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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": "/hr-rHR/user/mqtt.html#configuration" - },"3032": { + "relUrl": "/ca-rES/user/mqtt.html#configuration" + },"2889": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#map-reporting", + "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#map-reporting", - "relUrl": "/hr-rHR/user/mqtt.html#map-reporting" - },"3033": { + "relUrl": "/ca-rES/user/mqtt.html#map-reporting" + },"2890": { "doc": "MQTT", "title": "Uplink vs Downlink", - "content": "| Direction | Opis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#uplink-vs-downlink", + "content": "| Direction | Descripció | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#uplink-vs-downlink", - "relUrl": "/hr-rHR/user/mqtt.html#uplink-vs-downlink" - },"3034": { + "relUrl": "/ca-rES/user/mqtt.html#uplink-vs-downlink" + },"2891": { "doc": "MQTT", "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Opis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#message-formats", + "content": "MQTT uses protobuf message format: . | Format | Descripció | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#message-formats", - "relUrl": "/hr-rHR/user/mqtt.html#message-formats" - },"3035": { + "relUrl": "/ca-rES/user/mqtt.html#message-formats" + },"2892": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#encryption--privacy", + "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#encryption--privacy", - "relUrl": "/hr-rHR/user/mqtt.html#encryption--privacy" - },"3036": { + "relUrl": "/ca-rES/user/mqtt.html#encryption--privacy" + },"2893": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#best-practices", + "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#best-practices", - "relUrl": "/hr-rHR/user/mqtt.html#best-practices" - },"3037": { + "relUrl": "/ca-rES/user/mqtt.html#best-practices" + },"2894": { "doc": "MQTT", "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#troubleshooting", + "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#troubleshooting", - "relUrl": "/hr-rHR/user/mqtt.html#troubleshooting" - },"3038": { + "relUrl": "/ca-rES/user/mqtt.html#troubleshooting" + },"2895": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#related-topics", - "relUrl": "/hr-rHR/user/mqtt.html#related-topics" - },"3039": { - "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" - },"3040": { - "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" - },"3041": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#how-it-works", - - "relUrl": "/lt-rLT/user/mqtt.html#how-it-works" - },"3042": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Aprašymas | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3043": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#map-reporting", - - "relUrl": "/lt-rLT/user/mqtt.html#map-reporting" - },"3044": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Aprašymas | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/lt-rLT/user/mqtt.html#uplink-vs-downlink" - },"3045": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Aprašymas | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#message-formats", - - "relUrl": "/lt-rLT/user/mqtt.html#message-formats" - },"3046": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#encryption--privacy", - - "relUrl": "/lt-rLT/user/mqtt.html#encryption--privacy" - },"3047": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#best-practices", - - "relUrl": "/lt-rLT/user/mqtt.html#best-practices" - },"3048": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#troubleshooting", - - "relUrl": "/lt-rLT/user/mqtt.html#troubleshooting" - },"3049": { - "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" - },"3050": { - "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" - },"3051": { - "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" - },"3052": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/en/user/mqtt.html#how-it-works", - - "relUrl": "/en/user/mqtt.html#how-it-works" - },"3053": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Description | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3054": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/en/user/mqtt.html#map-reporting", - - "relUrl": "/en/user/mqtt.html#map-reporting" - },"3055": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Description | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/en/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/en/user/mqtt.html#uplink-vs-downlink" - },"3056": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Description | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/en/user/mqtt.html#message-formats", - - "relUrl": "/en/user/mqtt.html#message-formats" - },"3057": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/en/user/mqtt.html#encryption--privacy", - - "relUrl": "/en/user/mqtt.html#encryption--privacy" - },"3058": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/en/user/mqtt.html#best-practices", - - "relUrl": "/en/user/mqtt.html#best-practices" - },"3059": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/en/user/mqtt.html#troubleshooting", - - "relUrl": "/en/user/mqtt.html#troubleshooting" - },"3060": { - "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" - },"3061": { - "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" - },"3062": { - "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" - },"3063": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#how-it-works", - - "relUrl": "/hu-rHU/user/mqtt.html#how-it-works" - },"3064": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Leírás | Alapértelmezett | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Felhasználónév | Broker authentication | meshdev | . | Jelszó | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Engedélyezve | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3065": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#map-reporting", - - "relUrl": "/hu-rHU/user/mqtt.html#map-reporting" - },"3066": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Leírás | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/hu-rHU/user/mqtt.html#uplink-vs-downlink" - },"3067": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Leírás | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#message-formats", - - "relUrl": "/hu-rHU/user/mqtt.html#message-formats" - },"3068": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#encryption--privacy", - - "relUrl": "/hu-rHU/user/mqtt.html#encryption--privacy" - },"3069": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#best-practices", - - "relUrl": "/hu-rHU/user/mqtt.html#best-practices" - },"3070": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#troubleshooting", - - "relUrl": "/hu-rHU/user/mqtt.html#troubleshooting" - },"3071": { - "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" - },"3072": { - "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" - },"3073": { - "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#преглед" - },"3074": { - "doc": "MQTT", - "title": "Как работи", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "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#как-работи" - },"3075": { - "doc": "MQTT", - "title": "Конфигурация", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Настройка | Описание | По подразбиране | . | Адрес на сървъра | MQTT broker hostname | mqtt.meshtastic.org | . | Потребителско име | Broker authentication | meshdev | . | Парола | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Криптиране | Encrypt MQTT payload | Активиран | . | JSON Output | ⚠️ Отхвърлено — Поддръжката на JSON пакети е премахната от фърмуера; това поле се игнорира | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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#конфигурация" - },"3076": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#map-reporting", - - "relUrl": "/bg-rBG/user/mqtt.html#map-reporting" - },"3077": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Описание | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/bg-rBG/user/mqtt.html#uplink-vs-downlink" - },"3078": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Описание | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#message-formats", - - "relUrl": "/bg-rBG/user/mqtt.html#message-formats" - },"3079": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#encryption--privacy", - - "relUrl": "/bg-rBG/user/mqtt.html#encryption--privacy" - },"3080": { - "doc": "MQTT", - "title": "Най-добри практики", - "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "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#най-добри-практики" - },"3081": { - "doc": "MQTT", - "title": "Отстраняване на неизправности", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "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#отстраняване-на-неизправности" - },"3082": { - "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#свързани-теми" - },"3083": { - "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" - },"3084": { - "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" - },"3085": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#how-it-works", - - "relUrl": "/sl-rSI/user/mqtt.html#how-it-works" - },"3086": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Opis | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3087": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#map-reporting", - - "relUrl": "/sl-rSI/user/mqtt.html#map-reporting" - },"3088": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Opis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/sl-rSI/user/mqtt.html#uplink-vs-downlink" - },"3089": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Opis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#message-formats", - - "relUrl": "/sl-rSI/user/mqtt.html#message-formats" - },"3090": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#encryption--privacy", - - "relUrl": "/sl-rSI/user/mqtt.html#encryption--privacy" - },"3091": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#best-practices", - - "relUrl": "/sl-rSI/user/mqtt.html#best-practices" - },"3092": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#troubleshooting", - - "relUrl": "/sl-rSI/user/mqtt.html#troubleshooting" - },"3093": { - "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" - },"3094": { - "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" - },"3095": { - "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" - },"3096": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#how-it-works", - - "relUrl": "/pt-rPT/user/mqtt.html#how-it-works" - },"3097": { - "doc": "MQTT", - "title": "Configuração", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descrição | Predefinição | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Utilizador | Broker authentication | meshdev | . | Palavra-passe | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3098": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#map-reporting", - - "relUrl": "/pt-rPT/user/mqtt.html#map-reporting" - },"3099": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Descrição | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/pt-rPT/user/mqtt.html#uplink-vs-downlink" - },"3100": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Descrição | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#message-formats", - - "relUrl": "/pt-rPT/user/mqtt.html#message-formats" - },"3101": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#encryption--privacy", - - "relUrl": "/pt-rPT/user/mqtt.html#encryption--privacy" - },"3102": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#best-practices", - - "relUrl": "/pt-rPT/user/mqtt.html#best-practices" - },"3103": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#troubleshooting", - - "relUrl": "/pt-rPT/user/mqtt.html#troubleshooting" - },"3104": { - "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" - },"3105": { + "relUrl": "/ca-rES/user/mqtt.html#related-topics" + },"2896": { "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" - },"3106": { + },"2897": { "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#абзор" - },"3107": { + },"2898": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#how-it-works", "relUrl": "/be-rBY/user/mqtt.html#how-it-works" - },"3108": { + },"2899": { "doc": "MQTT", "title": "Конфигурация", "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Апісанне | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Імя карыстальніка | Broker authentication | meshdev | . | Пароль | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Шифравание | Encrypt MQTT payload | Уключана | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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#конфигурация" - },"3109": { + },"2900": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#map-reporting", "relUrl": "/be-rBY/user/mqtt.html#map-reporting" - },"3110": { + },"2901": { "doc": "MQTT", "title": "Uplink vs Downlink", "content": "| Direction | Апісанне | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#uplink-vs-downlink", "relUrl": "/be-rBY/user/mqtt.html#uplink-vs-downlink" - },"3111": { + },"2902": { "doc": "MQTT", "title": "Message Formats", "content": "MQTT uses protobuf message format: . | Format | Апісанне | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#message-formats", "relUrl": "/be-rBY/user/mqtt.html#message-formats" - },"3112": { + },"2903": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#encryption--privacy", "relUrl": "/be-rBY/user/mqtt.html#encryption--privacy" - },"3113": { + },"2904": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#best-practices", "relUrl": "/be-rBY/user/mqtt.html#best-practices" - },"3114": { + },"2905": { "doc": "MQTT", "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#troubleshooting", "relUrl": "/be-rBY/user/mqtt.html#troubleshooting" - },"3115": { + },"2906": { "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" - },"3116": { + },"2907": { + "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" + },"2908": { + "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" + },"2909": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#how-it-works", + + "relUrl": "/uk-rUA/user/mqtt.html#how-it-works" + },"2910": { + "doc": "MQTT", + "title": "Налаштування", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Опис | За замовчуванням | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Ім’я користувача | Broker authentication | meshdev | . | Пароль | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Шифрування | Encrypt MQTT payload | Увімкнено | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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#налаштування" + },"2911": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#map-reporting", + + "relUrl": "/uk-rUA/user/mqtt.html#map-reporting" + },"2912": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Опис | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/uk-rUA/user/mqtt.html#uplink-vs-downlink" + },"2913": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Опис | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#message-formats", + + "relUrl": "/uk-rUA/user/mqtt.html#message-formats" + },"2914": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#encryption--privacy", + + "relUrl": "/uk-rUA/user/mqtt.html#encryption--privacy" + },"2915": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#best-practices", + + "relUrl": "/uk-rUA/user/mqtt.html#best-practices" + },"2916": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#troubleshooting", + + "relUrl": "/uk-rUA/user/mqtt.html#troubleshooting" + },"2917": { + "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" + },"2918": { + "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" + },"2919": { + "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#总览" + },"2920": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#how-it-works", + + "relUrl": "/zh-rCN/user/mqtt.html#how-it-works" + },"2921": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | 说明 | 默认 | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | 用户名称 | Broker authentication | meshdev | . | 密码 | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | 加密 | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | 禁用 | . | TLS | Secure connection to broker | 禁用 | . | Map Reporting | Report position to public map | 禁用 | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"2922": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#map-reporting", + + "relUrl": "/zh-rCN/user/mqtt.html#map-reporting" + },"2923": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | 说明 | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/zh-rCN/user/mqtt.html#uplink-vs-downlink" + },"2924": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | 说明 | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#message-formats", + + "relUrl": "/zh-rCN/user/mqtt.html#message-formats" + },"2925": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#encryption--privacy", + + "relUrl": "/zh-rCN/user/mqtt.html#encryption--privacy" + },"2926": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#best-practices", + + "relUrl": "/zh-rCN/user/mqtt.html#best-practices" + },"2927": { + "doc": "MQTT", + "title": "问题排查", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "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#问题排查" + },"2928": { + "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" + },"2929": { + "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" + },"2930": { + "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#преглед" + },"2931": { + "doc": "MQTT", + "title": "Как работи", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "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#как-работи" + },"2932": { + "doc": "MQTT", + "title": "Конфигурация", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Настройка | Описание | По подразбиране | . | Адрес на сървъра | MQTT broker hostname | mqtt.meshtastic.org | . | Потребителско име | Broker authentication | meshdev | . | Парола | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Криптиране | Encrypt MQTT payload | Активиран | . | JSON Output | ⚠️ Отхвърлено — Поддръжката на JSON пакети е премахната от фърмуера; това поле се игнорира | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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#конфигурация" + },"2933": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#map-reporting", + + "relUrl": "/bg-rBG/user/mqtt.html#map-reporting" + },"2934": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Описание | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/bg-rBG/user/mqtt.html#uplink-vs-downlink" + },"2935": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Описание | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#message-formats", + + "relUrl": "/bg-rBG/user/mqtt.html#message-formats" + },"2936": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#encryption--privacy", + + "relUrl": "/bg-rBG/user/mqtt.html#encryption--privacy" + },"2937": { + "doc": "MQTT", + "title": "Най-добри практики", + "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "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#най-добри-практики" + },"2938": { + "doc": "MQTT", + "title": "Отстраняване на неизправности", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "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#отстраняване-на-неизправности" + },"2939": { + "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#свързани-теми" + },"2940": { + "doc": "MQTT", + "title": "MQTT", + "content": "MQTT 將您的 Meshtastic mesh 網路橋接至網際網路，實現超越無線電範圍的長距離通訊。 . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html", + + "relUrl": "/zh-rTW/user/mqtt.html" + },"2941": { + "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#概觀" + },"2942": { + "doc": "MQTT", + "title": "運作方式", + "content": "〔您的節點〕→ 無線電 → 〔具備 Wi-Fi 的閘道節點〕→ MQTT 代理伺服器 → 〔遠端閘道〕→ 無線電 → 〔遠端節點〕 . 具備網際網路連線（Wi-Fi 或乙太網路）的閘道節點，將 mesh 訊息發布至 MQTT 主題。 訂閱相同主題的遠端閘道，將這些訊息注入其本地 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#運作方式" + },"2943": { + "doc": "MQTT", + "title": "設定", + "content": "啟用 MQTT . | 前往「設定 → 模組設定 → MQTT」。 | 啟用 MQTT 模組。 | 設定代理伺服器連線： | . | 設定 | 描述說明 | 默認 | . | 伺服器位址 | MQTT 代理伺服器主機名稱 | mqtt.meshtastic.org | . | 使用者名稱 | 代理伺服器驗證 | meshdev | . | 密碼 | 代理伺服器驗證 | large4cats | . | 根主題 | 訊息的基礎主題 | msh | . | 加密 | 加密 MQTT 承載內容 | 已啟用 | . | JSON 輸出 | ⚠️ 已棄用——韌體已移除 JSON 封包支援；此欄位將被忽略 | 已停用 | . | TLS | 與代理伺服器的安全連線 | 已停用 | . | 地圖回報 | 將位置回報至公開地圖 | 已停用 | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. 預設 Meshtastic 代理伺服器 . 社群在 mqtt.meshtastic.org 維護一個公開的代理伺服器。 此伺服器供一般使用與測試之用。 . ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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#設定" + },"2944": { + "doc": "MQTT", + "title": "地圖回報", + "content": "啟用地圖回報後，您的節點將把位置發布至 Meshtastic 社群地圖： . | 可在〔meshmap.net〕(https://meshmap.net) 及類似的社群地圖服務上查看 | 僅分享位置與節點資訊 | 若不希望位置公開顯示，請停用此功能 | . ", + "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#地圖回報" + },"2945": { + "doc": "MQTT", + "title": "上行 vs 下行", + "content": "| 方向 | 描述說明 | . | 上行 | 訊息從 mesh 網路 → MQTT 代理伺服器 | . | 下行 | 訊息從 MQTT 代理伺服器 → mesh 網路 | . 可依頻道設定哪些方向為啟用狀態，以控制訊息流向與無線電佔用時間。 . ", + "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-下行" + },"2946": { + "doc": "MQTT", + "title": "訊息格式", + "content": "MQTT 使用 protobuf 訊息格式： . | 格式 | 描述說明 | 使用情境 | . | Protobuf | 二進位 Meshtastic protobuf 編碼 | 節點間 mesh 橋接 | . ⚠️ 注意：韌體已移除 JSON 輸出支援。 Json_enabled 設定在應用程式中仍會顯示，以維持舊版相容性，但對目前的韌體版本不會產生任何效果。 . ", + "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#訊息格式" + },"2947": { + "doc": "MQTT", + "title": "加密與隱私", + "content": "了解分層加密模型： . | 頻道加密在 mesh 網路上進行，發生於 MQTT 傳輸之前。 若您的頻道已設定 PSK，MQTT 承載內容將已加密——代理伺服器及任何訂閱者只能看到密文。 | MQTT 加密（模組設定）在傳輸至代理伺服器的過程中新增額外的加密層。 此設定可保護中繼資料與路由資訊。 | TLS 對連接至代理伺服器的 TCP 連線進行加密，防止網路層級的竊聽。 | . 🔒 重要：預設公開頻道使用眾所周知的金鑰。 透過 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#加密與隱私" + },"2948": { + "doc": "MQTT", + "title": "最佳實踐", + "content": ". | 在橋接至 MQTT 的頻道上使用頻道層級加密（PSK） | 請勿在無法連接網際網路的節點上啟用 MQTT（這將導致緩衝堆積並浪費記憶體） | 敏感部署環境請使用私有代理伺服器 | 從繁忙的 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#最佳實踐" + },"2949": { + "doc": "MQTT", + "title": "故障排除", + "content": "MQTT 無法連線 . | 檢查 Wi-Fi——閘道節點必須具備有效的網際網路連線（Wi-Fi 或乙太網路）。 MQTT 無法直接透過 LoRa 無線電連結運作。 | 確認登入憑證 — 帳號或密碼錯誤在大多數代理伺服器上會靜默失敗，不顯示錯誤訊息。 請仔細確認是否有多餘的尾端空白字元。 | 防火牆 — 連接埠 1883（MQTT）或 8883（MQTT+TLS）必須開放。 部分網路會封鎖非標準連接埠。 | DNS 解析 — 若使用自訂代理伺服器主機名稱，請確認節點能夠正確解析該名稱。 請嘗試直接使用代理伺服器的 IP 位址進行連線。 | . 訊息未正常橋接 . | 檢查上行／下行設定 — 若僅啟用上行，訊息只會從 mesh 網路流向 MQTT，不會反向傳送。 請在接收端閘道上啟用下行功能。 | 頻道不符 — 兩個閘道必須使用相同頻道且具備相同的 PSK。 不符時，訊息將以不同金鑰加密，導致對方收到的內容為亂碼。 | 主題不符 — 請確認兩個閘道使用相同的根主題。 預設的 msh 適用於公開代理伺服器。 | . ", + "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#故障排除" + },"2950": { + "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#相關主題" + },"2951": { + "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" + },"2952": { + "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" + },"2953": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#how-it-works", + + "relUrl": "/sr-rLatn/user/mqtt.html#how-it-works" + },"2954": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Опис | Подразумевано | . | Адреса сервера | MQTT broker hostname | mqtt.meshtastic.org | . | Корисничко име | Broker authentication | meshdev | . | Лозинка | Broker authentication | large4cats | . | Корен тема | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Омогућено | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Онемогућено | . | TLS | Secure connection to broker | Онемогућено | . | Map Reporting | Report position to public map | Онемогућено | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"2955": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#map-reporting", + + "relUrl": "/sr-rLatn/user/mqtt.html#map-reporting" + },"2956": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Опис | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/sr-rLatn/user/mqtt.html#uplink-vs-downlink" + },"2957": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Опис | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#message-formats", + + "relUrl": "/sr-rLatn/user/mqtt.html#message-formats" + },"2958": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#encryption--privacy", + + "relUrl": "/sr-rLatn/user/mqtt.html#encryption--privacy" + },"2959": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#best-practices", + + "relUrl": "/sr-rLatn/user/mqtt.html#best-practices" + },"2960": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#troubleshooting", + + "relUrl": "/sr-rLatn/user/mqtt.html#troubleshooting" + },"2961": { + "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" + },"2962": { + "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" + },"2963": { + "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" + },"2964": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#how-it-works", + + "relUrl": "/cs-rCZ/user/mqtt.html#how-it-works" + },"2965": { + "doc": "MQTT", + "title": "Nastavení", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Nastavení | Popis | Výchozí | . | Adresa serveru | MQTT broker hostname | mqtt.meshtastic.org | . | Uživatelské jméno | Broker authentication | meshdev | . | Heslo | Broker authentication | large4cats | . | Kořenové téma | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Povoleno | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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í" + },"2966": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#map-reporting", + + "relUrl": "/cs-rCZ/user/mqtt.html#map-reporting" + },"2967": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Popis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/cs-rCZ/user/mqtt.html#uplink-vs-downlink" + },"2968": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Popis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#message-formats", + + "relUrl": "/cs-rCZ/user/mqtt.html#message-formats" + },"2969": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#encryption--privacy", + + "relUrl": "/cs-rCZ/user/mqtt.html#encryption--privacy" + },"2970": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#best-practices", + + "relUrl": "/cs-rCZ/user/mqtt.html#best-practices" + },"2971": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#troubleshooting", + + "relUrl": "/cs-rCZ/user/mqtt.html#troubleshooting" + },"2972": { + "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" + },"2973": { + "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" + },"2974": { + "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" + },"2975": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/en/user/mqtt.html#how-it-works", + + "relUrl": "/en/user/mqtt.html#how-it-works" + },"2976": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Description | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"2977": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/en/user/mqtt.html#map-reporting", + + "relUrl": "/en/user/mqtt.html#map-reporting" + },"2978": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Description | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/en/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/en/user/mqtt.html#uplink-vs-downlink" + },"2979": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Description | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/en/user/mqtt.html#message-formats", + + "relUrl": "/en/user/mqtt.html#message-formats" + },"2980": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/en/user/mqtt.html#encryption--privacy", + + "relUrl": "/en/user/mqtt.html#encryption--privacy" + },"2981": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/en/user/mqtt.html#best-practices", + + "relUrl": "/en/user/mqtt.html#best-practices" + },"2982": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/en/user/mqtt.html#troubleshooting", + + "relUrl": "/en/user/mqtt.html#troubleshooting" + },"2983": { + "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" + },"2984": { + "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" + },"2985": { + "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" + },"2986": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#how-it-works", + + "relUrl": "/sl-rSI/user/mqtt.html#how-it-works" + },"2987": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Opis | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"2988": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#map-reporting", + + "relUrl": "/sl-rSI/user/mqtt.html#map-reporting" + },"2989": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Opis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/sl-rSI/user/mqtt.html#uplink-vs-downlink" + },"2990": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Opis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#message-formats", + + "relUrl": "/sl-rSI/user/mqtt.html#message-formats" + },"2991": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#encryption--privacy", + + "relUrl": "/sl-rSI/user/mqtt.html#encryption--privacy" + },"2992": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#best-practices", + + "relUrl": "/sl-rSI/user/mqtt.html#best-practices" + },"2993": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#troubleshooting", + + "relUrl": "/sl-rSI/user/mqtt.html#troubleshooting" + },"2994": { + "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" + },"2995": { + "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" + },"2996": { + "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" + },"2997": { + "doc": "MQTT", + "title": "Come funziona", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#come-funziona", + + "relUrl": "/it-rIT/user/mqtt.html#come-funziona" + },"2998": { + "doc": "MQTT", + "title": "Configurazione", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Impostazione | Descrizione | Predefinito | . | Indirizzo Server | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh | . | Cifratura | Encrypt MQTT payload | Abilitato | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"2999": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#map-reporting", + + "relUrl": "/it-rIT/user/mqtt.html#map-reporting" + },"3000": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Descrizione | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/it-rIT/user/mqtt.html#uplink-vs-downlink" + },"3001": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Descrizione | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#message-formats", + + "relUrl": "/it-rIT/user/mqtt.html#message-formats" + },"3002": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#encryption--privacy", + + "relUrl": "/it-rIT/user/mqtt.html#encryption--privacy" + },"3003": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#buone-pratiche", + + "relUrl": "/it-rIT/user/mqtt.html#buone-pratiche" + },"3004": { + "doc": "MQTT", + "title": "Risoluzione problemi", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#risoluzione-problemi", + + "relUrl": "/it-rIT/user/mqtt.html#risoluzione-problemi" + },"3005": { + "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" + },"3006": { "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" - },"3117": { + },"3007": { "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" - },"3118": { + },"3008": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#how-it-works", "relUrl": "/pt-rBR/user/mqtt.html#how-it-works" - },"3119": { + },"3009": { "doc": "MQTT", "title": "Configuration", "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descrição | Padrão | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Nome de usuário | Broker authentication | meshdev | . | Senha | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3120": { + },"3010": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#map-reporting", "relUrl": "/pt-rBR/user/mqtt.html#map-reporting" - },"3121": { + },"3011": { "doc": "MQTT", "title": "Uplink vs Downlink", "content": "| Direction | Descrição | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#uplink-vs-downlink", "relUrl": "/pt-rBR/user/mqtt.html#uplink-vs-downlink" - },"3122": { + },"3012": { "doc": "MQTT", "title": "Message Formats", "content": "MQTT uses protobuf message format: . | Format | Descrição | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#message-formats", "relUrl": "/pt-rBR/user/mqtt.html#message-formats" - },"3123": { + },"3013": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#encryption--privacy", "relUrl": "/pt-rBR/user/mqtt.html#encryption--privacy" - },"3124": { + },"3014": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#best-practices", "relUrl": "/pt-rBR/user/mqtt.html#best-practices" - },"3125": { + },"3015": { "doc": "MQTT", "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#troubleshooting", "relUrl": "/pt-rBR/user/mqtt.html#troubleshooting" - },"3126": { + },"3016": { "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" - },"3127": { + },"3017": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html", - "relUrl": "/el-rGR/user/mqtt.html" - },"3128": { + "relUrl": "/is-rIS/user/mqtt.html" + },"3018": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#overview", - "relUrl": "/el-rGR/user/mqtt.html#overview" - },"3129": { + "relUrl": "/is-rIS/user/mqtt.html#overview" + },"3019": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#how-it-works", + "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#how-it-works", - "relUrl": "/el-rGR/user/mqtt.html#how-it-works" - },"3130": { + "relUrl": "/is-rIS/user/mqtt.html#how-it-works" + },"3020": { "doc": "MQTT", "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Περιγραφή | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Όνομα χρήστη | Broker authentication | meshdev | . | Κωδικός πρόσβασης | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Lýsing | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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": "/el-rGR/user/mqtt.html#configuration" - },"3131": { + "relUrl": "/is-rIS/user/mqtt.html#configuration" + },"3021": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#map-reporting", + "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#map-reporting", - "relUrl": "/el-rGR/user/mqtt.html#map-reporting" - },"3132": { + "relUrl": "/is-rIS/user/mqtt.html#map-reporting" + },"3022": { "doc": "MQTT", "title": "Uplink vs Downlink", - "content": "| Direction | Περιγραφή | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#uplink-vs-downlink", + "content": "| Direction | Lýsing | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#uplink-vs-downlink", - "relUrl": "/el-rGR/user/mqtt.html#uplink-vs-downlink" - },"3133": { + "relUrl": "/is-rIS/user/mqtt.html#uplink-vs-downlink" + },"3023": { "doc": "MQTT", "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Περιγραφή | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#message-formats", + "content": "MQTT uses protobuf message format: . | Format | Lýsing | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#message-formats", - "relUrl": "/el-rGR/user/mqtt.html#message-formats" - },"3134": { + "relUrl": "/is-rIS/user/mqtt.html#message-formats" + },"3024": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#encryption--privacy", + "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#encryption--privacy", - "relUrl": "/el-rGR/user/mqtt.html#encryption--privacy" - },"3135": { + "relUrl": "/is-rIS/user/mqtt.html#encryption--privacy" + },"3025": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#best-practices", + "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#best-practices", - "relUrl": "/el-rGR/user/mqtt.html#best-practices" - },"3136": { + "relUrl": "/is-rIS/user/mqtt.html#best-practices" + },"3026": { "doc": "MQTT", "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#troubleshooting", + "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#troubleshooting", - "relUrl": "/el-rGR/user/mqtt.html#troubleshooting" - },"3137": { + "relUrl": "/is-rIS/user/mqtt.html#troubleshooting" + },"3027": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#related-topics", - "relUrl": "/el-rGR/user/mqtt.html#related-topics" - },"3138": { + "relUrl": "/is-rIS/user/mqtt.html#related-topics" + },"3028": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html", - "relUrl": "/es-rES/user/mqtt.html" - },"3139": { - "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" - },"3140": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#how-it-works", - - "relUrl": "/es-rES/user/mqtt.html#how-it-works" - },"3141": { - "doc": "MQTT", - "title": "Configuración", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descripción | Por defecto | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Usuario | Broker authentication | meshdev | . | Contraseña | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Cifrado | Encrypt MQTT payload | Habilitado | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3142": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#map-reporting", - - "relUrl": "/es-rES/user/mqtt.html#map-reporting" - },"3143": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Descripción | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/es-rES/user/mqtt.html#uplink-vs-downlink" - },"3144": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Descripción | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#message-formats", - - "relUrl": "/es-rES/user/mqtt.html#message-formats" - },"3145": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#encryption--privacy", - - "relUrl": "/es-rES/user/mqtt.html#encryption--privacy" - },"3146": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#best-practices", - - "relUrl": "/es-rES/user/mqtt.html#best-practices" - },"3147": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#troubleshooting", - - "relUrl": "/es-rES/user/mqtt.html#troubleshooting" - },"3148": { - "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" - },"3149": { - "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" - },"3150": { - "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ış" - },"3151": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#how-it-works", - - "relUrl": "/tr-rTR/user/mqtt.html#how-it-works" - },"3152": { - "doc": "MQTT", - "title": "Yapılandırma", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Açıklaması | Varsayılan | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Kullanıcı adı | Broker authentication | meshdev | . | Şifre | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Açık | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3153": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#map-reporting", - - "relUrl": "/tr-rTR/user/mqtt.html#map-reporting" - },"3154": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Açıklaması | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/tr-rTR/user/mqtt.html#uplink-vs-downlink" - },"3155": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Açıklaması | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#message-formats", - - "relUrl": "/tr-rTR/user/mqtt.html#message-formats" - },"3156": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#encryption--privacy", - - "relUrl": "/tr-rTR/user/mqtt.html#encryption--privacy" - },"3157": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#best-practices", - - "relUrl": "/tr-rTR/user/mqtt.html#best-practices" - },"3158": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#troubleshooting", - - "relUrl": "/tr-rTR/user/mqtt.html#troubleshooting" - },"3159": { - "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" - },"3160": { - "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" - },"3161": { + "relUrl": "/fr-rFR/user/mqtt.html" + },"3029": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#overview", - "relUrl": "/no-rNO/user/mqtt.html#overview" - },"3162": { + "relUrl": "/fr-rFR/user/mqtt.html#overview" + },"3030": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#how-it-works", + "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#how-it-works", - "relUrl": "/no-rNO/user/mqtt.html#how-it-works" - },"3163": { + "relUrl": "/fr-rFR/user/mqtt.html#how-it-works" + },"3031": { "doc": "MQTT", "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Beskrivelse | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Description | Par défaut | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Nom d’utilisateur | Broker authentication | meshdev | . | Mot de passe | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Chiffrement | Encrypt MQTT payload | Activé | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Désactivé | . | TLS | Secure connection to broker | Désactivé | . | Map Reporting | Report position to public map | Désactivé | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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": "/no-rNO/user/mqtt.html#configuration" - },"3164": { + "relUrl": "/fr-rFR/user/mqtt.html#configuration" + },"3032": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#map-reporting", + "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#map-reporting", - "relUrl": "/no-rNO/user/mqtt.html#map-reporting" - },"3165": { + "relUrl": "/fr-rFR/user/mqtt.html#map-reporting" + },"3033": { "doc": "MQTT", "title": "Uplink vs Downlink", - "content": "| Direction | Beskrivelse | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#uplink-vs-downlink", + "content": "| Direction | Description | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#uplink-vs-downlink", - "relUrl": "/no-rNO/user/mqtt.html#uplink-vs-downlink" - },"3166": { + "relUrl": "/fr-rFR/user/mqtt.html#uplink-vs-downlink" + },"3034": { "doc": "MQTT", "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Beskrivelse | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#message-formats", + "content": "MQTT uses protobuf message format: . | Format | Description | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#message-formats", - "relUrl": "/no-rNO/user/mqtt.html#message-formats" - },"3167": { + "relUrl": "/fr-rFR/user/mqtt.html#message-formats" + },"3035": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#encryption--privacy", + "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#encryption--privacy", - "relUrl": "/no-rNO/user/mqtt.html#encryption--privacy" - },"3168": { + "relUrl": "/fr-rFR/user/mqtt.html#encryption--privacy" + },"3036": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#best-practices", + "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#best-practices", - "relUrl": "/no-rNO/user/mqtt.html#best-practices" - },"3169": { + "relUrl": "/fr-rFR/user/mqtt.html#best-practices" + },"3037": { "doc": "MQTT", "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#troubleshooting", + "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#troubleshooting", - "relUrl": "/no-rNO/user/mqtt.html#troubleshooting" - },"3170": { + "relUrl": "/fr-rFR/user/mqtt.html#troubleshooting" + },"3038": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#related-topics", - "relUrl": "/no-rNO/user/mqtt.html#related-topics" - },"3171": { + "relUrl": "/fr-rFR/user/mqtt.html#related-topics" + },"3039": { + "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" + },"3040": { + "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" + },"3041": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/srp/user/mqtt.html#how-it-works", + + "relUrl": "/srp/user/mqtt.html#how-it-works" + },"3042": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Опис | Подразумевано | . | Адреса сервера | MQTT broker hostname | mqtt.meshtastic.org | . | Корисничко име | Broker authentication | meshdev | . | Лозинка | Broker authentication | large4cats | . | Корен тема | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Омогућено | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Онемогућено | . | TLS | Secure connection to broker | Онемогућено | . | Map Reporting | Report position to public map | Онемогућено | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3043": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/srp/user/mqtt.html#map-reporting", + + "relUrl": "/srp/user/mqtt.html#map-reporting" + },"3044": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Опис | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/srp/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/srp/user/mqtt.html#uplink-vs-downlink" + },"3045": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Опис | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/srp/user/mqtt.html#message-formats", + + "relUrl": "/srp/user/mqtt.html#message-formats" + },"3046": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/srp/user/mqtt.html#encryption--privacy", + + "relUrl": "/srp/user/mqtt.html#encryption--privacy" + },"3047": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/srp/user/mqtt.html#best-practices", + + "relUrl": "/srp/user/mqtt.html#best-practices" + },"3048": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/srp/user/mqtt.html#troubleshooting", + + "relUrl": "/srp/user/mqtt.html#troubleshooting" + },"3049": { + "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" + },"3050": { + "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" + },"3051": { + "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" + },"3052": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#how-it-works", + + "relUrl": "/sk-rSK/user/mqtt.html#how-it-works" + },"3053": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Popis | Predvolené | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Používateľské meno | Broker authentication | meshdev | . | Heslo | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3054": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#map-reporting", + + "relUrl": "/sk-rSK/user/mqtt.html#map-reporting" + },"3055": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Popis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/sk-rSK/user/mqtt.html#uplink-vs-downlink" + },"3056": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Popis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#message-formats", + + "relUrl": "/sk-rSK/user/mqtt.html#message-formats" + },"3057": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#encryption--privacy", + + "relUrl": "/sk-rSK/user/mqtt.html#encryption--privacy" + },"3058": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#best-practices", + + "relUrl": "/sk-rSK/user/mqtt.html#best-practices" + },"3059": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#troubleshooting", + + "relUrl": "/sk-rSK/user/mqtt.html#troubleshooting" + },"3060": { + "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" + },"3061": { + "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" + },"3062": { + "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" + },"3063": { + "doc": "MQTT", + "title": "Kuinka se toimii", + "content": "[Oma radiot] → Radio → Gateway-radio WiFi:llä → MQTT-välityspalvelin → Etä-gateway → Radio → Etä-radio . Internet-yhteydellinen gateway-radio (WiFi tai Ethernet) julkaisee mesh-viestit 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" + },"3064": { + "doc": "MQTT", + "title": "Asetukset", + "content": "MQTT:n käyttöönotto . | Siirry kohtaan Asetukset → Moduulin asetukset → MQTT. | Ota MQTT-moduuli käyttöön. | Määritä välityspalvelimen yhteys: | . | Asetus | Kuvaus | Oletus | . | Palvelimen osoite | MQTT-välityspalvelimen osoite | mqtt.meshtastic.org | . | Käyttäjänimi | Välityspalvelimen tunnistautuminen | meshdev | . | Salasana | Välityspalvelimen tunnistautuminen | large4cats | . | Juuriaihe | Viestien perusaihe | msh | . | Salaus | MQTT-viestisisällön salaus | Käytössä | . | JSON Output | ⚠️ Poistettu käytöstä — JSON-pakettituki on poistettu firmwaresta; tämä kenttä jätetään huomiotta | Ei käytössä | . | TLS | Yhteyden suojaaminen välityspalvelimeen | Ei käytössä | . | Karttaraportointi | Sijainnin julkaisu julkiselle kartalle | Ei käytössä | . 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 käyttöön MQTT ja Proxy to client enabled moduulin asetuksista, jolloin sovellus välittää MQTT-liikenteen radion ja välityspalvelimen välillä puhelimen internetyhteyden kautta. MQTT-asetusten yläreunassa oleva MQTT-välityspalvelin tässä puhelimessa -kytkin näyttää, onko tämä välitys käytössä, ja sen avulla voit poistaa sen käytöstä (tai käynnistää sen uudelleen) heti ilman, että laitteen MQTT-asetuksia tarvitsee muokata ja 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. ℹ️ Huomautus: Yhteydet palvelimeen mqtt.meshtastic.org käyttävät aina TLS-salausta (portti 8883), vaikka TLS-kytkin olisi poistettu käytöstä. Kaikkien muiden välityspalvelimien kohdalla TLS-salausta käytetään vain, kun otat sen käyttöön (TLS:llä portti 8883, ilman TLS:ää portti 1883). 🔒 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" + },"3065": { + "doc": "MQTT", + "title": "Karttaraportointi", + "content": "Kun karttajako (Map Reporting) on käytössä, radiosi julkaisee sijaintinsa Meshtastic-yhteisökartalle: . | Näkyvissä osoitteessa meshmap.net ja vastaavissa yhteisökarttapalveluissa | Jaetaan vain sijainti- ja laitetiedot | Poista käytöstä, jos et halua sijaintisi näkyvän julkisesti | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#karttaraportointi", + + "relUrl": "/fi-rFI/user/mqtt.html#karttaraportointi" + },"3066": { + "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 | . Määritä kanavakohtaisesti, mitkä suunnat ovat käytössä viestiliikenteen ja lähetysajan käytön hallintaan. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#l%C3%A4hetys-vs-vastaanotto", + + "relUrl": "/fi-rFI/user/mqtt.html#lähetys-vs-vastaanotto" + },"3067": { + "doc": "MQTT", + "title": "Viestiformaatit", + "content": "MQTT käyttää protobuf-viestimuotoa: . | Muoto | Kuvaus | Käyttötarkoitus | . | Protobuf | Binäärinen Meshtastic protobuf -enkoodaus | Radioiden välinen mesh-siltaus | . ⚠️ Huom: JSON-ulostulotuki on poistettu firmwaresta. json_enabled-asetus näkyy yhä sovelluksessa taaksepäinyhteensopivuuden vuoksi, mutta sillä ei ole vaikutusta nykyisissä firmware-versioissa. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#viestiformaatit", + + "relUrl": "/fi-rFI/user/mqtt.html#viestiformaatit" + },"3068": { + "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. | MQTT-salaus (moduuliasetus) lisää ylimääräisen salauskerroksen matkalla välityspalvelimelle. Tämä suojaa metatietoja ja reititystietoja. | TLS salaa TCP-yhteyden itse välityspalvelimeen estäen verkkotason salakuuntelun. | . 🔒 Tärkeää: julkisella oletuskanavalla 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" + },"3069": { + "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 laitteissa, joilla ei ole internet-yhteyttä (se puskuroidaan ja kuluttaa 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" + },"3070": { + "doc": "MQTT", + "title": "Vianetsintä", + "content": "MQTT ei yhdistä . | Tarkista WiFi — yhdyskäytävän radiolla täytyy olla aktiivinen internet-yhteys (WiFi tai Ethernet). MQTT ei toimi LoRa-radiolinkin kautta. | Tarkista tunnukset — väärä käyttäjänimi tai salasana epäonnistuu useimmilla välityspalvelimilla hiljaisesti Tarkista ylimääräiset välilyönnit | Palomuuri — portti 1883 (MQTT) tai 8883 (MQTT+TLS) täytyy olla auki. Jotkin verkot estävät ei-standardit portit. | 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. | Aihe ei täsmää – varmista, että molemmat yhdyskäytävät käyttävät samaa juuriaihetta (Root Topic). Oletus msh toimii julkisessa välityspalvelimessa. | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#vianetsint%C3%A4", + + "relUrl": "/fi-rFI/user/mqtt.html#vianetsintä" + },"3071": { + "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" + },"3072": { "doc": "MQTT", "title": "MQTT", "content": "MQTT соединяет твою mesh-сеть Meshtastic с интернетом, обеспечивая связь на больших расстояниях за пределами радиодиапазона. ", "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html", "relUrl": "/ru-rRU/user/mqtt.html" - },"3172": { + },"3073": { "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#обзор" - },"3173": { + },"3074": { "doc": "MQTT", "title": "Как это работает", "content": "[Ваша нода] → Радио → [Шлюзовая нода с WiFi] → MQTT-брокер → [Удалённый шлюз] → Радио → [Удалённая нода] . Шлюзовая нода с доступом в интернет (WiFi или Ethernet) публикует сообщения mesh-сети в топик MQTT. Удалённые шлюзы, подписанные на тот же топик, передают эти сообщения в свою локальную 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#как-это-работает" - },"3174": { + },"3075": { "doc": "MQTT", "title": "Настройки", "content": "Включение MQTT . | Перейдите в Настройки → Конфигурация модулей → MQTT. | Включите модуль MQTT. | Настройте подключение к брокеру: | . | Настройка | Описание | По умолчанию | . | Адрес сервера | Имя хоста MQTT-брокера | mqtt.meshtastic.org | . | Имя пользователя | Аутентификация брокера | meshdev | . | Пароль | Аутентификация брокера | large4cats | . | Корневая тема | Базовый топик для сообщений | msh | . | Шифрование | Шифровать полезную нагрузку MQTT | Включено | . | Вывод в JSON | ⚠️ Устарело — поддержка JSON-пакетов удалена из прошивки; это поле игнорируется | Отключено | . | TLS | Безопасное подключение к брокеру | Отключено | . | Публикация на карте | Сообщать о местоположении на публичную карту | Отключено | . MQTT-прокси на этом телефоне . Если у твоей ноды нет собственного доступа в интернет, она может использовать подключённый телефон как MQTT-шлюз: включите MQTT и Прокси для клиента в конфигурации модуля, и приложение будет передавать трафик MQTT между радио и брокером через интернет-соединение твоего телефона. Переключатель MQTT-прокси на этом телефоне в верхней части экрана настроек MQTT показывает, запущена ли сейчас эта ретрансляция, и позволяет тебе немедленно отключить (или перезапустить) её — без редактирования и повторного сохранения конфигурации MQTT устройства. Стандартный брокер Meshtastic . Сообщество поддерживает публичный брокер по адресу mqtt.meshtastic.org. Он предназначен для общего использования и тестирования. ℹ️ Примечание: Подключения к mqtt.meshtastic.org всегда используют TLS (порт 8883), даже если переключатель TLS выключен. Для любого другого брокера TLS используется только при включении (порт 8883 с TLS, 1883 без). 🔒 Приватность: Сообщения на публичном брокере доступны для чтения всем, кто подписан. Всегда используйте шифрование каналов для конфиденциальной связи. Частный брокер . Для большей приватности и контроля ты можешь запустить собственный 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#настройки" - },"3175": { + },"3076": { "doc": "MQTT", "title": "Публикация на карте", "content": "Когда публикация на карте включена, твоя нода отправляет своё местоположение на карту сообщества Meshtastic: . | Доступно на meshmap.net и аналогичных картографических сервисах сообщества | Передаются только координаты и информация о ноде | Отключи эту функцию, если не хочешь, чтобы твоё местоположение было общедоступным | . ", "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#публикация-на-карте" - },"3176": { + },"3077": { "doc": "MQTT", "title": "Uplink и Downlink", "content": "| Направление | Описание | . | Uplink (восходящий) | Сообщения из mesh-сети → MQTT-брокер | . | Downlink (нисходящий) | Сообщения от MQTT-брокера → mesh-сеть | . Настройте для каждого канала активные направления, чтобы управлять потоком сообщений и использованием эфирного времени. ", "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#uplink-%D0%B8-downlink", "relUrl": "/ru-rRU/user/mqtt.html#uplink-и-downlink" - },"3177": { + },"3078": { "doc": "MQTT", "title": "Форматы сообщений", "content": "MQTT использует формат сообщений protobuf: . | Формат | Описание | Сценарий использования | . | Protobuf | Бинарное кодирование Meshtastic protobuf | Соединение нод между mesh-сетями | . ⚠️ Примечание: Поддержка вывода в JSON была удалена из прошивки. Настройка json_enabled всё ещё отображается в приложении для обратной совместимости, но не влияет на текущие версии прошивки. ", "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#форматы-сообщений" - },"3178": { + },"3079": { "doc": "MQTT", "title": "Шифрование и приватность", "content": "Понимание многоуровневой модели шифрования: . | Шифрование канала происходит в mesh-сети до MQTT. Если твой канал использует PSK, полезная нагрузка MQTT уже зашифрована — брокер и любые подписчики видят только зашифрованный текст. | Шифрование MQTT (настройка модуля) добавляет дополнительный уровень шифрования при передаче к брокеру. Это защищает метаданные и информацию о маршрутизации. | TLS шифрует само TCP-соединение с брокером, предотвращая перехват на сетевом уровне. | . 🔒 Важно: Публичный канал по умолчанию использует общеизвестный ключ. Сообщения в канале по умолчанию, отправленные через 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#шифрование-и-приватность" - },"3179": { + },"3080": { "doc": "MQTT", "title": "Рекомендации", "content": ". | Используйте шифрование на уровне канала (PSK) на каналах, подключённых к MQTT | Не включайте MQTT на нодах без доступа в интернет (это приведёт к буферизации и напрасной трате памяти) | Используйте частный брокер для задач, требующих повышенной безопасности | Учитывайте эфирное время при передаче сообщений из загруженных 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#рекомендации" - },"3180": { + },"3081": { "doc": "MQTT", "title": "Устранение неполадок", "content": "MQTT не подключается . | Проверьте WiFi — шлюзовая нода должна иметь активное подключение к интернету (WiFi или Ethernet). MQTT не работает через сам радиоканал LoRa. | Проверьте учётные данные — неверное имя пользователя или пароль на большинстве брокеров приводят к тихому сбою. Проверьте, нет ли лишних пробелов в конце. | Брандмауэр — порт 1883 (MQTT) или 8883 (MQTT+TLS) должен быть открыт. Некоторые сети блокируют нестандартные порты. | Разрешение DNS — если используется имя хоста собственного брокера, убедитесь, что нода может его разрешить. Попробуйте подключиться напрямую по IP-адресу брокера. | . Сообщения не проходят через мост . | Проверьте настройки uplink/downlink — если включён только uplink, сообщения идут из mesh-сети в MQTT, но не обратно. Включите downlink на принимающем шлюзе. | Несовпадение каналов — оба шлюза должны использовать один и тот же канал с одинаковым PSK. Несовпадение означает, что сообщения зашифрованы разными ключами и выглядят как мусор. | Несовпадение топиков — убедитесь, что оба шлюза используют одинаковый корневой топик. Стандартный msh работает для публичного брокера. | . ", "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#устранение-неполадок" - },"3181": { + },"3082": { "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#связанные-темы" + },"3083": { + "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" + },"3084": { + "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" + },"3085": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#how-it-works", + + "relUrl": "/ko-rKR/user/mqtt.html#how-it-works" + },"3086": { + "doc": "MQTT", + "title": "설정", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | 설명 | 기본값 | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | 사용자명 | Broker authentication | meshdev | . | 비밀번호 | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | 암호화 | Encrypt MQTT payload | 활성화 | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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#설정" + },"3087": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#map-reporting", + + "relUrl": "/ko-rKR/user/mqtt.html#map-reporting" + },"3088": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | 설명 | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/ko-rKR/user/mqtt.html#uplink-vs-downlink" + },"3089": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | 설명 | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#message-formats", + + "relUrl": "/ko-rKR/user/mqtt.html#message-formats" + },"3090": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#encryption--privacy", + + "relUrl": "/ko-rKR/user/mqtt.html#encryption--privacy" + },"3091": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#best-practices", + + "relUrl": "/ko-rKR/user/mqtt.html#best-practices" + },"3092": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#troubleshooting", + + "relUrl": "/ko-rKR/user/mqtt.html#troubleshooting" + },"3093": { + "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" + },"3094": { + "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" + },"3095": { + "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" + },"3096": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#how-it-works", + + "relUrl": "/hr-rHR/user/mqtt.html#how-it-works" + },"3097": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Opis | Zadano | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3098": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#map-reporting", + + "relUrl": "/hr-rHR/user/mqtt.html#map-reporting" + },"3099": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Opis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/hr-rHR/user/mqtt.html#uplink-vs-downlink" + },"3100": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Opis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#message-formats", + + "relUrl": "/hr-rHR/user/mqtt.html#message-formats" + },"3101": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#encryption--privacy", + + "relUrl": "/hr-rHR/user/mqtt.html#encryption--privacy" + },"3102": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#best-practices", + + "relUrl": "/hr-rHR/user/mqtt.html#best-practices" + },"3103": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#troubleshooting", + + "relUrl": "/hr-rHR/user/mqtt.html#troubleshooting" + },"3104": { + "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" + },"3105": { + "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" + },"3106": { + "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" + },"3107": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#how-it-works", + + "relUrl": "/sq-rAL/user/mqtt.html#how-it-works" + },"3108": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Përshkrimi | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3109": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#map-reporting", + + "relUrl": "/sq-rAL/user/mqtt.html#map-reporting" + },"3110": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Përshkrimi | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/sq-rAL/user/mqtt.html#uplink-vs-downlink" + },"3111": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Përshkrimi | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#message-formats", + + "relUrl": "/sq-rAL/user/mqtt.html#message-formats" + },"3112": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#encryption--privacy", + + "relUrl": "/sq-rAL/user/mqtt.html#encryption--privacy" + },"3113": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#best-practices", + + "relUrl": "/sq-rAL/user/mqtt.html#best-practices" + },"3114": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#troubleshooting", + + "relUrl": "/sq-rAL/user/mqtt.html#troubleshooting" + },"3115": { + "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" + },"3116": { + "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" + },"3117": { + "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" + },"3118": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#how-it-works", + + "relUrl": "/no-rNO/user/mqtt.html#how-it-works" + },"3119": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Beskrivelse | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3120": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#map-reporting", + + "relUrl": "/no-rNO/user/mqtt.html#map-reporting" + },"3121": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Beskrivelse | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/no-rNO/user/mqtt.html#uplink-vs-downlink" + },"3122": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Beskrivelse | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#message-formats", + + "relUrl": "/no-rNO/user/mqtt.html#message-formats" + },"3123": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#encryption--privacy", + + "relUrl": "/no-rNO/user/mqtt.html#encryption--privacy" + },"3124": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#best-practices", + + "relUrl": "/no-rNO/user/mqtt.html#best-practices" + },"3125": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#troubleshooting", + + "relUrl": "/no-rNO/user/mqtt.html#troubleshooting" + },"3126": { + "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" + },"3127": { + "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" + },"3128": { + "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" + },"3129": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#how-it-works", + + "relUrl": "/lt-rLT/user/mqtt.html#how-it-works" + },"3130": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Aprašymas | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3131": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#map-reporting", + + "relUrl": "/lt-rLT/user/mqtt.html#map-reporting" + },"3132": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Aprašymas | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/lt-rLT/user/mqtt.html#uplink-vs-downlink" + },"3133": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Aprašymas | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#message-formats", + + "relUrl": "/lt-rLT/user/mqtt.html#message-formats" + },"3134": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#encryption--privacy", + + "relUrl": "/lt-rLT/user/mqtt.html#encryption--privacy" + },"3135": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#best-practices", + + "relUrl": "/lt-rLT/user/mqtt.html#best-practices" + },"3136": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#troubleshooting", + + "relUrl": "/lt-rLT/user/mqtt.html#troubleshooting" + },"3137": { + "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" + },"3138": { + "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" + },"3139": { + "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" + },"3140": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#how-it-works", + + "relUrl": "/ar-rSA/user/mqtt.html#how-it-works" + },"3141": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | الوصف | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3142": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#map-reporting", + + "relUrl": "/ar-rSA/user/mqtt.html#map-reporting" + },"3143": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | الوصف | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/ar-rSA/user/mqtt.html#uplink-vs-downlink" + },"3144": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | الوصف | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#message-formats", + + "relUrl": "/ar-rSA/user/mqtt.html#message-formats" + },"3145": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#encryption--privacy", + + "relUrl": "/ar-rSA/user/mqtt.html#encryption--privacy" + },"3146": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#best-practices", + + "relUrl": "/ar-rSA/user/mqtt.html#best-practices" + },"3147": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#troubleshooting", + + "relUrl": "/ar-rSA/user/mqtt.html#troubleshooting" + },"3148": { + "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" + },"3149": { + "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" + },"3150": { + "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" + },"3151": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#how-it-works", + + "relUrl": "/pt-rPT/user/mqtt.html#how-it-works" + },"3152": { + "doc": "MQTT", + "title": "Configuração", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descrição | Predefinição | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Utilizador | Broker authentication | meshdev | . | Palavra-passe | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3153": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#map-reporting", + + "relUrl": "/pt-rPT/user/mqtt.html#map-reporting" + },"3154": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Descrição | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/pt-rPT/user/mqtt.html#uplink-vs-downlink" + },"3155": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Descrição | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#message-formats", + + "relUrl": "/pt-rPT/user/mqtt.html#message-formats" + },"3156": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#encryption--privacy", + + "relUrl": "/pt-rPT/user/mqtt.html#encryption--privacy" + },"3157": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#best-practices", + + "relUrl": "/pt-rPT/user/mqtt.html#best-practices" + },"3158": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#troubleshooting", + + "relUrl": "/pt-rPT/user/mqtt.html#troubleshooting" + },"3159": { + "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" + },"3160": { + "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" + },"3161": { + "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" + },"3162": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#how-it-works", + + "relUrl": "/iw-rIL/user/mqtt.html#how-it-works" + },"3163": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | תיאור | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3164": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#map-reporting", + + "relUrl": "/iw-rIL/user/mqtt.html#map-reporting" + },"3165": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | תיאור | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/iw-rIL/user/mqtt.html#uplink-vs-downlink" + },"3166": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | תיאור | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#message-formats", + + "relUrl": "/iw-rIL/user/mqtt.html#message-formats" + },"3167": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#encryption--privacy", + + "relUrl": "/iw-rIL/user/mqtt.html#encryption--privacy" + },"3168": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#best-practices", + + "relUrl": "/iw-rIL/user/mqtt.html#best-practices" + },"3169": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#troubleshooting", + + "relUrl": "/iw-rIL/user/mqtt.html#troubleshooting" + },"3170": { + "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" + },"3171": { + "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" + },"3172": { + "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" + },"3173": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#how-it-works", + + "relUrl": "/el-rGR/user/mqtt.html#how-it-works" + },"3174": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Περιγραφή | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Όνομα χρήστη | Broker authentication | meshdev | . | Κωδικός πρόσβασης | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3175": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#map-reporting", + + "relUrl": "/el-rGR/user/mqtt.html#map-reporting" + },"3176": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Περιγραφή | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/el-rGR/user/mqtt.html#uplink-vs-downlink" + },"3177": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Περιγραφή | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#message-formats", + + "relUrl": "/el-rGR/user/mqtt.html#message-formats" + },"3178": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#encryption--privacy", + + "relUrl": "/el-rGR/user/mqtt.html#encryption--privacy" + },"3179": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#best-practices", + + "relUrl": "/el-rGR/user/mqtt.html#best-practices" + },"3180": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#troubleshooting", + + "relUrl": "/el-rGR/user/mqtt.html#troubleshooting" + },"3181": { + "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" },"3182": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html", - "relUrl": "/nl-rNL/user/mqtt.html" + "relUrl": "/ro-rRO/user/mqtt.html" },"3183": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#overview", - "relUrl": "/nl-rNL/user/mqtt.html#overview" + "relUrl": "/ro-rRO/user/mqtt.html#overview" },"3184": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#how-it-works", + "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#how-it-works", - "relUrl": "/nl-rNL/user/mqtt.html#how-it-works" + "relUrl": "/ro-rRO/user/mqtt.html#how-it-works" },"3185": { "doc": "MQTT", "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Beschrijving | Standaard | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Gebruikersnaam | Broker authentication | meshdev | . | Wachtwoord | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descriere | Prestabilit | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Nume de utilizator | Broker authentication | meshdev | . | Parolă | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Activat | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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": "/nl-rNL/user/mqtt.html#configuration" + "relUrl": "/ro-rRO/user/mqtt.html#configuration" },"3186": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#map-reporting", + "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#map-reporting", - "relUrl": "/nl-rNL/user/mqtt.html#map-reporting" + "relUrl": "/ro-rRO/user/mqtt.html#map-reporting" },"3187": { "doc": "MQTT", "title": "Uplink vs Downlink", - "content": "| Direction | Beschrijving | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#uplink-vs-downlink", + "content": "| Direction | Descriere | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#uplink-vs-downlink", - "relUrl": "/nl-rNL/user/mqtt.html#uplink-vs-downlink" + "relUrl": "/ro-rRO/user/mqtt.html#uplink-vs-downlink" },"3188": { "doc": "MQTT", "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Beschrijving | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#message-formats", + "content": "MQTT uses protobuf message format: . | Format | Descriere | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#message-formats", - "relUrl": "/nl-rNL/user/mqtt.html#message-formats" + "relUrl": "/ro-rRO/user/mqtt.html#message-formats" },"3189": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#encryption--privacy", + "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#encryption--privacy", - "relUrl": "/nl-rNL/user/mqtt.html#encryption--privacy" + "relUrl": "/ro-rRO/user/mqtt.html#encryption--privacy" },"3190": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#best-practices", + "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#best-practices", - "relUrl": "/nl-rNL/user/mqtt.html#best-practices" + "relUrl": "/ro-rRO/user/mqtt.html#best-practices" },"3191": { "doc": "MQTT", "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#troubleshooting", + "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#troubleshooting", - "relUrl": "/nl-rNL/user/mqtt.html#troubleshooting" + "relUrl": "/ro-rRO/user/mqtt.html#troubleshooting" },"3192": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#related-topics", - "relUrl": "/nl-rNL/user/mqtt.html#related-topics" + "relUrl": "/ro-rRO/user/mqtt.html#related-topics" },"3193": { "doc": "MQTT", "title": "MQTT", @@ -22430,772 +22430,772 @@ "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html", - "relUrl": "/it-rIT/user/mqtt.html" + "relUrl": "/ga-rIE/user/mqtt.html" },"3205": { "doc": "MQTT", - "title": "Panoramica", + "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/it-rIT/user/mqtt.html#panoramica", + "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#overview", - "relUrl": "/it-rIT/user/mqtt.html#panoramica" + "relUrl": "/ga-rIE/user/mqtt.html#overview" },"3206": { "doc": "MQTT", - "title": "Come funziona", + "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#come-funziona", + "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#how-it-works", - "relUrl": "/it-rIT/user/mqtt.html#come-funziona" + "relUrl": "/ga-rIE/user/mqtt.html#how-it-works" },"3207": { "doc": "MQTT", - "title": "Configurazione", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Impostazione | Descrizione | Predefinito | . | Indirizzo Server | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh | . | Cifratura | Encrypt MQTT payload | Abilitato | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Cur síos | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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": "/it-rIT/user/mqtt.html#configurazione" + "relUrl": "/ga-rIE/user/mqtt.html#configuration" },"3208": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#map-reporting", + "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#map-reporting", - "relUrl": "/it-rIT/user/mqtt.html#map-reporting" + "relUrl": "/ga-rIE/user/mqtt.html#map-reporting" },"3209": { "doc": "MQTT", "title": "Uplink vs Downlink", - "content": "| Direction | Descrizione | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#uplink-vs-downlink", + "content": "| Direction | Cur síos | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#uplink-vs-downlink", - "relUrl": "/it-rIT/user/mqtt.html#uplink-vs-downlink" + "relUrl": "/ga-rIE/user/mqtt.html#uplink-vs-downlink" },"3210": { "doc": "MQTT", "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Descrizione | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#message-formats", + "content": "MQTT uses protobuf message format: . | Format | Cur síos | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#message-formats", - "relUrl": "/it-rIT/user/mqtt.html#message-formats" + "relUrl": "/ga-rIE/user/mqtt.html#message-formats" },"3211": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#encryption--privacy", + "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#encryption--privacy", - "relUrl": "/it-rIT/user/mqtt.html#encryption--privacy" + "relUrl": "/ga-rIE/user/mqtt.html#encryption--privacy" },"3212": { "doc": "MQTT", - "title": "Buone pratiche", + "title": "Best Practices", "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#buone-pratiche", + "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#best-practices", - "relUrl": "/it-rIT/user/mqtt.html#buone-pratiche" + "relUrl": "/ga-rIE/user/mqtt.html#best-practices" },"3213": { "doc": "MQTT", - "title": "Risoluzione problemi", + "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#risoluzione-problemi", + "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#troubleshooting", - "relUrl": "/it-rIT/user/mqtt.html#risoluzione-problemi" + "relUrl": "/ga-rIE/user/mqtt.html#troubleshooting" },"3214": { "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#related-topics", - "relUrl": "/it-rIT/user/mqtt.html#related-topics" + "relUrl": "/ga-rIE/user/mqtt.html#related-topics" },"3215": { - "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" - },"3216": { - "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" - },"3217": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#how-it-works", - - "relUrl": "/ar-rSA/user/mqtt.html#how-it-works" - },"3218": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | الوصف | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3219": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#map-reporting", - - "relUrl": "/ar-rSA/user/mqtt.html#map-reporting" - },"3220": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | الوصف | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/ar-rSA/user/mqtt.html#uplink-vs-downlink" - },"3221": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | الوصف | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#message-formats", - - "relUrl": "/ar-rSA/user/mqtt.html#message-formats" - },"3222": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#encryption--privacy", - - "relUrl": "/ar-rSA/user/mqtt.html#encryption--privacy" - },"3223": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#best-practices", - - "relUrl": "/ar-rSA/user/mqtt.html#best-practices" - },"3224": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#troubleshooting", - - "relUrl": "/ar-rSA/user/mqtt.html#troubleshooting" - },"3225": { - "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" - },"3226": { - "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" - },"3227": { - "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" - },"3228": { - "doc": "MQTT", - "title": "How It Works", - "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#how-it-works", - - "relUrl": "/sk-rSK/user/mqtt.html#how-it-works" - },"3229": { - "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Popis | Predvolené | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Používateľské meno | Broker authentication | meshdev | . | Heslo | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3230": { - "doc": "MQTT", - "title": "Map Reporting", - "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#map-reporting", - - "relUrl": "/sk-rSK/user/mqtt.html#map-reporting" - },"3231": { - "doc": "MQTT", - "title": "Uplink vs Downlink", - "content": "| Direction | Popis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#uplink-vs-downlink", - - "relUrl": "/sk-rSK/user/mqtt.html#uplink-vs-downlink" - },"3232": { - "doc": "MQTT", - "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Popis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#message-formats", - - "relUrl": "/sk-rSK/user/mqtt.html#message-formats" - },"3233": { - "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#encryption--privacy", - - "relUrl": "/sk-rSK/user/mqtt.html#encryption--privacy" - },"3234": { - "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#best-practices", - - "relUrl": "/sk-rSK/user/mqtt.html#best-practices" - },"3235": { - "doc": "MQTT", - "title": "Troubleshooting", - "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#troubleshooting", - - "relUrl": "/sk-rSK/user/mqtt.html#troubleshooting" - },"3236": { - "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" - },"3237": { "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" - },"3238": { + },"3216": { "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" - },"3239": { + },"3217": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#how-it-works", "relUrl": "/pl-rPL/user/mqtt.html#how-it-works" - },"3240": { + },"3218": { "doc": "MQTT", "title": "Konfiguracja", "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Opis | Domyślny | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Nazwa użytkownika | Broker authentication | meshdev | . | Hasło | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Szyfrowanie | Encrypt MQTT payload | Włączony | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Wyłączony | . | TLS | Secure connection to broker | Wyłączony | . | Map Reporting | Report position to public map | Wyłączony | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" - },"3241": { + },"3219": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#map-reporting", "relUrl": "/pl-rPL/user/mqtt.html#map-reporting" - },"3242": { + },"3220": { "doc": "MQTT", "title": "Uplink vs Downlink", "content": "| Direction | Opis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#uplink-vs-downlink", "relUrl": "/pl-rPL/user/mqtt.html#uplink-vs-downlink" - },"3243": { + },"3221": { "doc": "MQTT", "title": "Message Formats", "content": "MQTT uses protobuf message format: . | Format | Opis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#message-formats", "relUrl": "/pl-rPL/user/mqtt.html#message-formats" - },"3244": { + },"3222": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#encryption--privacy", "relUrl": "/pl-rPL/user/mqtt.html#encryption--privacy" - },"3245": { + },"3223": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#best-practices", "relUrl": "/pl-rPL/user/mqtt.html#best-practices" - },"3246": { + },"3224": { "doc": "MQTT", "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#troubleshooting", "relUrl": "/pl-rPL/user/mqtt.html#troubleshooting" - },"3247": { + },"3225": { "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" + },"3226": { + "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" + },"3227": { + "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" + },"3228": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#how-it-works", + + "relUrl": "/nl-rNL/user/mqtt.html#how-it-works" + },"3229": { + "doc": "MQTT", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Beschrijving | Standaard | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Gebruikersnaam | Broker authentication | meshdev | . | Wachtwoord | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3230": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#map-reporting", + + "relUrl": "/nl-rNL/user/mqtt.html#map-reporting" + },"3231": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Beschrijving | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/nl-rNL/user/mqtt.html#uplink-vs-downlink" + },"3232": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Beschrijving | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#message-formats", + + "relUrl": "/nl-rNL/user/mqtt.html#message-formats" + },"3233": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#encryption--privacy", + + "relUrl": "/nl-rNL/user/mqtt.html#encryption--privacy" + },"3234": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#best-practices", + + "relUrl": "/nl-rNL/user/mqtt.html#best-practices" + },"3235": { + "doc": "MQTT", + "title": "Troubleshooting", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#troubleshooting", + + "relUrl": "/nl-rNL/user/mqtt.html#troubleshooting" + },"3236": { + "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" + },"3237": { + "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" + },"3238": { + "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" + },"3239": { + "doc": "MQTT", + "title": "How It Works", + "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#how-it-works", + + "relUrl": "/sv-rSE/user/mqtt.html#how-it-works" + },"3240": { + "doc": "MQTT", + "title": "Konfiguration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Beskrivning | Förvald | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Användarnamn | Broker authentication | meshdev | . | Lösenord | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Kryptering | Encrypt MQTT payload | Aktiverad | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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" + },"3241": { + "doc": "MQTT", + "title": "Map Reporting", + "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#map-reporting", + + "relUrl": "/sv-rSE/user/mqtt.html#map-reporting" + },"3242": { + "doc": "MQTT", + "title": "Uplink vs Downlink", + "content": "| Direction | Beskrivning | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#uplink-vs-downlink", + + "relUrl": "/sv-rSE/user/mqtt.html#uplink-vs-downlink" + },"3243": { + "doc": "MQTT", + "title": "Message Formats", + "content": "MQTT uses protobuf message format: . | Format | Beskrivning | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#message-formats", + + "relUrl": "/sv-rSE/user/mqtt.html#message-formats" + },"3244": { + "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#encryption--privacy", + + "relUrl": "/sv-rSE/user/mqtt.html#encryption--privacy" + },"3245": { + "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#best-practices", + + "relUrl": "/sv-rSE/user/mqtt.html#best-practices" + },"3246": { + "doc": "MQTT", + "title": "Felsökning", + "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#fels%C3%B6kning", + + "relUrl": "/sv-rSE/user/mqtt.html#felsökning" + },"3247": { + "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" },"3248": { "doc": "MQTT", "title": "MQTT", - "content": "MQTT 將您的 Meshtastic mesh 網路橋接至網際網路，實現超越無線電範圍的長距離通訊。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html", + "content": "MQTT は、Meshtastic のメッシュネットワークをインターネットに橋渡しし、無線の到達範囲を超えた長距離通信を可能にします。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html", - "relUrl": "/zh-rTW/user/mqtt.html" + "relUrl": "/ja-rJP/user/mqtt.html" },"3249": { "doc": "MQTT", - "title": "概觀", - "content": "MQTT 模組可將您的節點連接至 MQTT 代理伺服器，實現以下功能： . | 透過網際網路傳送訊息至不同實體 mesh 網路上的節點 | 與智慧家庭自動化及監控系統整合 | 將節點位置發布至公開的 Meshtastic 地圖 | 自訂資料管線，用於記錄與警示通知 | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E6%A6%82%E8%A7%80", + "title": "概要", + "content": "MQTT モジュールは、ノードを MQTT サーバーに接続し、次のことを可能にします： . | インターネット経由で、物理的に異なるメッシュ上のノードにメッセージを届ける | ホームオートメーションや監視システムとの連携 | ノードの位置を公開の Meshtastic マップに公開する | ログ記録や通知のためのカスタムデータパイプライン | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E6%A6%82%E8%A6%81", - "relUrl": "/zh-rTW/user/mqtt.html#概觀" + "relUrl": "/ja-rJP/user/mqtt.html#概要" },"3250": { "doc": "MQTT", - "title": "運作方式", - "content": "〔您的節點〕→ 無線電 → 〔具備 Wi-Fi 的閘道節點〕→ MQTT 代理伺服器 → 〔遠端閘道〕→ 無線電 → 〔遠端節點〕 . 具備網際網路連線（Wi-Fi 或乙太網路）的閘道節點，將 mesh 訊息發布至 MQTT 主題。 訂閱相同主題的遠端閘道，將這些訊息注入其本地 mesh 網路。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E9%81%8B%E4%BD%9C%E6%96%B9%E5%BC%8F", + "title": "仕組み", + "content": "[自分のノード] → 無線 → [WiFi 付きゲートウェイノード] → MQTT サーバー → [リモートゲートウェイ] → 無線 → [リモートノード] . インターネットに接続されたゲートウェイノード（WiFi または Ethernet）が、メッシュのメッセージを MQTT トピックに公開します。 同じトピックを購読しているリモートのゲートウェイが、それらのメッセージを自分のローカルメッシュに取り込みます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E4%BB%95%E7%B5%84%E3%81%BF", - "relUrl": "/zh-rTW/user/mqtt.html#運作方式" + "relUrl": "/ja-rJP/user/mqtt.html#仕組み" },"3251": { "doc": "MQTT", "title": "設定", - "content": "啟用 MQTT . | 前往「設定 → 模組設定 → MQTT」。 | 啟用 MQTT 模組。 | 設定代理伺服器連線： | . | 設定 | 描述說明 | 默認 | . | 伺服器位址 | MQTT 代理伺服器主機名稱 | mqtt.meshtastic.org | . | 使用者名稱 | 代理伺服器驗證 | meshdev | . | 密碼 | 代理伺服器驗證 | large4cats | . | 根主題 | 訊息的基礎主題 | msh | . | 加密 | 加密 MQTT 承載內容 | 已啟用 | . | JSON 輸出 | ⚠️ 已棄用——韌體已移除 JSON 封包支援；此欄位將被忽略 | 已停用 | . | TLS | 與代理伺服器的安全連線 | 已停用 | . | 地圖回報 | 將位置回報至公開地圖 | 已停用 | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. 預設 Meshtastic 代理伺服器 . 社群在 mqtt.meshtastic.org 維護一個公開的代理伺服器。 此伺服器供一般使用與測試之用。 . ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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", + "content": "MQTT を有効にする . | 「設定 → モジュール設定 → MQTT」に移動します。 | MQTT モジュールを有効にします。 | サーバーへの接続を設定します： | . | 設定項目 | 説明 | デフォルト | . | サーバーアドレス | MQTT サーバーのホスト名 | mqtt.meshtastic.org | . | ユーザー名 | サーバーの認証 | meshdev | . | パスワード | サーバーの認証 | large4cats | . | ルートトピック | メッセージのベーストピック | msh | . | 暗号化 | MQTT ペイロードを暗号化 | 有効 | . | JSON 出力 | ⚠️ 非推奨：JSON パケットのサポートはファームウェアから削除されました。このフィールドは無視されます | 無効 | . | TLS | サーバーへのセキュアな接続 | 無効 | . | マップ報告 | 公開マップに位置を報告 | 無効 | . このスマートフォンでの MQTT プロキシ . ノード自体がインターネットに接続できない場合、接続中のスマートフォンを MQTT ゲートウェイとして使えます。モジュール設定で「MQTT」と「クライアントへのプロキシを有効化」を有効にすると、アプリがスマートフォンのインターネット接続を通じて、無線機とサーバーの間で MQTT の通信を中継します。 . MQTT 設定画面の上部にある「このスマートフォンでの MQTT プロキシ」トグルは、この中継が現在動作しているかどうかを示し、デバイスの MQTT 設定を編集して保存し直すことなく、すぐに停止（または再開）できます。 . デフォルトの Meshtastic サーバー . コミュニティが mqtt.meshtastic.org で公開サーバーを運用しています。 これは一般的な利用やテストを目的としています。 . ℹ️ 注意： mqtt.meshtastic.org への接続は、TLS のトグルがオフでも常に TLS（ポート 8883）を使用します。 それ以外のサーバーでは、TLS は有効にした場合にのみ使用されます（TLS ありはポート 8883、なしは 1883）。 . 🔒 プライバシー： 公開サーバー上のメッセージは、購読している誰もが読めます。 プライベートな通信には、必ずチャンネルの暗号化を使用してください。 . プライベートサーバー . プライバシーと制御を高めるために、独自の MQTT サーバーを運用できます： . | Mosquitto（軽量、オープンソース） | HiveMQ | EMQX | . 適切な認証情報を設定して、ノードがプライベートサーバーに接続するよう構成します。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E8%A8%AD%E5%AE%9A", - "relUrl": "/zh-rTW/user/mqtt.html#設定" + "relUrl": "/ja-rJP/user/mqtt.html#設定" },"3252": { "doc": "MQTT", - "title": "地圖回報", - "content": "啟用地圖回報後，您的節點將把位置發布至 Meshtastic 社群地圖： . | 可在〔meshmap.net〕(https://meshmap.net) 及類似的社群地圖服務上查看 | 僅分享位置與節點資訊 | 若不希望位置公開顯示，請停用此功能 | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E5%9C%B0%E5%9C%96%E5%9B%9E%E5%A0%B1", + "title": "マップ報告", + "content": "マップ報告を有効にすると、ノードは自分の位置を Meshtastic のコミュニティマップに公開します： . | meshmap.net や、同様のコミュニティマップサービスで表示されます | 共有されるのは位置とノード情報のみです | 位置を公開したくない場合は、これを無効にしてください | . ", + "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": "/zh-rTW/user/mqtt.html#地圖回報" + "relUrl": "/ja-rJP/user/mqtt.html#マップ報告" },"3253": { "doc": "MQTT", - "title": "上行 vs 下行", - "content": "| 方向 | 描述說明 | . | 上行 | 訊息從 mesh 網路 → MQTT 代理伺服器 | . | 下行 | 訊息從 MQTT 代理伺服器 → mesh 網路 | . 可依頻道設定哪些方向為啟用狀態，以控制訊息流向與無線電佔用時間。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E4%B8%8A%E8%A1%8C-vs-%E4%B8%8B%E8%A1%8C", + "title": "アップリンクとダウンリンク", + "content": "| 方向 | 説明 | . | アップリンク | メッシュ → MQTT サーバーへのメッセージ | . | ダウンリンク | MQTT サーバー → メッシュへのメッセージ | . メッセージの流れと電波利用時間を制御するため、どの方向を有効にするかをチャンネルごとに設定します。 . ", + "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": "/zh-rTW/user/mqtt.html#上行-vs-下行" + "relUrl": "/ja-rJP/user/mqtt.html#アップリンクとダウンリンク" },"3254": { "doc": "MQTT", - "title": "訊息格式", - "content": "MQTT 使用 protobuf 訊息格式： . | 格式 | 描述說明 | 使用情境 | . | Protobuf | 二進位 Meshtastic protobuf 編碼 | 節點間 mesh 橋接 | . ⚠️ 注意：韌體已移除 JSON 輸出支援。 Json_enabled 設定在應用程式中仍會顯示，以維持舊版相容性，但對目前的韌體版本不會產生任何效果。 . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E8%A8%8A%E6%81%AF%E6%A0%BC%E5%BC%8F", + "title": "メッセージ形式", + "content": "MQTT は protobuf のメッセージ形式を使用します： . | 形式 | 説明 | 用途 | . | Protobuf | バイナリの Meshtastic protobuf エンコード | ノード間のメッシュ橋渡し | . ⚠️ 注意： JSON 出力のサポートはファームウェアから削除されました。 json_enabled の設定は、以前との互換性のためにアプリ上には表示されますが、現在のファームウェアバージョンには影響しません。 . ", + "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": "/zh-rTW/user/mqtt.html#訊息格式" + "relUrl": "/ja-rJP/user/mqtt.html#メッセージ形式" },"3255": { "doc": "MQTT", - "title": "加密與隱私", - "content": "了解分層加密模型： . | 頻道加密在 mesh 網路上進行，發生於 MQTT 傳輸之前。 若您的頻道已設定 PSK，MQTT 承載內容將已加密——代理伺服器及任何訂閱者只能看到密文。 | MQTT 加密（模組設定）在傳輸至代理伺服器的過程中新增額外的加密層。 此設定可保護中繼資料與路由資訊。 | TLS 對連接至代理伺服器的 TCP 連線進行加密，防止網路層級的竊聽。 | . 🔒 重要：預設公開頻道使用眾所周知的金鑰。 透過 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", + "title": "暗号化とプライバシー", + "content": "階層化された暗号化モデルを理解する： . | チャンネルの暗号化は、MQTT の前にメッシュ上で行われます。 チャンネルに PSK が設定されている場合、MQTT ペイロードはすでに暗号化されています。サーバーや購読者には暗号文しか見えません。 | MQTT の暗号化（モジュールの設定）は、サーバーへの転送のために追加の暗号化レイヤーを加えます。 これはメタデータやルーティング情報を保護します。 | TLS はサーバーへの TCP 接続自体を暗号化し、ネットワークレベルの盗聴を防ぎます。 | . 🔒 重要： デフォルトの公開チャンネルは、よく知られた鍵を使用しています。 デフォルトチャンネルで 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": "/zh-rTW/user/mqtt.html#加密與隱私" + "relUrl": "/ja-rJP/user/mqtt.html#暗号化とプライバシー" },"3256": { "doc": "MQTT", - "title": "最佳實踐", - "content": ". | 在橋接至 MQTT 的頻道上使用頻道層級加密（PSK） | 請勿在無法連接網際網路的節點上啟用 MQTT（這將導致緩衝堆積並浪費記憶體） | 敏感部署環境請使用私有代理伺服器 | 從繁忙的 MQTT 主題下行訊息時，請留意無線電佔用時間——每則下行訊息都會消耗本地 mesh 網路的無線電佔用時間 | 若僅需遠端監控 mesh 網路而不需注入訊息，建議僅啟用上行模式 | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E6%9C%80%E4%BD%B3%E5%AF%A6%E8%B8%90", + "title": "ベストプラクティス", + "content": ". | MQTT に橋渡しするチャンネルでは、チャンネルレベルの暗号化（PSK）を使用します | インターネットに接続できないノードでは MQTT を有効にしないでください（バッファリングしてメモリを浪費します） | 機密性の高い運用にはプライベートサーバーを使用します | 混雑した 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": "/zh-rTW/user/mqtt.html#最佳實踐" + "relUrl": "/ja-rJP/user/mqtt.html#ベストプラクティス" },"3257": { "doc": "MQTT", - "title": "故障排除", - "content": "MQTT 無法連線 . | 檢查 Wi-Fi——閘道節點必須具備有效的網際網路連線（Wi-Fi 或乙太網路）。 MQTT 無法直接透過 LoRa 無線電連結運作。 | 確認登入憑證 — 帳號或密碼錯誤在大多數代理伺服器上會靜默失敗，不顯示錯誤訊息。 請仔細確認是否有多餘的尾端空白字元。 | 防火牆 — 連接埠 1883（MQTT）或 8883（MQTT+TLS）必須開放。 部分網路會封鎖非標準連接埠。 | DNS 解析 — 若使用自訂代理伺服器主機名稱，請確認節點能夠正確解析該名稱。 請嘗試直接使用代理伺服器的 IP 位址進行連線。 | . 訊息未正常橋接 . | 檢查上行／下行設定 — 若僅啟用上行，訊息只會從 mesh 網路流向 MQTT，不會反向傳送。 請在接收端閘道上啟用下行功能。 | 頻道不符 — 兩個閘道必須使用相同頻道且具備相同的 PSK。 不符時，訊息將以不同金鑰加密，導致對方收到的內容為亂碼。 | 主題不符 — 請確認兩個閘道使用相同的根主題。 預設的 msh 適用於公開代理伺服器。 | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E6%95%85%E9%9A%9C%E6%8E%92%E9%99%A4", + "title": "トラブルシューティング", + "content": "MQTT が接続できない . | WiFi を確認： ゲートウェイノードには、有効なインターネット接続（WiFi または Ethernet）が必要です。 MQTT は LoRa の無線リンク自体では動作しません。 | 認証情報を確認： ユーザー名やパスワードが正しくないと、ほとんどのサーバーでは何も表示されずに失敗します。 末尾のスペースがないか、よく確認してください。 | ファイアウォール： ポート 1883（MQTT）または 8883（MQTT+TLS）が開いている必要があります。 一部のネットワークは、標準外のポートをブロックします。 | DNS 解決： カスタムのサーバーホスト名を使う場合は、ノードがそれを解決できるか確認してください。 サーバーの IP アドレスを直接試してみてください。 | . メッセージが橋渡しされない . | アップリンク／ダウンリンクの設定を確認： アップリンクのみが有効な場合、メッセージはメッシュから MQTT へ流れますが、戻ってきません。 受信側のゲートウェイでダウンリンクを有効にしてください。 | チャンネルの不一致： 両方のゲートウェイが、同じ PSK を持つ同じチャンネルを共有している必要があります。 不一致の場合、メッセージは異なる鍵で暗号化され、判読できないデータとして表示されます。 | トピックの不一致： 両方のゲートウェイが同じルートトピックを使用しているか確認してください。 デフォルトの msh は公開サーバーで機能します。 | . ", + "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": "/zh-rTW/user/mqtt.html#故障排除" + "relUrl": "/ja-rJP/user/mqtt.html#トラブルシューティング" },"3258": { "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", + "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": "/zh-rTW/user/mqtt.html#相關主題" + "relUrl": "/ja-rJP/user/mqtt.html#関連トピック" },"3259": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html", - "relUrl": "/cs-rCZ/user/mqtt.html" + "relUrl": "/hu-rHU/user/mqtt.html" },"3260": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#overview", - "relUrl": "/cs-rCZ/user/mqtt.html#overview" + "relUrl": "/hu-rHU/user/mqtt.html#overview" },"3261": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#how-it-works", + "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#how-it-works", - "relUrl": "/cs-rCZ/user/mqtt.html#how-it-works" + "relUrl": "/hu-rHU/user/mqtt.html#how-it-works" },"3262": { "doc": "MQTT", - "title": "Nastavení", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Nastavení | Popis | Výchozí | . | Adresa serveru | MQTT broker hostname | mqtt.meshtastic.org | . | Uživatelské jméno | Broker authentication | meshdev | . | Heslo | Broker authentication | large4cats | . | Kořenové téma | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Povoleno | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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", + "title": "Configuration", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Leírás | Alapértelmezett | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Felhasználónév | Broker authentication | meshdev | . | Jelszó | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Engedélyezve | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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": "/cs-rCZ/user/mqtt.html#nastavení" + "relUrl": "/hu-rHU/user/mqtt.html#configuration" },"3263": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#map-reporting", + "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#map-reporting", - "relUrl": "/cs-rCZ/user/mqtt.html#map-reporting" + "relUrl": "/hu-rHU/user/mqtt.html#map-reporting" },"3264": { "doc": "MQTT", "title": "Uplink vs Downlink", - "content": "| Direction | Popis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#uplink-vs-downlink", + "content": "| Direction | Leírás | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#uplink-vs-downlink", - "relUrl": "/cs-rCZ/user/mqtt.html#uplink-vs-downlink" + "relUrl": "/hu-rHU/user/mqtt.html#uplink-vs-downlink" },"3265": { "doc": "MQTT", "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Popis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#message-formats", + "content": "MQTT uses protobuf message format: . | Format | Leírás | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#message-formats", - "relUrl": "/cs-rCZ/user/mqtt.html#message-formats" + "relUrl": "/hu-rHU/user/mqtt.html#message-formats" },"3266": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#encryption--privacy", + "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#encryption--privacy", - "relUrl": "/cs-rCZ/user/mqtt.html#encryption--privacy" + "relUrl": "/hu-rHU/user/mqtt.html#encryption--privacy" },"3267": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#best-practices", + "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#best-practices", - "relUrl": "/cs-rCZ/user/mqtt.html#best-practices" + "relUrl": "/hu-rHU/user/mqtt.html#best-practices" },"3268": { "doc": "MQTT", "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#troubleshooting", + "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#troubleshooting", - "relUrl": "/cs-rCZ/user/mqtt.html#troubleshooting" + "relUrl": "/hu-rHU/user/mqtt.html#troubleshooting" },"3269": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#related-topics", - "relUrl": "/cs-rCZ/user/mqtt.html#related-topics" + "relUrl": "/hu-rHU/user/mqtt.html#related-topics" },"3270": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html", - "relUrl": "/fr-rFR/user/mqtt.html" + "relUrl": "/ht-rHT/user/mqtt.html" },"3271": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#overview", - "relUrl": "/fr-rFR/user/mqtt.html#overview" + "relUrl": "/ht-rHT/user/mqtt.html#overview" },"3272": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#how-it-works", + "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#how-it-works", - "relUrl": "/fr-rFR/user/mqtt.html#how-it-works" + "relUrl": "/ht-rHT/user/mqtt.html#how-it-works" },"3273": { "doc": "MQTT", "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Description | Par défaut | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Nom d’utilisateur | Broker authentication | meshdev | . | Mot de passe | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Chiffrement | Encrypt MQTT payload | Activé | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Désactivé | . | TLS | Secure connection to broker | Désactivé | . | Map Reporting | Report position to public map | Désactivé | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Deskripsyon | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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": "/fr-rFR/user/mqtt.html#configuration" + "relUrl": "/ht-rHT/user/mqtt.html#configuration" },"3274": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#map-reporting", + "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#map-reporting", - "relUrl": "/fr-rFR/user/mqtt.html#map-reporting" + "relUrl": "/ht-rHT/user/mqtt.html#map-reporting" },"3275": { "doc": "MQTT", "title": "Uplink vs Downlink", - "content": "| Direction | Description | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#uplink-vs-downlink", + "content": "| Direction | Deskripsyon | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#uplink-vs-downlink", - "relUrl": "/fr-rFR/user/mqtt.html#uplink-vs-downlink" + "relUrl": "/ht-rHT/user/mqtt.html#uplink-vs-downlink" },"3276": { "doc": "MQTT", "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Description | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#message-formats", + "content": "MQTT uses protobuf message format: . | Format | Deskripsyon | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#message-formats", - "relUrl": "/fr-rFR/user/mqtt.html#message-formats" + "relUrl": "/ht-rHT/user/mqtt.html#message-formats" },"3277": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#encryption--privacy", + "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#encryption--privacy", - "relUrl": "/fr-rFR/user/mqtt.html#encryption--privacy" + "relUrl": "/ht-rHT/user/mqtt.html#encryption--privacy" },"3278": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#best-practices", + "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#best-practices", - "relUrl": "/fr-rFR/user/mqtt.html#best-practices" + "relUrl": "/ht-rHT/user/mqtt.html#best-practices" },"3279": { "doc": "MQTT", "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#troubleshooting", + "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#troubleshooting", - "relUrl": "/fr-rFR/user/mqtt.html#troubleshooting" + "relUrl": "/ht-rHT/user/mqtt.html#troubleshooting" },"3280": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#related-topics", - "relUrl": "/fr-rFR/user/mqtt.html#related-topics" + "relUrl": "/ht-rHT/user/mqtt.html#related-topics" },"3281": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html", - "relUrl": "/zh-rCN/user/mqtt.html" + "relUrl": "/gl-rES/user/mqtt.html" },"3282": { "doc": "MQTT", - "title": "总览", + "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/zh-rCN/user/mqtt.html#%E6%80%BB%E8%A7%88", + "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#overview", - "relUrl": "/zh-rCN/user/mqtt.html#总览" + "relUrl": "/gl-rES/user/mqtt.html#overview" },"3283": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#how-it-works", + "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#how-it-works", - "relUrl": "/zh-rCN/user/mqtt.html#how-it-works" + "relUrl": "/gl-rES/user/mqtt.html#how-it-works" },"3284": { "doc": "MQTT", "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | 说明 | 默认 | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | 用户名称 | Broker authentication | meshdev | . | 密码 | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | 加密 | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | 禁用 | . | TLS | Secure connection to broker | 禁用 | . | Map Reporting | Report position to public map | 禁用 | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descrición | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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": "/zh-rCN/user/mqtt.html#configuration" + "relUrl": "/gl-rES/user/mqtt.html#configuration" },"3285": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#map-reporting", + "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#map-reporting", - "relUrl": "/zh-rCN/user/mqtt.html#map-reporting" + "relUrl": "/gl-rES/user/mqtt.html#map-reporting" },"3286": { "doc": "MQTT", "title": "Uplink vs Downlink", - "content": "| Direction | 说明 | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#uplink-vs-downlink", + "content": "| Direction | Descrición | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#uplink-vs-downlink", - "relUrl": "/zh-rCN/user/mqtt.html#uplink-vs-downlink" + "relUrl": "/gl-rES/user/mqtt.html#uplink-vs-downlink" },"3287": { "doc": "MQTT", "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | 说明 | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#message-formats", + "content": "MQTT uses protobuf message format: . | Format | Descrición | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#message-formats", - "relUrl": "/zh-rCN/user/mqtt.html#message-formats" + "relUrl": "/gl-rES/user/mqtt.html#message-formats" },"3288": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#encryption--privacy", + "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#encryption--privacy", - "relUrl": "/zh-rCN/user/mqtt.html#encryption--privacy" + "relUrl": "/gl-rES/user/mqtt.html#encryption--privacy" },"3289": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#best-practices", + "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#best-practices", - "relUrl": "/zh-rCN/user/mqtt.html#best-practices" + "relUrl": "/gl-rES/user/mqtt.html#best-practices" },"3290": { "doc": "MQTT", - "title": "问题排查", + "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#%E9%97%AE%E9%A2%98%E6%8E%92%E6%9F%A5", + "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#troubleshooting", - "relUrl": "/zh-rCN/user/mqtt.html#问题排查" + "relUrl": "/gl-rES/user/mqtt.html#troubleshooting" },"3291": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#related-topics", - "relUrl": "/zh-rCN/user/mqtt.html#related-topics" + "relUrl": "/gl-rES/user/mqtt.html#related-topics" },"3292": { "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html", - "relUrl": "/srp/user/mqtt.html" + "relUrl": "/tr-rTR/user/mqtt.html" },"3293": { "doc": "MQTT", - "title": "Overview", + "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/srp/user/mqtt.html#overview", + "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#genel-bak%C4%B1%C5%9F", - "relUrl": "/srp/user/mqtt.html#overview" + "relUrl": "/tr-rTR/user/mqtt.html#genel-bakış" },"3294": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/srp/user/mqtt.html#how-it-works", + "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#how-it-works", - "relUrl": "/srp/user/mqtt.html#how-it-works" + "relUrl": "/tr-rTR/user/mqtt.html#how-it-works" },"3295": { "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Опис | Подразумевано | . | Адреса сервера | MQTT broker hostname | mqtt.meshtastic.org | . | Корисничко име | Broker authentication | meshdev | . | Лозинка | Broker authentication | large4cats | . | Корен тема | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Омогућено | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Онемогућено | . | TLS | Secure connection to broker | Онемогућено | . | Map Reporting | Report position to public map | Онемогућено | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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", + "title": "Yapılandırma", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Açıklaması | Varsayılan | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Kullanıcı adı | Broker authentication | meshdev | . | Şifre | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Açık | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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": "/srp/user/mqtt.html#configuration" + "relUrl": "/tr-rTR/user/mqtt.html#yapılandırma" },"3296": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/srp/user/mqtt.html#map-reporting", + "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#map-reporting", - "relUrl": "/srp/user/mqtt.html#map-reporting" + "relUrl": "/tr-rTR/user/mqtt.html#map-reporting" },"3297": { "doc": "MQTT", "title": "Uplink vs Downlink", - "content": "| Direction | Опис | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/srp/user/mqtt.html#uplink-vs-downlink", + "content": "| Direction | Açıklaması | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#uplink-vs-downlink", - "relUrl": "/srp/user/mqtt.html#uplink-vs-downlink" + "relUrl": "/tr-rTR/user/mqtt.html#uplink-vs-downlink" },"3298": { "doc": "MQTT", "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Опис | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/srp/user/mqtt.html#message-formats", + "content": "MQTT uses protobuf message format: . | Format | Açıklaması | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#message-formats", - "relUrl": "/srp/user/mqtt.html#message-formats" + "relUrl": "/tr-rTR/user/mqtt.html#message-formats" },"3299": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/srp/user/mqtt.html#encryption--privacy", + "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#encryption--privacy", - "relUrl": "/srp/user/mqtt.html#encryption--privacy" + "relUrl": "/tr-rTR/user/mqtt.html#encryption--privacy" },"3300": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/srp/user/mqtt.html#best-practices", + "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#best-practices", - "relUrl": "/srp/user/mqtt.html#best-practices" + "relUrl": "/tr-rTR/user/mqtt.html#best-practices" },"3301": { "doc": "MQTT", "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/srp/user/mqtt.html#troubleshooting", + "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#troubleshooting", - "relUrl": "/srp/user/mqtt.html#troubleshooting" + "relUrl": "/tr-rTR/user/mqtt.html#troubleshooting" },"3302": { "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#related-topics", - "relUrl": "/srp/user/mqtt.html#related-topics" + "relUrl": "/tr-rTR/user/mqtt.html#related-topics" },"3303": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html", - "relUrl": "/sq-rAL/user/mqtt.html" + "relUrl": "/es-rES/user/mqtt.html" },"3304": { "doc": "MQTT", - "title": "Overview", + "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/sq-rAL/user/mqtt.html#overview", + "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#visi%C3%B3n-general", - "relUrl": "/sq-rAL/user/mqtt.html#overview" + "relUrl": "/es-rES/user/mqtt.html#visión-general" },"3305": { "doc": "MQTT", "title": "How It Works", "content": "[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#how-it-works", + "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#how-it-works", - "relUrl": "/sq-rAL/user/mqtt.html#how-it-works" + "relUrl": "/es-rES/user/mqtt.html#how-it-works" },"3306": { "doc": "MQTT", - "title": "Configuration", - "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Përshkrimi | Default | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Encryption | Encrypt MQTT payload | Enabled | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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", + "title": "Configuración", + "content": "Enabling MQTT . | Navigate to Settings → Module Config → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descripción | Por defecto | . | Server Address | MQTT broker hostname | mqtt.meshtastic.org | . | Usuario | Broker authentication | meshdev | . | Contraseña | Broker authentication | large4cats | . | Root Topic | Base topic for messages | msh | . | Cifrado | Encrypt MQTT payload | Habilitado | . | JSON Output | ⚠️ Deprecated — JSON packet support has been removed from firmware; this field is ignored | Disabled | . | TLS | Secure connection to broker | Disabled | . | Map Reporting | Report position to public map | Disabled | . MQTT Proxy on This Phone . If your node 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. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. ℹ️ Note: Connections to mqtt.meshtastic.org always use TLS (port 8883), even if the TLS toggle is off. For any other broker, TLS is used only when you enable it (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": "/sq-rAL/user/mqtt.html#configuration" + "relUrl": "/es-rES/user/mqtt.html#configuración" },"3307": { "doc": "MQTT", "title": "Map Reporting", "content": "When Map Reporting is enabled, your node publishes its position to the Meshtastic community map: . | Visible at meshmap.net and similar community map services | Only position and node info are shared | Disable this if you don’t want your location publicly visible | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#map-reporting", + "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#map-reporting", - "relUrl": "/sq-rAL/user/mqtt.html#map-reporting" + "relUrl": "/es-rES/user/mqtt.html#map-reporting" },"3308": { "doc": "MQTT", "title": "Uplink vs Downlink", - "content": "| Direction | Përshkrimi | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#uplink-vs-downlink", + "content": "| Direction | Descripción | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Configure per-channel which directions are active to control message flow and airtime usage. ", + "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#uplink-vs-downlink", - "relUrl": "/sq-rAL/user/mqtt.html#uplink-vs-downlink" + "relUrl": "/es-rES/user/mqtt.html#uplink-vs-downlink" },"3309": { "doc": "MQTT", "title": "Message Formats", - "content": "MQTT uses protobuf message format: . | Format | Përshkrimi | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#message-formats", + "content": "MQTT uses protobuf message format: . | Format | Descripción | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . ⚠️ Note: JSON output support was removed from firmware. The json_enabled setting is still visible in the app for legacy compatibility but has no effect on current firmware versions. ", + "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#message-formats", - "relUrl": "/sq-rAL/user/mqtt.html#message-formats" + "relUrl": "/es-rES/user/mqtt.html#message-formats" },"3310": { "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. | MQTT encryption (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Important: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#encryption--privacy", + "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#encryption--privacy", - "relUrl": "/sq-rAL/user/mqtt.html#encryption--privacy" + "relUrl": "/es-rES/user/mqtt.html#encryption--privacy" },"3311": { "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 (it will buffer and waste memory) | Use a private broker for sensitive deployments | Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh | Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#best-practices", + "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#best-practices", - "relUrl": "/sq-rAL/user/mqtt.html#best-practices" + "relUrl": "/es-rES/user/mqtt.html#best-practices" },"3312": { "doc": "MQTT", "title": "Troubleshooting", "content": "MQTT Not Connecting . | Check WiFi — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports. | DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly. | . Messages Not Bridging . | Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway. | Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage. | Topic mismatch — ensure both gateways use the same root topic. The default msh works for the public broker. | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#troubleshooting", + "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#troubleshooting", - "relUrl": "/sq-rAL/user/mqtt.html#troubleshooting" + "relUrl": "/es-rES/user/mqtt.html#troubleshooting" },"3313": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#related-topics", - "relUrl": "/sq-rAL/user/mqtt.html#related-topics" + "relUrl": "/es-rES/user/mqtt.html#related-topics" },"3314": { "doc": "Navigation & Deep Links", "title": "Navigation & Deep Links", @@ -23246,2238 +23246,2238 @@ "relUrl": "/en/developer/navigation-and-deep-links.html" },"3321": { - "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" - },"3322": { - "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 | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#device-metrics", - - "relUrl": "/is-rIS/user/node-metrics.html#device-metrics" - },"3323": { - "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 for easy trend analysis — 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" - },"3324": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3325": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#signal-metrics", - - "relUrl": "/is-rIS/user/node-metrics.html#signal-metrics" - },"3326": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Lýsing | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#power-metrics", - - "relUrl": "/is-rIS/user/node-metrics.html#power-metrics" - },"3327": { - "doc": "Node Metrics", - "title": "Ferilkönnun", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#ferilk%C3%B6nnun", - - "relUrl": "/is-rIS/user/node-metrics.html#ferilkönnun" - },"3328": { - "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" - },"3329": { - "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" - },"3330": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"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 | 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" - },"3332": { - "doc": "ノードメトリクス", - "title": "ノードメトリクス", - "content": "ノードの詳細画面では、メッシュ上の各ノードについて、包括的なテレメトリとメトリクスを確認できます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html", - - "relUrl": "/ja-rJP/user/node-metrics.html" - },"3333": { - "doc": "ノードメトリクス", - "title": "デバイスメトリクス", - "content": "各ノードが報告する基本的な動作情報です： . | メトリクス | 説明 | . | バッテリー残量 | 現在のバッテリー残量（％） | . | 電圧 | バッテリー電圧の測定値 | . | チャンネル全体の利用率 | 消費した電波利用時間の割合 | . | 電波利用時間 | このノードが使用した送信時間 | . | 連続稼働時間 | 前回の再起動からの経過時間 | . デバイスメトリクスは、バッテリー残量・電圧・チャンネル利用率・電波利用時間・連続稼働時間の推移を示すトレンドのスパークライン付きの個別カードとして表示されます。 . 💡 ヒント： メトリクスカードをタップすると、履歴データ点を含む詳細なグラフに展開できます。 時間軸はピンチ操作で拡大縮小できます。 . ", - "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#デバイスメトリクス" - },"3334": { - "doc": "ノードメトリクス", - "title": "環境メトリクス", - "content": "環境センサーのデータです（対応ハードウェアが必要）： . | メトリクス | センサーの例 | . | 温度 | BME280, BME680, SHT31 | . | 湿度 | BME280, BME680, SHT31 | . | 大気圧 | BME280, BMP280 | . | ガス抵抗 | BME680 | . | IAQ（大気質） | BME680 | . 環境メトリクスは、傾向を分析しやすいよう時系列でグラフ化されます。温度・湿度・気圧はそれぞれ独立した折れ線グラフになり、測定単位が Y 軸に表示されます。 . 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#環境メトリクス" - },"3335": { - "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 指数 | 最近の PM2.5 の履歴から算出される EPA の NowCast AQI で、色分けされた深刻度ラベルが付きます。 十分な測定値が蓄積されると、PM2.5 の横に表示されます。 | . | CO₂ | ppm | 二酸化炭素の濃度 | . | CO₂ 温度 | °C / °F | CO₂ センサー自体が報告する温度（例：SCD4x） | . | CO₂ 湿度 | % | CO₂ センサーが報告する相対湿度 | . CO₂ の測定値は、大気質をひと目で把握できるよう、深刻度に応じて色分けされます： . | 区分 | CO₂ の範囲（ppm） | 色 | . | 良 | < 1000 | 緑 | . | 空気がこもる | < 2000 | 黄色 | . | 不良 | < 5000 | オレンジ | . | 危険 | < 30000 | 赤 | . | 退避 | ≥ 30000 | 濃い赤 | . 大気質のログ／メトリクスボタンは、ノードが大気質のテレメトリを報告したときにのみ、ノードの詳細画面に表示されます。 大気質ビューでは、次のことができます： . | グラフの期間を選択します。 | メトリクスチップで絞り込みます。データがあるメトリクスのみが表示されます。 | 最新の大気質テレメトリを更新／要求します。 | 表計算ソフトで分析できるよう、CSV にエクスポートします。 | . 💡 ヒント： 大気質メトリクスには、リモートノードに対応する大気質センサーが必要です。 ノードに粒子状物質センサーや CO₂ センサーがない場合、大気質ボタンは表示されません。 対応ハードウェアについては、テレメトリとセンサー を参照してください。 . ", - "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#大気質メトリクス" - },"3336": { - "doc": "ノードメトリクス", - "title": "信号メトリクス", - "content": "無線信号の品質に関する情報です： . | メトリクス | 説明 | . | SN比 | 信号対ノイズ比（高いほど良い） | . | RSSI | 受信信号強度インジケーター（0 に近いほど良い） | . | ノイズフロア | ローカルの背景 RF ノイズ（dBm、値が小さい（負が大きい）ほど静か） | . | ホップ数 | 直前のメッセージのメッシュホップ数 | . 信号品質の目安 . 信号品質は、固定のしきい値ではなく、現在の LoRa モデムプリセットの復調限界に対する SNR で評価されます。同じ SNR でもプリセットによって意味が異なります（例：−15 dB は LongSlow では問題ありませんが、ShortFast では使い物になりません）。 RSSI は表示されますが、評価には含まれません。 limit をプリセットの SNR 限界とすると： . | 品質 | 基準 | . | 良 | SNR がプリセットの限界を上回る | . | 普通 | 限界より 5.5 dB 未満低い | . | 不良 | 限界より 5.5 dB〜7.5 dB 低い | . | なし | 限界より 7.5 dB を超えて低い | . 詳しい説明は、信号メーターを理解する を参照してください。 . 接続中の無線機のローカル統計も、利用可能な場合は信号品質に表示されます。 これらのログには、ノイズフロア、トラフィックカウンター、中継カウンター、オンラインノード数、無線機の連続稼働時間が含まれます。 ノイズフロアのグラフでは、混雑した RF 環境を見分けやすいよう、-85 dBm に破線の基準線が引かれます。 「要求」で接続中の無線機に最新のローカル統計テレメトリレポートを要求し、「消去」でそのノードのローカル統計ログを削除し、「保存」で表示中のローカル統計の履歴を CSV としてエクスポートします。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E4%BF%A1%E5%8F%B7%E3%83%A1%E3%83%88%E3%83%AA%E3%82%AF%E3%82%B9", - - "relUrl": "/ja-rJP/user/node-metrics.html#信号メトリクス" - },"3337": { - "doc": "ノードメトリクス", - "title": "電力メトリクス", - "content": "電力管理のテレメトリです（INA センサーまたは対応ハードウェアが必要）： . | メトリクス | 説明 | . | バス電圧 | 供給電圧 | . | 電流 | 消費電流（ミリアンペア） | . | 電力 | 計算されたワット数 | . ", - "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#電力メトリクス" - },"3338": { - "doc": "ノードメトリクス", - "title": "ルート追跡", - "content": "ルート追跡は、メッセージがメッシュ内を通る経路を表示します： . | ノードの詳細画面で、「ルート追跡」をタップします。 | アプリが対象のノードにルート追跡の要求を送信します。 | 結果には、各ホップが SNR／RSSI の値とともに表示されます。 | . ルート追跡の結果の見方 . 自分 → ノード A (SNR: 8.5) → ノード B (SNR: 5.2) → ターゲット . 各ホップは、メッセージを転送した中継ノードを表します。 . ", - "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#ルート追跡" - },"3339": { - "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#位置ログ" - },"3340": { - "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#隣接ノード情報" - },"3341": { - "doc": "ノードメトリクス", - "title": "メトリクスを表示する", - "content": ". | 「ノード」に移動します。 | 確認したいノードをタップします。 | 詳細タブからメトリクスのカテゴリを選択します。 | . 位置タブには、GPS を共有しているノードの位置データが表示されます： . ⚠️ 注意： メトリクスは、リモートノードが報告した場合にのみ利用できます。 メトリクスは、各ノードのテレメトリ設定で構成された間隔で更新されます。 . ", - "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#メトリクスを表示する" - },"3342": { - "doc": "ノードメトリクス", - "title": "関連トピック", - "content": ". | ノード：ノードリスト、絞り込み、並べ替え | テレメトリとセンサー：対応センサーと設定 | 信号メーター：SNR と RSSI から信号品質を計算する方法 | 探索：ルート追跡の詳細と隣接ノード情報 | 単位とロケール：温度・距離・速度の表示形式 | . ", - "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#関連トピック" - },"3343": { - "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" - },"3344": { - "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 | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#device-metrics", - - "relUrl": "/ca-rES/user/node-metrics.html#device-metrics" - },"3345": { - "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 for easy trend analysis — 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" - },"3346": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3347": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#signal-metrics", - - "relUrl": "/ca-rES/user/node-metrics.html#signal-metrics" - },"3348": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descripció | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#power-metrics", - - "relUrl": "/ca-rES/user/node-metrics.html#power-metrics" - },"3349": { - "doc": "Node Metrics", - "title": "Traçar ruta", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#tra%C3%A7ar-ruta", - - "relUrl": "/ca-rES/user/node-metrics.html#traçar-ruta" - },"3350": { - "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" - },"3351": { - "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" - },"3352": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3353": { - "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 | 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" - },"3354": { - "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" - },"3355": { - "doc": "Node Metrics", - "title": "Метрика уређаја", - "content": "Basic operating information reported by each node: . | Метрика | Опис | . | Ниво батерије | Current battery percentage | . | Напон | Battery voltage reading | . | Искоришћеност канала | Percentage of airtime consumed | . | Време емитовања | Transmission time used by this node | . | Време рада | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "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#метрика-уређаја" - },"3356": { - "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 for easy trend analysis — 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#метрике-сензора" - },"3357": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3358": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#signal-metrics", - - "relUrl": "/sr-rLatn/user/node-metrics.html#signal-metrics" - },"3359": { - "doc": "Node Metrics", - "title": "Мерни подаци о снази", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Метрика | Опис | . | Bus Voltage | Supply voltage | . | Струја | Power draw in milliamps | . | Снага | Calculated wattage | . ", - "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#мерни-подаци-о-снази" - },"3360": { - "doc": "Node Metrics", - "title": "Праћење руте", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "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#праћење-руте" - },"3361": { - "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" - },"3362": { - "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" - },"3363": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3364": { - "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 | 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" - },"3365": { - "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" - },"3366": { - "doc": "Node Metrics", - "title": "Device Metrics", - "content": "Basic operating information reported by each node: . | Metric | 설명 | . | Battery Level | Current battery percentage | . | 전압 | Battery voltage reading | . | 채널 사용 | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | 업타임 | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#device-metrics", - - "relUrl": "/ko-rKR/user/node-metrics.html#device-metrics" - },"3367": { - "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 for easy trend analysis — 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" - },"3368": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3369": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#signal-metrics", - - "relUrl": "/ko-rKR/user/node-metrics.html#signal-metrics" - },"3370": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | 설명 | . | Bus Voltage | Supply voltage | . | 전류 | Power draw in milliamps | . | 전원 | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#power-metrics", - - "relUrl": "/ko-rKR/user/node-metrics.html#power-metrics" - },"3371": { - "doc": "Node Metrics", - "title": "추적 루트", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "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#추적-루트" - },"3372": { - "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#위치-로그" - },"3373": { - "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#이웃-정보" - },"3374": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3375": { - "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 | 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" - },"3376": { - "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" - },"3377": { - "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 | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Timp de functionare | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#valori-dispozitiv", - - "relUrl": "/ro-rRO/user/node-metrics.html#valori-dispozitiv" - },"3378": { - "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 for easy trend analysis — 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" - },"3379": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3380": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#signal-metrics", - - "relUrl": "/ro-rRO/user/node-metrics.html#signal-metrics" - },"3381": { - "doc": "Node Metrics", - "title": "Valori putere", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descriere | . | Bus Voltage | Supply voltage | . | Actual | Power draw in milliamps | . | Alimentare | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#valori-putere", - - "relUrl": "/ro-rRO/user/node-metrics.html#valori-putere" - },"3382": { - "doc": "Node Metrics", - "title": "Trasare traseu", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#trasare-traseu", - - "relUrl": "/ro-rRO/user/node-metrics.html#trasare-traseu" - },"3383": { - "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" - },"3384": { - "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" - },"3385": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3386": { - "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 | 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" - },"3387": { - "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" - },"3388": { - "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 | . | Úsáid cainéil | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#device-metrics", - - "relUrl": "/ga-rIE/user/node-metrics.html#device-metrics" - },"3389": { - "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 for easy trend analysis — 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" - },"3390": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3391": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#signal-metrics", - - "relUrl": "/ga-rIE/user/node-metrics.html#signal-metrics" - },"3392": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Cur síos | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#power-metrics", - - "relUrl": "/ga-rIE/user/node-metrics.html#power-metrics" - },"3393": { - "doc": "Node Metrics", - "title": "Céim rianadóireachta", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "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" - },"3394": { - "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" - },"3395": { - "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" - },"3396": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3397": { - "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 | 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" - },"3398": { - "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" - },"3399": { - "doc": "Node Metrics", - "title": "Device Metrics", - "content": "Basic operating information reported by each node: . | Metric | תיאור | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#device-metrics", - - "relUrl": "/iw-rIL/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 for easy trend analysis — 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" - },"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 | תיאור | . | 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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3402": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#signal-metrics", - - "relUrl": "/iw-rIL/user/node-metrics.html#signal-metrics" - },"3403": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | תיאור | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#power-metrics", - - "relUrl": "/iw-rIL/user/node-metrics.html#power-metrics" - },"3404": { - "doc": "Node Metrics", - "title": "בדיקת מסלול", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "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#בדיקת-מסלול" - },"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/iw-rIL/user/node-metrics.html#position-log", - - "relUrl": "/iw-rIL/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/iw-rIL/user/node-metrics.html#neighbor-info", - - "relUrl": "/iw-rIL/user/node-metrics.html#neighbor-info" - },"3407": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3408": { - "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 | 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" - },"3409": { - "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" - },"3410": { - "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 | . | Kanalutnyttjande | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Upptid | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "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" - },"3411": { - "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 for easy trend analysis — 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" - },"3412": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3413": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#signal-metrics", - - "relUrl": "/sv-rSE/user/node-metrics.html#signal-metrics" - },"3414": { - "doc": "Node Metrics", - "title": "Strömdata", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Beskrivning | . | Bus Voltage | Supply voltage | . | Ström | Power draw in milliamps | . | Ström | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#str%C3%B6mdata", - - "relUrl": "/sv-rSE/user/node-metrics.html#strömdata" - },"3415": { - "doc": "Node Metrics", - "title": "Traceroute (spåra rutt)", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "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" - },"3416": { - "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" - },"3417": { - "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" - },"3418": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3419": { - "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 | 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" - },"3420": { - "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" - },"3421": { - "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 | . | Itilizasyon Kanal | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#device-metrics", - - "relUrl": "/ht-rHT/user/node-metrics.html#device-metrics" - },"3422": { - "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 for easy trend analysis — 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" - },"3423": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3424": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#signal-metrics", - - "relUrl": "/ht-rHT/user/node-metrics.html#signal-metrics" - },"3425": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Deskripsyon | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#power-metrics", - - "relUrl": "/ht-rHT/user/node-metrics.html#power-metrics" - },"3426": { - "doc": "Node Metrics", - "title": "Traceroute", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#traceroute", - - "relUrl": "/ht-rHT/user/node-metrics.html#traceroute" - },"3427": { - "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" - },"3428": { - "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" - },"3429": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3430": { - "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 | 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" - },"3431": { - "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" - },"3432": { - "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ö | Käytetyn lähetysajan käyttöasteen prosenttiosuus | . | Lähetysaika | Tämän radion käyttämä lähetysaika | . | Käyttöaika | Aika viimeisestä uudelleenkäynnistyksestä | . Laitemittarit näytetään erillisinä kortteina, joissa trendikäyrät esittävät akun varaustason, jännitteen, kanavan käyttöasteen, käyttöasteen ja käyttöajan kehitystä ajan kuluessa. 💡 Vinkki: Napauta mitä tahansa mittarikorttia laajentaaksesi sen täydelliseksi kaavioksi, jossa näkyvät historiatiedot. Nipistä lähentääksesi tai loitontaaksesi aika-akselia. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#laitteen-mittausloki", - - "relUrl": "/fi-rFI/user/node-metrics.html#laitteen-mittausloki" - },"3433": { - "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ömittarit esitetään kaavioina ajan kuluessa tapahtuvan trendianalyysin helpottamiseksi — lämpötila, kosteus ja ilmanpaine saavat kukin oman viivakaavionsa, jossa 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" - },"3434": { - "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-AQI, joka lasketaan viimeaikaisesta PM2.5-historiastasi ja esitetään värikoodatulla ilmanlaadun luokituksella. 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 vakavuusasteen mukaan, jotta ilmanlaadun arviointi onnistuu 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. Jos radiossa ei ole hiukkas- tai CO₂-anturia, ilmanlaatupainiketta ei näytetä. 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" - },"3435": { - "doc": "Radion mittarit", - "title": "Signaalin voimakkuudet", - "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). RSSI näytetään, mutta sitä ei käytetä arvioinnissa. Jos 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. Käytä Pyydä-painiketta pyytääksesi yhdistetystä radiosta tuoreen Paikalliset tilastot -telemetriaraportin, Tyhjennä-painiketta poistaaksesi Paikalliset tilastot -lokit kyseiseltä radiolta ja Tallenna-painiketta viedäksesi näkyvän Paikalliset tilastot -historian CSV-tiedostoksi. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#signaalin-voimakkuudet", - - "relUrl": "/fi-rFI/user/node-metrics.html#signaalin-voimakkuudet" - },"3436": { - "doc": "Radion mittarit", - "title": "Virranhallinnan arvot", - "content": "Virranhallintatelemetria (edellyttää INA-anturia tai yhteensopivaa laitteistoa): . | Metrijärjestelmä | Kuvaus | . | Väyläjännite | Syöttöjännite | . | Virta | Virrankulutus milliampeereina | . | Virta | Laskennallinen teho | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#virranhallinnan-arvot", - - "relUrl": "/fi-rFI/user/node-metrics.html#virranhallinnan-arvot" - },"3437": { - "doc": "Radion mittarit", - "title": "Reitinselvitys", - "content": "Reitinselvitys näyttää viestin kulkeman reitin verkossa: . | Napauta radion tietonäytössä Reitinselvitys. | Sovellus lähettää reitinselvityspyynnön kohderadiolle. | Tulokset näyttävät jokaisen hypyn SNR- ja RSSI-arvoineen. | . Reitinselvityksen tulosten lukeminen . Sinä → Radio A (SNR: 8.5) → Radio B (SNR: 5.2) → Kohde . Jokainen hyppy edustaa välitysradiota, joka välitti viestin eteenpäin. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#reitinselvitys", - - "relUrl": "/fi-rFI/user/node-metrics.html#reitinselvitys" - },"3438": { - "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" - },"3439": { - "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" - },"3440": { - "doc": "Radion mittarit", - "title": "Mittareiden tarkastelu", - "content": ". | Siirry kohtaan Radiot. | Napauta radiota, jota haluat tarkastella. | Valitse mittariluokka tietonäytön välilehdistä. | . Sijainti-välilehti näyttää sijaintitiedot radioille, jotka jakavat GPS-sijaintinsa: . ⚠️ Huomautus: Mittarit ovat käytettävissä vain, jos etäradio on raportoinut 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" - },"3441": { - "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 | Haku — reitinselvityksen 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" - },"3442": { - "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" - },"3443": { - "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 | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#device-metrics", - - "relUrl": "/gl-rES/user/node-metrics.html#device-metrics" - },"3444": { - "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 for easy trend analysis — 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" - },"3445": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3446": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#signal-metrics", - - "relUrl": "/gl-rES/user/node-metrics.html#signal-metrics" - },"3447": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descrición | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#power-metrics", - - "relUrl": "/gl-rES/user/node-metrics.html#power-metrics" - },"3448": { - "doc": "Node Metrics", - "title": "Traza-ruta", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#traza-ruta", - - "relUrl": "/gl-rES/user/node-metrics.html#traza-ruta" - },"3449": { - "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" - },"3450": { - "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" - },"3451": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3452": { - "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 | 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" - },"3453": { - "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" - },"3454": { - "doc": "Node Metrics", - "title": "Показники пристрою", - "content": "Basic operating information reported by each node: . | Metric | Опис | . | Battery Level | Current battery percentage | . | Напруга | Battery voltage reading | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Час роботи | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "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#показники-пристрою" - },"3455": { - "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 for easy trend analysis — 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#показники-довкілля" - },"3456": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3457": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#signal-metrics", - - "relUrl": "/uk-rUA/user/node-metrics.html#signal-metrics" - },"3458": { - "doc": "Node Metrics", - "title": "Показники живлення", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Опис | . | Bus Voltage | Supply voltage | . | Поточний | Power draw in milliamps | . | Живлення | Calculated wattage | . ", - "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#показники-живлення" - },"3459": { - "doc": "Node Metrics", - "title": "Маршрут", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "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#маршрут" - },"3460": { - "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" - },"3461": { - "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#інформація-про-сусідів" - },"3462": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3463": { - "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 | 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" - },"3464": { "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" - },"3465": { + },"3322": { "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 | . | Kanalbelegung | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Laufzeit | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#ger%C3%A4tedaten", "relUrl": "/de-rDE/user/node-metrics.html#gerätedaten" - },"3466": { + },"3323": { "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 | . Umgebungsmesswerte werden zur einfachen Trendanalyse im Zeitverlauf dargestellt – Temperatur, Luftfeuchtigkeit und Luftdruck erhalten jeweils ein eigenes Liniendiagramm, wobei die Maßeinheit auf der Y-Achse angezeigt wird. 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" - },"3467": { + },"3324": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3468": { + },"3325": { "doc": "Node Metrics", "title": "Signaldaten", "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). RSSI is shown but is not part of the rating. Letting limit be 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. Verwenden Sie Anfordern, um beim verbundenen Funkgerät einen aktuellen Telemetriebericht zu den lokalen Statistiken (Local Stats) abzurufen, Löschen, um die Protokolle der lokalen Statistiken für diesen Knoten zu löschen, und Speichern, um den sichtbaren Verlauf der lokalen Statistiken als CSV-Datei zu exportieren. ", "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#signaldaten", "relUrl": "/de-rDE/user/node-metrics.html#signaldaten" - },"3469": { + },"3326": { "doc": "Node Metrics", "title": "Energiedaten", "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metrisch | Beschreibung | . | Bus Voltage | Supply voltage | . | Stromstärke | Power draw in milliamps | . | Leistung | Calculated wattage | . ", "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#energiedaten", "relUrl": "/de-rDE/user/node-metrics.html#energiedaten" - },"3470": { + },"3327": { "doc": "Node Metrics", "title": "Traceroute", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#traceroute", "relUrl": "/de-rDE/user/node-metrics.html#traceroute" - },"3471": { + },"3328": { "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" - },"3472": { + },"3329": { "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" - },"3473": { + },"3330": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3474": { + },"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 | Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ", "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#related-topics", "relUrl": "/de-rDE/user/node-metrics.html#related-topics" - },"3475": { + },"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/hr-rHR/user/node-metrics.html", + "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html", - "relUrl": "/hr-rHR/user/node-metrics.html" - },"3476": { + "relUrl": "/ca-rES/user/node-metrics.html" + },"3333": { "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 | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#device-metrics", + "content": "Basic operating information reported by each node: . | Metric | Descripció | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#device-metrics", - "relUrl": "/hr-rHR/user/node-metrics.html#device-metrics" - },"3477": { + "relUrl": "/ca-rES/user/node-metrics.html#device-metrics" + },"3334": { "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 for easy trend analysis — 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", + "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#environment-metrics", - "relUrl": "/hr-rHR/user/node-metrics.html#environment-metrics" - },"3478": { + "relUrl": "/ca-rES/user/node-metrics.html#environment-metrics" + },"3335": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", + "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#air-quality-metrics", - "relUrl": "/hr-rHR/user/node-metrics.html#air-quality-metrics" - },"3479": { + "relUrl": "/ca-rES/user/node-metrics.html#air-quality-metrics" + },"3336": { "doc": "Node Metrics", "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#signal-metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#signal-metrics", - "relUrl": "/hr-rHR/user/node-metrics.html#signal-metrics" - },"3480": { + "relUrl": "/ca-rES/user/node-metrics.html#signal-metrics" + },"3337": { "doc": "Node Metrics", "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Opis | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#power-metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descripció | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#power-metrics", - "relUrl": "/hr-rHR/user/node-metrics.html#power-metrics" - },"3481": { + "relUrl": "/ca-rES/user/node-metrics.html#power-metrics" + },"3338": { "doc": "Node Metrics", - "title": "Traceroute", + "title": "Traçar ruta", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#traceroute", + "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#tra%C3%A7ar-ruta", - "relUrl": "/hr-rHR/user/node-metrics.html#traceroute" - },"3482": { + "relUrl": "/ca-rES/user/node-metrics.html#traçar-ruta" + },"3339": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#position-log", - "relUrl": "/hr-rHR/user/node-metrics.html#position-log" - },"3483": { + "relUrl": "/ca-rES/user/node-metrics.html#position-log" + },"3340": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#neighbor-info", - "relUrl": "/hr-rHR/user/node-metrics.html#neighbor-info" - },"3484": { + "relUrl": "/ca-rES/user/node-metrics.html#neighbor-info" + },"3341": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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", + "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#viewing-metrics", - "relUrl": "/hr-rHR/user/node-metrics.html#viewing-metrics" - },"3485": { + "relUrl": "/ca-rES/user/node-metrics.html#viewing-metrics" + },"3342": { "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 | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#related-topics", - "relUrl": "/hr-rHR/user/node-metrics.html#related-topics" - },"3486": { - "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" - },"3487": { - "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 | . | Kanalo panaudojimas | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#device-metrics", - - "relUrl": "/lt-rLT/user/node-metrics.html#device-metrics" - },"3488": { - "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 for easy trend analysis — 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" - },"3489": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3490": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#signal-metrics", - - "relUrl": "/lt-rLT/user/node-metrics.html#signal-metrics" - },"3491": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Aprašymas | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#power-metrics", - - "relUrl": "/lt-rLT/user/node-metrics.html#power-metrics" - },"3492": { - "doc": "Node Metrics", - "title": "Žinutės kelias", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "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" - },"3493": { - "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" - },"3494": { - "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" - },"3495": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3496": { - "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 | 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" - },"3497": { - "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" - },"3498": { - "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 | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/en/user/node-metrics.html#device-metrics", - - "relUrl": "/en/user/node-metrics.html#device-metrics" - },"3499": { - "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 for easy trend analysis — 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" - },"3500": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3501": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/en/user/node-metrics.html#signal-metrics", - - "relUrl": "/en/user/node-metrics.html#signal-metrics" - },"3502": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Description | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/en/user/node-metrics.html#power-metrics", - - "relUrl": "/en/user/node-metrics.html#power-metrics" - },"3503": { - "doc": "Node Metrics", - "title": "Traceroute", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/en/user/node-metrics.html#traceroute", - - "relUrl": "/en/user/node-metrics.html#traceroute" - },"3504": { - "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" - },"3505": { - "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" - },"3506": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3507": { - "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 | 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" - },"3508": { - "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" - },"3509": { - "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 | . | Csatornahasználat | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Működési idő | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "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" - },"3510": { - "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 for easy trend analysis — 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" - },"3511": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3512": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#signal-metrics", - - "relUrl": "/hu-rHU/user/node-metrics.html#signal-metrics" - },"3513": { - "doc": "Node Metrics", - "title": "Tápellátási metrikák", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Leírás | . | Bus Voltage | Supply voltage | . | Áramerősség | Power draw in milliamps | . | Energia | Calculated wattage | . ", - "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" - },"3514": { - "doc": "Node Metrics", - "title": "Traceroute", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#traceroute", - - "relUrl": "/hu-rHU/user/node-metrics.html#traceroute" - },"3515": { - "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ó" - },"3516": { - "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ó" - },"3517": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3518": { - "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 | 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" - },"3519": { - "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" - },"3520": { - "doc": "Node Metrics", - "title": "Метрики на устройството", - "content": "Basic operating information reported by each node: . | Метрични | Описание | . | Battery Level | Current battery percentage | . | Напрежение | Battery voltage reading | . | Използване на канала | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Време на работа | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "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#метрики-на-устройството" - },"3521": { - "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 for easy trend analysis — 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#показатели-на-околната-среда" - },"3522": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3523": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#signal-metrics", - - "relUrl": "/bg-rBG/user/node-metrics.html#signal-metrics" - },"3524": { - "doc": "Node Metrics", - "title": "Показатели на мощност", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Метрични | Описание | . | Bus Voltage | Supply voltage | . | Текущ | Power draw in milliamps | . | Захранване | Calculated wattage | . ", - "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#показатели-на-мощност" - },"3525": { - "doc": "Node Metrics", - "title": "Трасиране на маршрут", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "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#трасиране-на-маршрут" - },"3526": { - "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#журнал-на-позициите" - },"3527": { - "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" - },"3528": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3529": { - "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 | Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#related-topics", - - "relUrl": "/bg-rBG/user/node-metrics.html#related-topics" - },"3530": { - "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" - },"3531": { - "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 | . | Uporaba kanala | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#device-metrics", - - "relUrl": "/sl-rSI/user/node-metrics.html#device-metrics" - },"3532": { - "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 for easy trend analysis — 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" - },"3533": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3534": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#signal-metrics", - - "relUrl": "/sl-rSI/user/node-metrics.html#signal-metrics" - },"3535": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Opis | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#power-metrics", - - "relUrl": "/sl-rSI/user/node-metrics.html#power-metrics" - },"3536": { - "doc": "Node Metrics", - "title": "Pot", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#pot", - - "relUrl": "/sl-rSI/user/node-metrics.html#pot" - },"3537": { - "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" - },"3538": { - "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" - },"3539": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3540": { - "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 | 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" - },"3541": { - "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" - },"3542": { - "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 | . | Utilização do canal | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Tempo ativo | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#device-metrics", - - "relUrl": "/pt-rPT/user/node-metrics.html#device-metrics" - },"3543": { - "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 for easy trend analysis — 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" - },"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. | 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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3545": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#signal-metrics", - - "relUrl": "/pt-rPT/user/node-metrics.html#signal-metrics" - },"3546": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descrição | . | Bus Voltage | Supply voltage | . | Atual | Power draw in milliamps | . | Energia | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#power-metrics", - - "relUrl": "/pt-rPT/user/node-metrics.html#power-metrics" - },"3547": { - "doc": "Node Metrics", - "title": "Traçar rota", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#tra%C3%A7ar-rota", - - "relUrl": "/pt-rPT/user/node-metrics.html#traçar-rota" - },"3548": { - "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" - },"3549": { - "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" - },"3550": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3551": { - "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 | 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" - },"3552": { + "relUrl": "/ca-rES/user/node-metrics.html#related-topics" + },"3343": { "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" - },"3553": { + },"3344": { "doc": "Node Metrics", "title": "Device Metrics", "content": "Basic operating information reported by each node: . | Metric | Апісанне | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#device-metrics", "relUrl": "/be-rBY/user/node-metrics.html#device-metrics" - },"3554": { + },"3345": { "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 for easy trend analysis — 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" - },"3555": { + },"3346": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3556": { + },"3347": { "doc": "Node Metrics", "title": "Signal Metrics", "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#signal-metrics", "relUrl": "/be-rBY/user/node-metrics.html#signal-metrics" - },"3557": { + },"3348": { "doc": "Node Metrics", "title": "Power Metrics", "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Апісанне | . | Bus Voltage | Supply voltage | . | 3 | Power draw in milliamps | . | Power | Calculated wattage | . ", "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#power-metrics", "relUrl": "/be-rBY/user/node-metrics.html#power-metrics" - },"3558": { + },"3349": { "doc": "Node Metrics", "title": "Traceroute", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#traceroute", "relUrl": "/be-rBY/user/node-metrics.html#traceroute" - },"3559": { + },"3350": { "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#гісторыя-месцазнаходжання" - },"3560": { + },"3351": { "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" - },"3561": { + },"3352": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3562": { + },"3353": { "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 | 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" - },"3563": { + },"3354": { + "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" + },"3355": { + "doc": "Node Metrics", + "title": "Показники пристрою", + "content": "Basic operating information reported by each node: . | Metric | Опис | . | Battery Level | Current battery percentage | . | Напруга | Battery voltage reading | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Час роботи | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "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#показники-пристрою" + },"3356": { + "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 for easy trend analysis — 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#показники-довкілля" + },"3357": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3358": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#signal-metrics", + + "relUrl": "/uk-rUA/user/node-metrics.html#signal-metrics" + },"3359": { + "doc": "Node Metrics", + "title": "Показники живлення", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Опис | . | Bus Voltage | Supply voltage | . | Поточний | Power draw in milliamps | . | Живлення | Calculated wattage | . ", + "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#показники-живлення" + },"3360": { + "doc": "Node Metrics", + "title": "Маршрут", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "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#маршрут" + },"3361": { + "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" + },"3362": { + "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#інформація-про-сусідів" + },"3363": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3364": { + "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 | 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" + },"3365": { + "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" + },"3366": { + "doc": "Node Metrics", + "title": "设备数据", + "content": "Basic operating information reported by each node: . | 公制 | 说明 | . | 电池电量 | Current battery percentage | . | 电压 | Battery voltage reading | . | 频道利用率 | Percentage of airtime consumed | . | 广播时间 | Transmission time used by this node | . | 正常运行时间 | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "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#设备数据" + },"3367": { + "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 for easy trend analysis — 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#传感器指标" + },"3368": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3369": { + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E4%BF%A1%E5%8F%B7%E5%BC%BA%E5%BA%A6", + + "relUrl": "/zh-rCN/user/node-metrics.html#信号强度" + },"3370": { + "doc": "Node Metrics", + "title": "电源计量", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | 公制 | 说明 | . | Bus Voltage | Supply voltage | . | 电流 | Power draw in milliamps | . | 电源 | Calculated wattage | . ", + "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#电源计量" + },"3371": { + "doc": "Node Metrics", + "title": "追踪器", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "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#追踪器" + },"3372": { + "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#定位日志" + },"3373": { + "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#邻居信息" + },"3374": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3375": { + "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 | 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" + },"3376": { + "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" + },"3377": { + "doc": "Node Metrics", + "title": "Метрики на устройството", + "content": "Basic operating information reported by each node: . | Метрични | Описание | . | Battery Level | Current battery percentage | . | Напрежение | Battery voltage reading | . | Използване на канала | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Време на работа | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "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#метрики-на-устройството" + },"3378": { + "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 for easy trend analysis — 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#показатели-на-околната-среда" + },"3379": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3380": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#signal-metrics", + + "relUrl": "/bg-rBG/user/node-metrics.html#signal-metrics" + },"3381": { + "doc": "Node Metrics", + "title": "Показатели на мощност", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Метрични | Описание | . | Bus Voltage | Supply voltage | . | Текущ | Power draw in milliamps | . | Захранване | Calculated wattage | . ", + "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#показатели-на-мощност" + },"3382": { + "doc": "Node Metrics", + "title": "Трасиране на маршрут", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "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#трасиране-на-маршрут" + },"3383": { + "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#журнал-на-позициите" + },"3384": { + "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" + },"3385": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3386": { + "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 | Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#related-topics", + + "relUrl": "/bg-rBG/user/node-metrics.html#related-topics" + },"3387": { + "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" + },"3388": { + "doc": "Node Metrics", + "title": "裝置計量資料", + "content": "Basic operating information reported by each node: . | 公制（公里/公尺） | 描述說明 | . | Battery Level | Current battery percentage | . | 電壓 | Battery voltage reading | . | 頻道使用量 | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | 運行時間 | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "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#裝置計量資料" + },"3389": { + "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 for easy trend analysis — 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#環境計量資料" + },"3390": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3391": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#signal-metrics", + + "relUrl": "/zh-rTW/user/node-metrics.html#signal-metrics" + },"3392": { + "doc": "Node Metrics", + "title": "電源計量資料", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | 公制（公里/公尺） | 描述說明 | . | Bus Voltage | Supply voltage | . | 目前 | Power draw in milliamps | . | 電力 | Calculated wattage | . ", + "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#電源計量資料" + },"3393": { + "doc": "Node Metrics", + "title": "路由追蹤", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "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#路由追蹤" + },"3394": { + "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-rTW/user/node-metrics.html#%E5%AE%9A%E4%BD%8D%E6%97%A5%E8%AA%8C", + + "relUrl": "/zh-rTW/user/node-metrics.html#定位日誌" + },"3395": { + "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#鄰近節點資訊" + },"3396": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3397": { + "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 | Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#related-topics", + + "relUrl": "/zh-rTW/user/node-metrics.html#related-topics" + },"3398": { + "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" + },"3399": { + "doc": "Node Metrics", + "title": "Метрика уређаја", + "content": "Basic operating information reported by each node: . | Метрика | Опис | . | Ниво батерије | Current battery percentage | . | Напон | Battery voltage reading | . | Искоришћеност канала | Percentage of airtime consumed | . | Време емитовања | Transmission time used by this node | . | Време рада | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "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#метрика-уређаја" + },"3400": { + "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 for easy trend analysis — 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#метрике-сензора" + },"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. | Метрика | 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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3402": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#signal-metrics", + + "relUrl": "/sr-rLatn/user/node-metrics.html#signal-metrics" + },"3403": { + "doc": "Node Metrics", + "title": "Мерни подаци о снази", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Метрика | Опис | . | Bus Voltage | Supply voltage | . | Струја | Power draw in milliamps | . | Снага | Calculated wattage | . ", + "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#мерни-подаци-о-снази" + },"3404": { + "doc": "Node Metrics", + "title": "Праћење руте", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "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#праћење-руте" + },"3405": { + "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" + },"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/sr-rLatn/user/node-metrics.html#neighbor-info", + + "relUrl": "/sr-rLatn/user/node-metrics.html#neighbor-info" + },"3407": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3408": { + "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 | 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" + },"3409": { + "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" + },"3410": { + "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 | . | Využití kanálu | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Doba provozu | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "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í" + },"3411": { + "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 for easy trend analysis — 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í" + },"3412": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3413": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#signal-metrics", + + "relUrl": "/cs-rCZ/user/node-metrics.html#signal-metrics" + },"3414": { + "doc": "Node Metrics", + "title": "Metriky napájení", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metrický | Popis | . | Bus Voltage | Supply voltage | . | Proud | Power draw in milliamps | . | Napájení | Calculated wattage | . ", + "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í" + },"3415": { + "doc": "Node Metrics", + "title": "Traceroute", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#traceroute", + + "relUrl": "/cs-rCZ/user/node-metrics.html#traceroute" + },"3416": { + "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" + },"3417": { + "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" + },"3418": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3419": { + "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 | 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" + },"3420": { + "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" + },"3421": { + "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 | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/en/user/node-metrics.html#device-metrics", + + "relUrl": "/en/user/node-metrics.html#device-metrics" + },"3422": { + "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 for easy trend analysis — 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" + },"3423": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3424": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/en/user/node-metrics.html#signal-metrics", + + "relUrl": "/en/user/node-metrics.html#signal-metrics" + },"3425": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Description | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/en/user/node-metrics.html#power-metrics", + + "relUrl": "/en/user/node-metrics.html#power-metrics" + },"3426": { + "doc": "Node Metrics", + "title": "Traceroute", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "url": "/Meshtastic-Android/main/en/user/node-metrics.html#traceroute", + + "relUrl": "/en/user/node-metrics.html#traceroute" + },"3427": { + "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" + },"3428": { + "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" + },"3429": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3430": { + "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 | 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" + },"3431": { + "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" + },"3432": { + "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 | . | Uporaba kanala | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#device-metrics", + + "relUrl": "/sl-rSI/user/node-metrics.html#device-metrics" + },"3433": { + "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 for easy trend analysis — 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" + },"3434": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3435": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#signal-metrics", + + "relUrl": "/sl-rSI/user/node-metrics.html#signal-metrics" + },"3436": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Opis | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#power-metrics", + + "relUrl": "/sl-rSI/user/node-metrics.html#power-metrics" + },"3437": { + "doc": "Node Metrics", + "title": "Pot", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#pot", + + "relUrl": "/sl-rSI/user/node-metrics.html#pot" + },"3438": { + "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" + },"3439": { + "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" + },"3440": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3441": { + "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 | 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" + },"3442": { + "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" + },"3443": { + "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 | . | Utilizzo Canale | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Tempo di attività | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#metriche-dispositivo", + + "relUrl": "/it-rIT/user/node-metrics.html#metriche-dispositivo" + },"3444": { + "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 for easy trend analysis — 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" + },"3445": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3446": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#signal-metrics", + + "relUrl": "/it-rIT/user/node-metrics.html#signal-metrics" + },"3447": { + "doc": "Node Metrics", + "title": "Metriche Alimentazione", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metrico | Descrizione | . | Bus Voltage | Supply voltage | . | Attuale | Power draw in milliamps | . | Alimentazione | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#metriche-alimentazione", + + "relUrl": "/it-rIT/user/node-metrics.html#metriche-alimentazione" + },"3448": { + "doc": "Node Metrics", + "title": "Traceroute", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#traceroute", + + "relUrl": "/it-rIT/user/node-metrics.html#traceroute" + },"3449": { + "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" + },"3450": { + "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" + },"3451": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3452": { + "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 | 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" + },"3453": { "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" - },"3564": { + },"3454": { "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 | . | Utilização do Canal | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#device-metrics", "relUrl": "/pt-rBR/user/node-metrics.html#device-metrics" - },"3565": { + },"3455": { "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 for easy trend analysis — 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" - },"3566": { + },"3456": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3567": { + },"3457": { "doc": "Node Metrics", "title": "Signal Metrics", "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#signal-metrics", "relUrl": "/pt-rBR/user/node-metrics.html#signal-metrics" - },"3568": { + },"3458": { "doc": "Node Metrics", "title": "Power Metrics", "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descrição | . | Bus Voltage | Supply voltage | . | Atual | Power draw in milliamps | . | Energia | Calculated wattage | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#power-metrics", "relUrl": "/pt-rBR/user/node-metrics.html#power-metrics" - },"3569": { + },"3459": { "doc": "Node Metrics", "title": "Traçar rota", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#tra%C3%A7ar-rota", "relUrl": "/pt-rBR/user/node-metrics.html#traçar-rota" - },"3570": { + },"3460": { "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" - },"3571": { + },"3461": { "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" - },"3572": { + },"3462": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3573": { + },"3463": { "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 | 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" - },"3574": { + },"3464": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html", - "relUrl": "/el-rGR/user/node-metrics.html" - },"3575": { + "relUrl": "/is-rIS/user/node-metrics.html" + },"3465": { "doc": "Node Metrics", "title": "Device Metrics", - "content": "Basic operating information reported by each node: . | Metric | Περιγραφή | . | Battery Level | Current battery percentage | . | Τάση | Battery voltage reading | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#device-metrics", + "content": "Basic operating information reported by each node: . | Metric | Lýsing | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#device-metrics", - "relUrl": "/el-rGR/user/node-metrics.html#device-metrics" - },"3576": { + "relUrl": "/is-rIS/user/node-metrics.html#device-metrics" + },"3466": { "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 for easy trend analysis — 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", + "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 for easy trend analysis — 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": "/el-rGR/user/node-metrics.html#environment-metrics" - },"3577": { + "relUrl": "/is-rIS/user/node-metrics.html#environment-metrics" + },"3467": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", - "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", + "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#air-quality-metrics", - "relUrl": "/el-rGR/user/node-metrics.html#air-quality-metrics" - },"3578": { + "relUrl": "/is-rIS/user/node-metrics.html#air-quality-metrics" + },"3468": { "doc": "Node Metrics", "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#signal-metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#signal-metrics", - "relUrl": "/el-rGR/user/node-metrics.html#signal-metrics" - },"3579": { + "relUrl": "/is-rIS/user/node-metrics.html#signal-metrics" + },"3469": { "doc": "Node Metrics", "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Περιγραφή | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#power-metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Lýsing | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#power-metrics", - "relUrl": "/el-rGR/user/node-metrics.html#power-metrics" - },"3580": { + "relUrl": "/is-rIS/user/node-metrics.html#power-metrics" + },"3470": { "doc": "Node Metrics", - "title": "Traceroute", + "title": "Ferilkönnun", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#traceroute", + "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#ferilk%C3%B6nnun", - "relUrl": "/el-rGR/user/node-metrics.html#traceroute" - },"3581": { + "relUrl": "/is-rIS/user/node-metrics.html#ferilkönnun" + },"3471": { "doc": "Node Metrics", - "title": "Αρχείο Καταγραφής Τοποθεσίας", + "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/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", + "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#position-log", - "relUrl": "/el-rGR/user/node-metrics.html#αρχείο-καταγραφής-τοποθεσίας" - },"3582": { + "relUrl": "/is-rIS/user/node-metrics.html#position-log" + },"3472": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#neighbor-info", - "relUrl": "/el-rGR/user/node-metrics.html#neighbor-info" - },"3583": { + "relUrl": "/is-rIS/user/node-metrics.html#neighbor-info" + },"3473": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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", + "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#viewing-metrics", - "relUrl": "/el-rGR/user/node-metrics.html#viewing-metrics" - },"3584": { + "relUrl": "/is-rIS/user/node-metrics.html#viewing-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 | 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", + "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#related-topics", - "relUrl": "/el-rGR/user/node-metrics.html#related-topics" - },"3585": { + "relUrl": "/is-rIS/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/es-rES/user/node-metrics.html", + "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html", - "relUrl": "/es-rES/user/node-metrics.html" - },"3586": { + "relUrl": "/fr-rFR/user/node-metrics.html" + },"3476": { "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 | . | Utilización del canal | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Tiempo encendido | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#m%C3%A9tricas-de-dispositivo", + "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 | . | Utilisation du canal | Percentage of airtime consumed | . | Temps d’émission | Transmission time used by this node | . | Durée de fonctionnement | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#m%C3%A9triques-de-lappareil", - "relUrl": "/es-rES/user/node-metrics.html#métricas-de-dispositivo" - },"3587": { + "relUrl": "/fr-rFR/user/node-metrics.html#métriques-de-lappareil" + },"3477": { "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 for easy trend analysis — 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", + "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 for easy trend analysis — 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": "/es-rES/user/node-metrics.html#métricas-de-entorno" - },"3588": { + "relUrl": "/fr-rFR/user/node-metrics.html#métriques-denvironnement" + },"3478": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", - "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#air-quality-metrics", - "relUrl": "/es-rES/user/node-metrics.html#air-quality-metrics" - },"3589": { + "relUrl": "/fr-rFR/user/node-metrics.html#air-quality-metrics" + },"3479": { "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#signal-metrics", + "title": "Métriques de 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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#m%C3%A9triques-de-signal", - "relUrl": "/es-rES/user/node-metrics.html#signal-metrics" - },"3590": { + "relUrl": "/fr-rFR/user/node-metrics.html#métriques-de-signal" + },"3480": { "doc": "Node Metrics", - "title": "Métricas de Energía", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Métrico | Descripción | . | Bus Voltage | Supply voltage | . | Intensidad | Power draw in milliamps | . | Consumo | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#m%C3%A9tricas-de-energ%C3%ADa", + "title": "Métriques d’alimentation", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Description | . | Bus Voltage | Supply voltage | . | Actif | Power draw in milliamps | . | Alimentation | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#m%C3%A9triques-dalimentation", - "relUrl": "/es-rES/user/node-metrics.html#métricas-de-energía" - },"3591": { + "relUrl": "/fr-rFR/user/node-metrics.html#métriques-dalimentation" + },"3481": { "doc": "Node Metrics", "title": "Traceroute", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#traceroute", + "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#traceroute", - "relUrl": "/es-rES/user/node-metrics.html#traceroute" - },"3592": { + "relUrl": "/fr-rFR/user/node-metrics.html#traceroute" + },"3482": { "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" - },"3593": { - "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" - },"3594": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3595": { - "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 | 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" - },"3596": { - "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" - },"3597": { - "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 | . | Kanal Kullanımı | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Çalışma Süresi | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#device-metrics", - - "relUrl": "/tr-rTR/user/node-metrics.html#device-metrics" - },"3598": { - "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 for easy trend analysis — 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" - },"3599": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3600": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#signal-metrics", - - "relUrl": "/tr-rTR/user/node-metrics.html#signal-metrics" - },"3601": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Açıklaması | . | Bus Voltage | Supply voltage | . | Akım | Power draw in milliamps | . | Güç | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#power-metrics", - - "relUrl": "/tr-rTR/user/node-metrics.html#power-metrics" - },"3602": { - "doc": "Node Metrics", - "title": "Yol izle", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#yol-izle", - - "relUrl": "/tr-rTR/user/node-metrics.html#yol-izle" - },"3603": { - "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ı" - },"3604": { - "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" - },"3605": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3606": { - "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 | 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" - },"3607": { - "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" - },"3608": { - "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 | . | Kanalutnyttelse | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#device-metrics", - - "relUrl": "/no-rNO/user/node-metrics.html#device-metrics" - },"3609": { - "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 for easy trend analysis — 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" - },"3610": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3611": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#signal-metrics", - - "relUrl": "/no-rNO/user/node-metrics.html#signal-metrics" - },"3612": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Beskrivelse | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#power-metrics", - - "relUrl": "/no-rNO/user/node-metrics.html#power-metrics" - },"3613": { - "doc": "Node Metrics", - "title": "Traceroute", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#traceroute", - - "relUrl": "/no-rNO/user/node-metrics.html#traceroute" - },"3614": { - "doc": "Node Metrics", - "title": "Posisjonslogg", + "title": "Journal des positions", "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#journal-des-positions", - "relUrl": "/no-rNO/user/node-metrics.html#posisjonslogg" - },"3615": { + "relUrl": "/fr-rFR/user/node-metrics.html#journal-des-positions" + },"3483": { + "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" + },"3484": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3485": { + "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 | 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" + },"3486": { + "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" + },"3487": { + "doc": "Node Metrics", + "title": "Метрика уређаја", + "content": "Basic operating information reported by each node: . | Метрика | Опис | . | Ниво батерије | Current battery percentage | . | Напон | Battery voltage reading | . | Искоришћеност канала | Percentage of airtime consumed | . | Време емитовања | Transmission time used by this node | . | Време рада | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "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#метрика-уређаја" + },"3488": { + "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 for easy trend analysis — 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#метрике-сензора" + },"3489": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3490": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#signal-metrics", + + "relUrl": "/srp/user/node-metrics.html#signal-metrics" + },"3491": { + "doc": "Node Metrics", + "title": "Мерни подаци о снази", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Метрика | Опис | . | Bus Voltage | Supply voltage | . | Струја | Power draw in milliamps | . | Снага | Calculated wattage | . ", + "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#мерни-подаци-о-снази" + },"3492": { + "doc": "Node Metrics", + "title": "Праћење руте", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "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#праћење-руте" + },"3493": { + "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#логови-позиција" + },"3494": { "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", + "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#neighbor-info", - "relUrl": "/no-rNO/user/node-metrics.html#neighbor-info" - },"3616": { + "relUrl": "/srp/user/node-metrics.html#neighbor-info" + },"3495": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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", + "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#viewing-metrics", - "relUrl": "/no-rNO/user/node-metrics.html#viewing-metrics" - },"3617": { + "relUrl": "/srp/user/node-metrics.html#viewing-metrics" + },"3496": { "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 | 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", + "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#related-topics", - "relUrl": "/no-rNO/user/node-metrics.html#related-topics" - },"3618": { + "relUrl": "/srp/user/node-metrics.html#related-topics" + },"3497": { + "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" + },"3498": { + "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 | . | Využitie kanálu | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Doba prevádzky | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#device-metrics", + + "relUrl": "/sk-rSK/user/node-metrics.html#device-metrics" + },"3499": { + "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 for easy trend analysis — 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" + },"3500": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3501": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#signal-metrics", + + "relUrl": "/sk-rSK/user/node-metrics.html#signal-metrics" + },"3502": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Popis | . | Bus Voltage | Supply voltage | . | Prúd | Power draw in milliamps | . | Napájanie | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#power-metrics", + + "relUrl": "/sk-rSK/user/node-metrics.html#power-metrics" + },"3503": { + "doc": "Node Metrics", + "title": "Trasovanie", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#trasovanie", + + "relUrl": "/sk-rSK/user/node-metrics.html#trasovanie" + },"3504": { + "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" + },"3505": { + "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" + },"3506": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3507": { + "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 | 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" + },"3508": { + "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" + },"3509": { + "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ö | Käytetyn lähetysajan käyttöasteen prosenttiosuus | . | Lähetysaika | Tämän radion käyttämä lähetysaika | . | Käyttöaika | Aika viimeisestä uudelleenkäynnistyksestä | . Laitemittarit näytetään erillisinä kortteina, joissa trendikäyrät esittävät akun varaustason, jännitteen, kanavan käyttöasteen, käyttöasteen ja käyttöajan kehitystä ajan kuluessa. 💡 Vinkki: Napauta mitä tahansa mittarikorttia laajentaaksesi sen täydelliseksi kaavioksi, jossa näkyvät historiatiedot. Nipistä lähentääksesi tai loitontaaksesi aika-akselia. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#laitteen-mittausloki", + + "relUrl": "/fi-rFI/user/node-metrics.html#laitteen-mittausloki" + },"3510": { + "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ömittarit esitetään kaavioina ajan kuluessa tapahtuvan trendianalyysin helpottamiseksi — lämpötila, kosteus ja ilmanpaine saavat kukin oman viivakaavionsa, jossa 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" + },"3511": { + "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-AQI, joka lasketaan viimeaikaisesta PM2.5-historiastasi ja esitetään värikoodatulla ilmanlaadun luokituksella. 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 vakavuusasteen mukaan, jotta ilmanlaadun arviointi onnistuu 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. Jos radiossa ei ole hiukkas- tai CO₂-anturia, ilmanlaatupainiketta ei näytetä. 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" + },"3512": { + "doc": "Radion mittarit", + "title": "Signaalin voimakkuudet", + "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). RSSI näytetään, mutta sitä ei käytetä arvioinnissa. Jos 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. Käytä Pyydä-painiketta pyytääksesi yhdistetystä radiosta tuoreen Paikalliset tilastot -telemetriaraportin, Tyhjennä-painiketta poistaaksesi Paikalliset tilastot -lokit kyseiseltä radiolta ja Tallenna-painiketta viedäksesi näkyvän Paikalliset tilastot -historian CSV-tiedostoksi. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#signaalin-voimakkuudet", + + "relUrl": "/fi-rFI/user/node-metrics.html#signaalin-voimakkuudet" + },"3513": { + "doc": "Radion mittarit", + "title": "Virranhallinnan arvot", + "content": "Virranhallintatelemetria (edellyttää INA-anturia tai yhteensopivaa laitteistoa): . | Metrijärjestelmä | Kuvaus | . | Väyläjännite | Syöttöjännite | . | Virta | Virrankulutus milliampeereina | . | Virta | Laskennallinen teho | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#virranhallinnan-arvot", + + "relUrl": "/fi-rFI/user/node-metrics.html#virranhallinnan-arvot" + },"3514": { + "doc": "Radion mittarit", + "title": "Reitinselvitys", + "content": "Reitinselvitys näyttää viestin kulkeman reitin verkossa: . | Napauta radion tietonäytössä Reitinselvitys. | Sovellus lähettää reitinselvityspyynnön kohderadiolle. | Tulokset näyttävät jokaisen hypyn SNR- ja RSSI-arvoineen. | . Reitinselvityksen tulosten lukeminen . Sinä → Radio A (SNR: 8.5) → Radio B (SNR: 5.2) → Kohde . Jokainen hyppy edustaa välitysradiota, joka välitti viestin eteenpäin. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#reitinselvitys", + + "relUrl": "/fi-rFI/user/node-metrics.html#reitinselvitys" + },"3515": { + "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" + },"3516": { + "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" + },"3517": { + "doc": "Radion mittarit", + "title": "Mittareiden tarkastelu", + "content": ". | Siirry kohtaan Radiot. | Napauta radiota, jota haluat tarkastella. | Valitse mittariluokka tietonäytön välilehdistä. | . Sijainti-välilehti näyttää sijaintitiedot radioille, jotka jakavat GPS-sijaintinsa: . ⚠️ Huomautus: Mittarit ovat käytettävissä vain, jos etäradio on raportoinut 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" + },"3518": { + "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 | Haku — reitinselvityksen 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" + },"3519": { "doc": "Метрики ноды", "title": "Метрики ноды", "content": "Экран сведений о ноде предоставляет подробную телеметрию и метрики для каждой ноды твоей mesh-сети. ", "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html", "relUrl": "/ru-rRU/user/node-metrics.html" - },"3619": { + },"3520": { "doc": "Метрики ноды", "title": "Интервал передачи", "content": "Основная информация о работе, сообщаемая каждой нодой: . | Метрическая | Описание | . | Уровень заряда | Текущий процент заряда батареи | . | Напряжение | Показания напряжения батареи | . | Использование канала | Процент израсходованного эфирного времени | . | Эфирное время | Время передачи, использованное этой нодой | . | Аптайм | Время с момента последней перезагрузки | . Метрики устройства отображаются в виде отдельных карточек с трендовыми спарклайнами, показывающими уровень заряда, напряжение, использование канала, эфирное время и время безотказной работы(аптайма) с течением времени. 💡 Совет: Нажмите на любую карточку метрики, чтобы развернуть её в полноценный график с историческими точками данных. Масштабируйте временную ось щипком. ", "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#интервал-передачи" - },"3620": { + },"3521": { "doc": "Метрики ноды", "title": "Метрики окружения", "content": "Данные датчиков окружающей среды (требуется совместимое оборудование): . | Метрическая | Примеры сенсоров | . | Температура | BME280, BME680, SHT31 | . | Влажность | BME280, BME680, SHT31 | . | Давление на барометре | BME280, BMP280 | . | Сопротивление газа | BME680 | . | IAQ (Качества воздуха) | BME680 | . Метрики окружающей среды отображаются на графиках с течением времени для удобного анализа тенденций — температура, влажность и давление выводятся каждый в виде отдельного линейного графика с единицами измерения по оси Y. Индекс 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#метрики-окружения" - },"3621": { + },"3522": { "doc": "Метрики ноды", "title": "Метрики качества воздуха", "content": "Качество воздуха — это отдельный экран метрик для нод, оснащённых датчиком взвешенных частиц и/или CO₂. Этот экран отделён от показателя IAQ датчика BME680, отображаемого в разделе “Метрики окружающей среды” — IAQ представляет собой единый индекс, основанный на сопротивлении газа, тогда как экран качества воздуха показывает графики исходных измерений взвешенных частиц и CO₂. | Метрическая | Единица | Описание | . | PM1.0 | мкг/м³ | Взвешенные частицы размером до 1,0 микрона | . | PM2.5 | мкг/м³ | Взвешенные частицы размером до 2,5 микрона | . | PM10 | мкг/м³ | Взвешенные частицы размером до 10 микронов | . | AQI | Индекс EPA | AQI EPA по методу NowCast, вычисляемый на основе твоей недавней истории PM2.5, с цветовой меткой уровня опасности. Отображается рядом с PM2.5, как только накопится достаточно показаний. | . | CO₂ | ppm | Концентрация углекислого газа | . | Температура CO₂ | °C / °F | Температура, сообщаемая самим датчиком CO₂ (например, SCD4x) | . | Влажность CO₂ | % | Относительная влажность, сообщаемая датчиком CO₂ | . Показания CO₂ окрашены по уровню опасности, чтобы качество воздуха можно было легко оценить с первого взгляда: . | Диапазон | Диапазон CO₂ (ppm) | Цвет | . | Хороший | < 1000 | Зеленый | . | Душно | < 2000 | Янтарный | . | Плохо | < 5000 | Оранжевый | . | Небезопасно | < 30000 | Красный | . | Эвакуация | ≥ 30000 | Тёмно-красный | . Кнопка журнала/метрик качества воздуха появляется на экране сведений о ноде только в том случае, если нода передала телеметрию о качестве воздуха. В режиме просмотра качества воздуха ты можешь: . | Выбрать временной интервал для графиков. | Фильтровать с помощью кнопок метрик — отображаются только те метрики, по которым есть данные. | Обновить / запросить последнюю телеметрию о качестве воздуха. | Экспортировать в CSV для анализа в электронных таблицах. | . 💡 Совет: Для получения метрик качества воздуха на удалённой ноде должен быть установлен совместимый датчик. Если у ноды нет датчика взвешенных частиц или CO₂, кнопка качества воздуха не появится. См. Телеметрия и датчики для получения информации о поддерживаемом оборудовании. ", "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#метрики-качества-воздуха" - },"3622": { + },"3523": { "doc": "Метрики ноды", "title": "Показатели сигнала", "content": "Информация о качестве радиосигнала: . | Метрическая | Описание | . | Сигнал/шум | Отношение сигнал/шум (SNR) (чем выше, тем лучше) | . | RSSI | Индикатор уровня принимаемого сигнала (Rssi) (чем ближе к 0, тем лучше) | . | Уровень собственных шумов | Местный фоновый радиочастотный шум в дБм (чем более отрицательное значение, тем тише) | . | Количество хопов | Количество хопов в mesh-сети для последнего сообщения | . Оценка качества сигнала . Качество сигнала оценивается по SNR относительно минимального уровня демодуляции активного пресета LoRa-модема, а не по фиксированным порогам — конкретное значение SNR означает разное на разных пресетах (например, −15 дБ нормально для LongSlow, но неприемлемо для ShortFast). RSSI отображается, но не учитывается в оценке. Пусть limit — это предельное значение SNR для пресета: . | Качество | Критерии | . | Хороший | SNR выше предела пресета | . | Средний | менее чем на 5,5 дБ ниже предела | . | Плохой | от 5,5 до 7,5 дБ ниже предела | . | Отсутствует | более чем на 7,5 дБ ниже предела | . См. Понимание измерителя сигнала для полного объяснения. Локальная статистика твоего подключённого радио также отображается в разделе “Качество сигнала”, когда она доступна. Эти журналы включают уровень шума, счётчики трафика, счётчики ретрансляций, количество нод в сети и время работы радио. График уровня шума использует пунктирную опорную линию на уровне -85 дБм, чтобы помочь определить загруженность радиоэфира. Используйте “Запросить”, чтобы запросить у подключённого радио свежий отчёт телеметрии локальной статистики, “Очистить” — чтобы удалить журналы локальной статистики для этой ноды, и “Сохранить” — чтобы экспортировать видимую историю локальной статистики в формате CSV. ", "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D0%BF%D0%BE%D0%BA%D0%B0%D0%B7%D0%B0%D1%82%D0%B5%D0%BB%D0%B8-%D1%81%D0%B8%D0%B3%D0%BD%D0%B0%D0%BB%D0%B0", "relUrl": "/ru-rRU/user/node-metrics.html#показатели-сигнала" - },"3623": { + },"3524": { "doc": "Метрики ноды", "title": "Метрики питания", "content": "Телеметрия управления питанием (требуется датчик INA или совместимое оборудование): . | Метрическая | Описание | . | Напряжение шины | Напряжение питания | . | Ток | Потребляемый ток в миллиамперах | . | Питание | Расчётная мощность | . ", "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#метрики-питания" - },"3624": { + },"3525": { "doc": "Метрики ноды", "title": "Трассировка маршрута", "content": "Трассировка показывает путь сообщения через mesh-сеть: . | На экране сведений о ноде нажмите “Трассировка”. | Приложение отправляет запрос трассировки целевой ноде. | Результаты показывают каждый хоп со значениями SNR/RSSI. | . Чтение результатов трассировки . Ты → Нода A (SNR: 8.5) → Нода B (SNR: 5.2) → Цель . Каждый хоп обозначает ретранслирующую ноду, которая переслала сообщение. ", "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#трассировка-маршрута" - },"3625": { + },"3526": { "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#журнал-местоположения" - },"3626": { + },"3527": { "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#информация-об-окружении" - },"3627": { + },"3528": { "doc": "Метрики ноды", "title": "Просмотр метрик", "content": ". | Перейдите в раздел Ноды. | Нажмите на ноду, которую хотите просмотреть. | Выберите категорию метрик на вкладках с подробностями. | . Вкладка “Местоположение” показывает координаты нод, которые передают GPS-данные: . ⚠️ Примечание: Метрики доступны только в том случае, если они были переданы удалённой нодой. Метрики обновляются с интервалами, настроенными в параметрах телеметрии каждой ноды. ", "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#просмотр-метрик" - },"3628": { + },"3529": { "doc": "Метрики ноды", "title": "Связанные темы", "content": ". | Ноды — список нод, фильтрация и сортировка | Телеметрия и датчики — поддерживаемые датчики и настройка | Измеритель сигнал — как рассчитывается качество сигнала на основе SNR и RSSI | Обнаружение— сведения о трассировке и информации о соседях | Единицы измерения и регион — форматы отображения температуры, расстояния и скорости | . ", "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#связанные-темы" + },"3530": { + "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" + },"3531": { + "doc": "Node Metrics", + "title": "Device Metrics", + "content": "Basic operating information reported by each node: . | Metric | 설명 | . | Battery Level | Current battery percentage | . | 전압 | Battery voltage reading | . | 채널 사용 | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | 업타임 | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#device-metrics", + + "relUrl": "/ko-rKR/user/node-metrics.html#device-metrics" + },"3532": { + "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 for easy trend analysis — 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" + },"3533": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3534": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#signal-metrics", + + "relUrl": "/ko-rKR/user/node-metrics.html#signal-metrics" + },"3535": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | 설명 | . | Bus Voltage | Supply voltage | . | 전류 | Power draw in milliamps | . | 전원 | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#power-metrics", + + "relUrl": "/ko-rKR/user/node-metrics.html#power-metrics" + },"3536": { + "doc": "Node Metrics", + "title": "추적 루트", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "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#추적-루트" + },"3537": { + "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#위치-로그" + },"3538": { + "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#이웃-정보" + },"3539": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3540": { + "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 | 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" + },"3541": { + "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" + },"3542": { + "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 | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#device-metrics", + + "relUrl": "/hr-rHR/user/node-metrics.html#device-metrics" + },"3543": { + "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 for easy trend analysis — 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" + },"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. | 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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3545": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#signal-metrics", + + "relUrl": "/hr-rHR/user/node-metrics.html#signal-metrics" + },"3546": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Opis | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#power-metrics", + + "relUrl": "/hr-rHR/user/node-metrics.html#power-metrics" + },"3547": { + "doc": "Node Metrics", + "title": "Traceroute", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#traceroute", + + "relUrl": "/hr-rHR/user/node-metrics.html#traceroute" + },"3548": { + "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" + },"3549": { + "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" + },"3550": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3551": { + "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 | 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" + },"3552": { + "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" + },"3553": { + "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 | . | Përdorimi i kanalit | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#device-metrics", + + "relUrl": "/sq-rAL/user/node-metrics.html#device-metrics" + },"3554": { + "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 for easy trend analysis — 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" + },"3555": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3556": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#signal-metrics", + + "relUrl": "/sq-rAL/user/node-metrics.html#signal-metrics" + },"3557": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Përshkrimi | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#power-metrics", + + "relUrl": "/sq-rAL/user/node-metrics.html#power-metrics" + },"3558": { + "doc": "Node Metrics", + "title": "Traceroute", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#traceroute", + + "relUrl": "/sq-rAL/user/node-metrics.html#traceroute" + },"3559": { + "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" + },"3560": { + "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" + },"3561": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3562": { + "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 | 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" + },"3563": { + "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" + },"3564": { + "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 | . | Kanalutnyttelse | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#device-metrics", + + "relUrl": "/no-rNO/user/node-metrics.html#device-metrics" + },"3565": { + "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 for easy trend analysis — 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" + },"3566": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3567": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#signal-metrics", + + "relUrl": "/no-rNO/user/node-metrics.html#signal-metrics" + },"3568": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Beskrivelse | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#power-metrics", + + "relUrl": "/no-rNO/user/node-metrics.html#power-metrics" + },"3569": { + "doc": "Node Metrics", + "title": "Traceroute", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#traceroute", + + "relUrl": "/no-rNO/user/node-metrics.html#traceroute" + },"3570": { + "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" + },"3571": { + "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" + },"3572": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3573": { + "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 | 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" + },"3574": { + "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" + },"3575": { + "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 | . | Kanalo panaudojimas | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#device-metrics", + + "relUrl": "/lt-rLT/user/node-metrics.html#device-metrics" + },"3576": { + "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 for easy trend analysis — 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" + },"3577": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3578": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#signal-metrics", + + "relUrl": "/lt-rLT/user/node-metrics.html#signal-metrics" + },"3579": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Aprašymas | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#power-metrics", + + "relUrl": "/lt-rLT/user/node-metrics.html#power-metrics" + },"3580": { + "doc": "Node Metrics", + "title": "Žinutės kelias", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "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" + },"3581": { + "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" + },"3582": { + "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" + },"3583": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3584": { + "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 | 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" + },"3585": { + "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" + },"3586": { + "doc": "Node Metrics", + "title": "Device Metrics", + "content": "Basic operating information reported by each node: . | Metric | الوصف | . | Battery Level | Current battery percentage | . | شدة التيار | Battery voltage reading | . | استخدام القناة | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#device-metrics", + + "relUrl": "/ar-rSA/user/node-metrics.html#device-metrics" + },"3587": { + "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 for easy trend analysis — 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" + },"3588": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3589": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#signal-metrics", + + "relUrl": "/ar-rSA/user/node-metrics.html#signal-metrics" + },"3590": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | الوصف | . | Bus Voltage | Supply voltage | . | الحالي | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#power-metrics", + + "relUrl": "/ar-rSA/user/node-metrics.html#power-metrics" + },"3591": { + "doc": "Node Metrics", + "title": "Traceroute", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#traceroute", + + "relUrl": "/ar-rSA/user/node-metrics.html#traceroute" + },"3592": { + "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#سجل-الموقع" + },"3593": { + "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" + },"3594": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3595": { + "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 | 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" + },"3596": { + "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" + },"3597": { + "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 | . | Utilização do canal | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Tempo ativo | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#device-metrics", + + "relUrl": "/pt-rPT/user/node-metrics.html#device-metrics" + },"3598": { + "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 for easy trend analysis — 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" + },"3599": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3600": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#signal-metrics", + + "relUrl": "/pt-rPT/user/node-metrics.html#signal-metrics" + },"3601": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descrição | . | Bus Voltage | Supply voltage | . | Atual | Power draw in milliamps | . | Energia | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#power-metrics", + + "relUrl": "/pt-rPT/user/node-metrics.html#power-metrics" + },"3602": { + "doc": "Node Metrics", + "title": "Traçar rota", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#tra%C3%A7ar-rota", + + "relUrl": "/pt-rPT/user/node-metrics.html#traçar-rota" + },"3603": { + "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" + },"3604": { + "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" + },"3605": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3606": { + "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 | 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" + },"3607": { + "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" + },"3608": { + "doc": "Node Metrics", + "title": "Device Metrics", + "content": "Basic operating information reported by each node: . | Metric | תיאור | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#device-metrics", + + "relUrl": "/iw-rIL/user/node-metrics.html#device-metrics" + },"3609": { + "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 for easy trend analysis — 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" + },"3610": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3611": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#signal-metrics", + + "relUrl": "/iw-rIL/user/node-metrics.html#signal-metrics" + },"3612": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | תיאור | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#power-metrics", + + "relUrl": "/iw-rIL/user/node-metrics.html#power-metrics" + },"3613": { + "doc": "Node Metrics", + "title": "בדיקת מסלול", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "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#בדיקת-מסלול" + },"3614": { + "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" + },"3615": { + "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" + },"3616": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"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 | 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" + },"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/el-rGR/user/node-metrics.html", + + "relUrl": "/el-rGR/user/node-metrics.html" + },"3619": { + "doc": "Node Metrics", + "title": "Device Metrics", + "content": "Basic operating information reported by each node: . | Metric | Περιγραφή | . | Battery Level | Current battery percentage | . | Τάση | Battery voltage reading | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#device-metrics", + + "relUrl": "/el-rGR/user/node-metrics.html#device-metrics" + },"3620": { + "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 for easy trend analysis — 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" + },"3621": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3622": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#signal-metrics", + + "relUrl": "/el-rGR/user/node-metrics.html#signal-metrics" + },"3623": { + "doc": "Node Metrics", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Περιγραφή | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#power-metrics", + + "relUrl": "/el-rGR/user/node-metrics.html#power-metrics" + },"3624": { + "doc": "Node Metrics", + "title": "Traceroute", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#traceroute", + + "relUrl": "/el-rGR/user/node-metrics.html#traceroute" + },"3625": { + "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#αρχείο-καταγραφής-τοποθεσίας" + },"3626": { + "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" + },"3627": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3628": { + "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 | 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" },"3629": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html", - "relUrl": "/nl-rNL/user/node-metrics.html" + "relUrl": "/ro-rRO/user/node-metrics.html" },"3630": { "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 | . | Kanaalgebruik | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Tijd online | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#device-metrics", + "title": "Valori dispozitiv", + "content": "Basic operating information reported by each node: . | Metric | Descriere | . | Battery Level | Current battery percentage | . | Tensiune | Battery voltage reading | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Timp de functionare | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#valori-dispozitiv", - "relUrl": "/nl-rNL/user/node-metrics.html#device-metrics" + "relUrl": "/ro-rRO/user/node-metrics.html#valori-dispozitiv" },"3631": { "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 for easy trend analysis — 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", + "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 for easy trend analysis — 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": "/nl-rNL/user/node-metrics.html#environment-metrics" + "relUrl": "/ro-rRO/user/node-metrics.html#indicatori-de-mediu" },"3632": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#air-quality-metrics", - "relUrl": "/nl-rNL/user/node-metrics.html#air-quality-metrics" + "relUrl": "/ro-rRO/user/node-metrics.html#air-quality-metrics" },"3633": { "doc": "Node Metrics", "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#signal-metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#signal-metrics", - "relUrl": "/nl-rNL/user/node-metrics.html#signal-metrics" + "relUrl": "/ro-rRO/user/node-metrics.html#signal-metrics" },"3634": { "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Beschrijving | . | Bus Voltage | Supply voltage | . | Huidige | Power draw in milliamps | . | Vermogen | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#power-metrics", + "title": "Valori putere", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descriere | . | Bus Voltage | Supply voltage | . | Actual | Power draw in milliamps | . | Alimentare | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#valori-putere", - "relUrl": "/nl-rNL/user/node-metrics.html#power-metrics" + "relUrl": "/ro-rRO/user/node-metrics.html#valori-putere" },"3635": { "doc": "Node Metrics", - "title": "Traceroute", + "title": "Trasare traseu", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#traceroute", + "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#trasare-traseu", - "relUrl": "/nl-rNL/user/node-metrics.html#traceroute" + "relUrl": "/ro-rRO/user/node-metrics.html#trasare-traseu" },"3636": { "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", + "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": "/nl-rNL/user/node-metrics.html#positie-logboek" + "relUrl": "/ro-rRO/user/node-metrics.html#position-log" },"3637": { "doc": "Node Metrics", - "title": "Neighbor Info", + "title": "Informații vecin", "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#informa%C8%9Bii-vecin", - "relUrl": "/nl-rNL/user/node-metrics.html#neighbor-info" + "relUrl": "/ro-rRO/user/node-metrics.html#informații-vecin" },"3638": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#viewing-metrics", - "relUrl": "/nl-rNL/user/node-metrics.html#viewing-metrics" + "relUrl": "/ro-rRO/user/node-metrics.html#viewing-metrics" },"3639": { "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 | 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#related-topics", - "relUrl": "/nl-rNL/user/node-metrics.html#related-topics" + "relUrl": "/ro-rRO/user/node-metrics.html#related-topics" },"3640": { "doc": "Sõlme mõõdikud", "title": "Sõlme mõõdikud", @@ -25559,2193 +25559,2193 @@ "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html", - "relUrl": "/it-rIT/user/node-metrics.html" + "relUrl": "/ga-rIE/user/node-metrics.html" },"3652": { "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 | . | Utilizzo Canale | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Tempo di attività | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#metriche-dispositivo", + "title": "Device Metrics", + "content": "Basic operating information reported by each node: . | Metric | Cur síos | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | Úsáid cainéil | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#device-metrics", - "relUrl": "/it-rIT/user/node-metrics.html#metriche-dispositivo" + "relUrl": "/ga-rIE/user/node-metrics.html#device-metrics" },"3653": { "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 for easy trend analysis — 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", + "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 for easy trend analysis — 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": "/it-rIT/user/node-metrics.html#metriche-ambientali" + "relUrl": "/ga-rIE/user/node-metrics.html#environment-metrics" },"3654": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", - "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#air-quality-metrics", - "relUrl": "/it-rIT/user/node-metrics.html#air-quality-metrics" + "relUrl": "/ga-rIE/user/node-metrics.html#air-quality-metrics" },"3655": { "doc": "Node Metrics", "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#signal-metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#signal-metrics", - "relUrl": "/it-rIT/user/node-metrics.html#signal-metrics" + "relUrl": "/ga-rIE/user/node-metrics.html#signal-metrics" },"3656": { "doc": "Node Metrics", - "title": "Metriche Alimentazione", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metrico | Descrizione | . | Bus Voltage | Supply voltage | . | Attuale | Power draw in milliamps | . | Alimentazione | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#metriche-alimentazione", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Cur síos | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#power-metrics", - "relUrl": "/it-rIT/user/node-metrics.html#metriche-alimentazione" + "relUrl": "/ga-rIE/user/node-metrics.html#power-metrics" },"3657": { "doc": "Node Metrics", - "title": "Traceroute", + "title": "Céim rianadóireachta", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#traceroute", + "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#c%C3%A9im-rianad%C3%B3ireachta", - "relUrl": "/it-rIT/user/node-metrics.html#traceroute" + "relUrl": "/ga-rIE/user/node-metrics.html#céim-rianadóireachta" },"3658": { "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", + "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": "/it-rIT/user/node-metrics.html#registro-posizione" + "relUrl": "/ga-rIE/user/node-metrics.html#lógáil-seirbhís" },"3659": { "doc": "Node Metrics", - "title": "Informazioni Vicinato", + "title": "Neighbor Info", "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#neighbor-info", - "relUrl": "/it-rIT/user/node-metrics.html#informazioni-vicinato" + "relUrl": "/ga-rIE/user/node-metrics.html#neighbor-info" },"3660": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#viewing-metrics", - "relUrl": "/it-rIT/user/node-metrics.html#viewing-metrics" + "relUrl": "/ga-rIE/user/node-metrics.html#viewing-metrics" },"3661": { "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 | 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#related-topics", - "relUrl": "/it-rIT/user/node-metrics.html#related-topics" + "relUrl": "/ga-rIE/user/node-metrics.html#related-topics" },"3662": { - "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" - },"3663": { - "doc": "Node Metrics", - "title": "Device Metrics", - "content": "Basic operating information reported by each node: . | Metric | الوصف | . | Battery Level | Current battery percentage | . | شدة التيار | Battery voltage reading | . | استخدام القناة | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#device-metrics", - - "relUrl": "/ar-rSA/user/node-metrics.html#device-metrics" - },"3664": { - "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 for easy trend analysis — 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" - },"3665": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3666": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#signal-metrics", - - "relUrl": "/ar-rSA/user/node-metrics.html#signal-metrics" - },"3667": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | الوصف | . | Bus Voltage | Supply voltage | . | الحالي | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#power-metrics", - - "relUrl": "/ar-rSA/user/node-metrics.html#power-metrics" - },"3668": { - "doc": "Node Metrics", - "title": "Traceroute", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#traceroute", - - "relUrl": "/ar-rSA/user/node-metrics.html#traceroute" - },"3669": { - "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#سجل-الموقع" - },"3670": { - "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" - },"3671": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3672": { - "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 | 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" - },"3673": { - "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" - },"3674": { - "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 | . | Využitie kanálu | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Doba prevádzky | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#device-metrics", - - "relUrl": "/sk-rSK/user/node-metrics.html#device-metrics" - },"3675": { - "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 for easy trend analysis — 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" - },"3676": { - "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3677": { - "doc": "Node Metrics", - "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#signal-metrics", - - "relUrl": "/sk-rSK/user/node-metrics.html#signal-metrics" - },"3678": { - "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Popis | . | Bus Voltage | Supply voltage | . | Prúd | Power draw in milliamps | . | Napájanie | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#power-metrics", - - "relUrl": "/sk-rSK/user/node-metrics.html#power-metrics" - },"3679": { - "doc": "Node Metrics", - "title": "Trasovanie", - "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#trasovanie", - - "relUrl": "/sk-rSK/user/node-metrics.html#trasovanie" - },"3680": { - "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" - },"3681": { - "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" - },"3682": { - "doc": "Node Metrics", - "title": "Viewing Metrics", - "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3683": { - "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 | 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" - },"3684": { "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" - },"3685": { + },"3663": { "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 | . | Wykorzystanie kanału | Percentage of airtime consumed | . | Czas nadawania | Transmission time used by this node | . | Czas pracy | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#metryka-urz%C4%85dzenia", "relUrl": "/pl-rPL/user/node-metrics.html#metryka-urządzenia" - },"3686": { + },"3664": { "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 for easy trend analysis — 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" - },"3687": { + },"3665": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" - },"3688": { + },"3666": { "doc": "Node Metrics", "title": "Signal Metrics", "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#signal-metrics", "relUrl": "/pl-rPL/user/node-metrics.html#signal-metrics" - },"3689": { + },"3667": { "doc": "Node Metrics", "title": "Metryki zasilania", "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Opis | . | Bus Voltage | Supply voltage | . | Natężenie | Power draw in milliamps | . | Zasilanie | Calculated wattage | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#metryki-zasilania", "relUrl": "/pl-rPL/user/node-metrics.html#metryki-zasilania" - },"3690": { + },"3668": { "doc": "Node Metrics", "title": "Pokaż trasę", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", "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ę" - },"3691": { + },"3669": { "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" - },"3692": { + },"3670": { "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" - },"3693": { + },"3671": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" - },"3694": { + },"3672": { "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 | 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" - },"3695": { + },"3673": { "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", + "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html", - "relUrl": "/zh-rTW/user/node-metrics.html" - },"3696": { + "relUrl": "/nl-rNL/user/node-metrics.html" + },"3674": { "doc": "Node Metrics", - "title": "裝置計量資料", - "content": "Basic operating information reported by each node: . | 公制（公里/公尺） | 描述說明 | . | Battery Level | Current battery percentage | . | 電壓 | Battery voltage reading | . | 頻道使用量 | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | 運行時間 | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "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", + "title": "Device Metrics", + "content": "Basic operating information reported by each node: . | Metric | Beschrijving | . | Battery Level | Current battery percentage | . | Spanning | Battery voltage reading | . | Kanaalgebruik | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Tijd online | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#device-metrics", - "relUrl": "/zh-rTW/user/node-metrics.html#裝置計量資料" - },"3697": { + "relUrl": "/nl-rNL/user/node-metrics.html#device-metrics" + },"3675": { "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 for easy trend analysis — 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", + "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 for easy trend analysis — 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": "/zh-rTW/user/node-metrics.html#環境計量資料" - },"3698": { + "relUrl": "/nl-rNL/user/node-metrics.html#environment-metrics" + },"3676": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#air-quality-metrics", - "relUrl": "/zh-rTW/user/node-metrics.html#air-quality-metrics" - },"3699": { + "relUrl": "/nl-rNL/user/node-metrics.html#air-quality-metrics" + },"3677": { "doc": "Node Metrics", "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#signal-metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#signal-metrics", - "relUrl": "/zh-rTW/user/node-metrics.html#signal-metrics" - },"3700": { + "relUrl": "/nl-rNL/user/node-metrics.html#signal-metrics" + },"3678": { "doc": "Node Metrics", - "title": "電源計量資料", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | 公制（公里/公尺） | 描述說明 | . | Bus Voltage | Supply voltage | . | 目前 | Power draw in milliamps | . | 電力 | Calculated wattage | . ", - "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", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Beschrijving | . | Bus Voltage | Supply voltage | . | Huidige | Power draw in milliamps | . | Vermogen | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#power-metrics", - "relUrl": "/zh-rTW/user/node-metrics.html#電源計量資料" - },"3701": { + "relUrl": "/nl-rNL/user/node-metrics.html#power-metrics" + },"3679": { "doc": "Node Metrics", - "title": "路由追蹤", + "title": "Traceroute", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#%E8%B7%AF%E7%94%B1%E8%BF%BD%E8%B9%A4", + "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#traceroute", - "relUrl": "/zh-rTW/user/node-metrics.html#路由追蹤" - },"3702": { + "relUrl": "/nl-rNL/user/node-metrics.html#traceroute" + },"3680": { "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-rTW/user/node-metrics.html#%E5%AE%9A%E4%BD%8D%E6%97%A5%E8%AA%8C", + "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": "/zh-rTW/user/node-metrics.html#定位日誌" - },"3703": { + "relUrl": "/nl-rNL/user/node-metrics.html#positie-logboek" + },"3681": { "doc": "Node Metrics", - "title": "鄰近節點資訊", + "title": "Neighbor Info", "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", + "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#neighbor-info", - "relUrl": "/zh-rTW/user/node-metrics.html#鄰近節點資訊" - },"3704": { + "relUrl": "/nl-rNL/user/node-metrics.html#neighbor-info" + },"3682": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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", + "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#viewing-metrics", - "relUrl": "/zh-rTW/user/node-metrics.html#viewing-metrics" - },"3705": { + "relUrl": "/nl-rNL/user/node-metrics.html#viewing-metrics" + },"3683": { "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 | Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#related-topics", + "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#related-topics", - "relUrl": "/zh-rTW/user/node-metrics.html#related-topics" + "relUrl": "/nl-rNL/user/node-metrics.html#related-topics" + },"3684": { + "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" + },"3685": { + "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 | . | Kanalutnyttjande | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Upptid | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "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" + },"3686": { + "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 for easy trend analysis — 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" + },"3687": { + "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. 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" + },"3688": { + "doc": "Node Metrics", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#signal-metrics", + + "relUrl": "/sv-rSE/user/node-metrics.html#signal-metrics" + },"3689": { + "doc": "Node Metrics", + "title": "Strömdata", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Beskrivning | . | Bus Voltage | Supply voltage | . | Ström | Power draw in milliamps | . | Ström | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#str%C3%B6mdata", + + "relUrl": "/sv-rSE/user/node-metrics.html#strömdata" + },"3690": { + "doc": "Node Metrics", + "title": "Traceroute (spåra rutt)", + "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", + "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" + },"3691": { + "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" + },"3692": { + "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" + },"3693": { + "doc": "Node Metrics", + "title": "Viewing Metrics", + "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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" + },"3694": { + "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 | 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" + },"3695": { + "doc": "ノードメトリクス", + "title": "ノードメトリクス", + "content": "ノードの詳細画面では、メッシュ上の各ノードについて、包括的なテレメトリとメトリクスを確認できます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html", + + "relUrl": "/ja-rJP/user/node-metrics.html" + },"3696": { + "doc": "ノードメトリクス", + "title": "デバイスメトリクス", + "content": "各ノードが報告する基本的な動作情報です： . | メトリクス | 説明 | . | バッテリー残量 | 現在のバッテリー残量（％） | . | 電圧 | バッテリー電圧の測定値 | . | チャンネル全体の利用率 | 消費した電波利用時間の割合 | . | 電波利用時間 | このノードが使用した送信時間 | . | 連続稼働時間 | 前回の再起動からの経過時間 | . デバイスメトリクスは、バッテリー残量・電圧・チャンネル利用率・電波利用時間・連続稼働時間の推移を示すトレンドのスパークライン付きの個別カードとして表示されます。 . 💡 ヒント： メトリクスカードをタップすると、履歴データ点を含む詳細なグラフに展開できます。 時間軸はピンチ操作で拡大縮小できます。 . ", + "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#デバイスメトリクス" + },"3697": { + "doc": "ノードメトリクス", + "title": "環境メトリクス", + "content": "環境センサーのデータです（対応ハードウェアが必要）： . | メトリクス | センサーの例 | . | 温度 | BME280, BME680, SHT31 | . | 湿度 | BME280, BME680, SHT31 | . | 大気圧 | BME280, BMP280 | . | ガス抵抗 | BME680 | . | IAQ（大気質） | BME680 | . 環境メトリクスは、傾向を分析しやすいよう時系列でグラフ化されます。温度・湿度・気圧はそれぞれ独立した折れ線グラフになり、測定単位が Y 軸に表示されます。 . 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#環境メトリクス" + },"3698": { + "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 指数 | 最近の PM2.5 の履歴から算出される EPA の NowCast AQI で、色分けされた深刻度ラベルが付きます。 十分な測定値が蓄積されると、PM2.5 の横に表示されます。 | . | CO₂ | ppm | 二酸化炭素の濃度 | . | CO₂ 温度 | °C / °F | CO₂ センサー自体が報告する温度（例：SCD4x） | . | CO₂ 湿度 | % | CO₂ センサーが報告する相対湿度 | . CO₂ の測定値は、大気質をひと目で把握できるよう、深刻度に応じて色分けされます： . | 区分 | CO₂ の範囲（ppm） | 色 | . | 良 | < 1000 | 緑 | . | 空気がこもる | < 2000 | 黄色 | . | 不良 | < 5000 | オレンジ | . | 危険 | < 30000 | 赤 | . | 退避 | ≥ 30000 | 濃い赤 | . 大気質のログ／メトリクスボタンは、ノードが大気質のテレメトリを報告したときにのみ、ノードの詳細画面に表示されます。 大気質ビューでは、次のことができます： . | グラフの期間を選択します。 | メトリクスチップで絞り込みます。データがあるメトリクスのみが表示されます。 | 最新の大気質テレメトリを更新／要求します。 | 表計算ソフトで分析できるよう、CSV にエクスポートします。 | . 💡 ヒント： 大気質メトリクスには、リモートノードに対応する大気質センサーが必要です。 ノードに粒子状物質センサーや CO₂ センサーがない場合、大気質ボタンは表示されません。 対応ハードウェアについては、テレメトリとセンサー を参照してください。 . ", + "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#大気質メトリクス" + },"3699": { + "doc": "ノードメトリクス", + "title": "信号メトリクス", + "content": "無線信号の品質に関する情報です： . | メトリクス | 説明 | . | SN比 | 信号対ノイズ比（高いほど良い） | . | RSSI | 受信信号強度インジケーター（0 に近いほど良い） | . | ノイズフロア | ローカルの背景 RF ノイズ（dBm、値が小さい（負が大きい）ほど静か） | . | ホップ数 | 直前のメッセージのメッシュホップ数 | . 信号品質の目安 . 信号品質は、固定のしきい値ではなく、現在の LoRa モデムプリセットの復調限界に対する SNR で評価されます。同じ SNR でもプリセットによって意味が異なります（例：−15 dB は LongSlow では問題ありませんが、ShortFast では使い物になりません）。 RSSI は表示されますが、評価には含まれません。 limit をプリセットの SNR 限界とすると： . | 品質 | 基準 | . | 良 | SNR がプリセットの限界を上回る | . | 普通 | 限界より 5.5 dB 未満低い | . | 不良 | 限界より 5.5 dB〜7.5 dB 低い | . | なし | 限界より 7.5 dB を超えて低い | . 詳しい説明は、信号メーターを理解する を参照してください。 . 接続中の無線機のローカル統計も、利用可能な場合は信号品質に表示されます。 これらのログには、ノイズフロア、トラフィックカウンター、中継カウンター、オンラインノード数、無線機の連続稼働時間が含まれます。 ノイズフロアのグラフでは、混雑した RF 環境を見分けやすいよう、-85 dBm に破線の基準線が引かれます。 「要求」で接続中の無線機に最新のローカル統計テレメトリレポートを要求し、「消去」でそのノードのローカル統計ログを削除し、「保存」で表示中のローカル統計の履歴を CSV としてエクスポートします。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E4%BF%A1%E5%8F%B7%E3%83%A1%E3%83%88%E3%83%AA%E3%82%AF%E3%82%B9", + + "relUrl": "/ja-rJP/user/node-metrics.html#信号メトリクス" + },"3700": { + "doc": "ノードメトリクス", + "title": "電力メトリクス", + "content": "電力管理のテレメトリです（INA センサーまたは対応ハードウェアが必要）： . | メトリクス | 説明 | . | バス電圧 | 供給電圧 | . | 電流 | 消費電流（ミリアンペア） | . | 電力 | 計算されたワット数 | . ", + "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#電力メトリクス" + },"3701": { + "doc": "ノードメトリクス", + "title": "ルート追跡", + "content": "ルート追跡は、メッセージがメッシュ内を通る経路を表示します： . | ノードの詳細画面で、「ルート追跡」をタップします。 | アプリが対象のノードにルート追跡の要求を送信します。 | 結果には、各ホップが SNR／RSSI の値とともに表示されます。 | . ルート追跡の結果の見方 . 自分 → ノード A (SNR: 8.5) → ノード B (SNR: 5.2) → ターゲット . 各ホップは、メッセージを転送した中継ノードを表します。 . ", + "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#ルート追跡" + },"3702": { + "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#位置ログ" + },"3703": { + "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#隣接ノード情報" + },"3704": { + "doc": "ノードメトリクス", + "title": "メトリクスを表示する", + "content": ". | 「ノード」に移動します。 | 確認したいノードをタップします。 | 詳細タブからメトリクスのカテゴリを選択します。 | . 位置タブには、GPS を共有しているノードの位置データが表示されます： . ⚠️ 注意： メトリクスは、リモートノードが報告した場合にのみ利用できます。 メトリクスは、各ノードのテレメトリ設定で構成された間隔で更新されます。 . ", + "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#メトリクスを表示する" + },"3705": { + "doc": "ノードメトリクス", + "title": "関連トピック", + "content": ". | ノード：ノードリスト、絞り込み、並べ替え | テレメトリとセンサー：対応センサーと設定 | 信号メーター：SNR と RSSI から信号品質を計算する方法 | 探索：ルート追跡の詳細と隣接ノード情報 | 単位とロケール：温度・距離・速度の表示形式 | . ", + "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#関連トピック" },"3706": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html", - "relUrl": "/cs-rCZ/user/node-metrics.html" + "relUrl": "/hu-rHU/user/node-metrics.html" },"3707": { "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 | . | Využití kanálu | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Doba provozu | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#metriky-za%C5%99%C3%ADzen%C3%AD", + "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 | . | Csatornahasználat | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Működési idő | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#eszk%C3%B6zmetrik%C3%A1k", - "relUrl": "/cs-rCZ/user/node-metrics.html#metriky-zařízení" + "relUrl": "/hu-rHU/user/node-metrics.html#eszközmetrikák" },"3708": { "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 for easy trend analysis — 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", + "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 for easy trend analysis — 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": "/cs-rCZ/user/node-metrics.html#metriky-prostředí" + "relUrl": "/hu-rHU/user/node-metrics.html#környezeti-metrikák" },"3709": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#air-quality-metrics", - "relUrl": "/cs-rCZ/user/node-metrics.html#air-quality-metrics" + "relUrl": "/hu-rHU/user/node-metrics.html#air-quality-metrics" },"3710": { "doc": "Node Metrics", "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#signal-metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#signal-metrics", - "relUrl": "/cs-rCZ/user/node-metrics.html#signal-metrics" + "relUrl": "/hu-rHU/user/node-metrics.html#signal-metrics" },"3711": { "doc": "Node Metrics", - "title": "Metriky napájení", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metrický | Popis | . | Bus Voltage | Supply voltage | . | Proud | Power draw in milliamps | . | Napájení | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#metriky-nap%C3%A1jen%C3%AD", + "title": "Tápellátási metrikák", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Leírás | . | Bus Voltage | Supply voltage | . | Áramerősség | Power draw in milliamps | . | Energia | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#t%C3%A1pell%C3%A1t%C3%A1si-metrik%C3%A1k", - "relUrl": "/cs-rCZ/user/node-metrics.html#metriky-napájení" + "relUrl": "/hu-rHU/user/node-metrics.html#tápellátási-metrikák" },"3712": { "doc": "Node Metrics", "title": "Traceroute", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#traceroute", + "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#traceroute", - "relUrl": "/cs-rCZ/user/node-metrics.html#traceroute" + "relUrl": "/hu-rHU/user/node-metrics.html#traceroute" },"3713": { "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", + "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": "/cs-rCZ/user/node-metrics.html#protokol-pozic" + "relUrl": "/hu-rHU/user/node-metrics.html#pozíciónapló" },"3714": { "doc": "Node Metrics", - "title": "Informace o sousedech", + "title": "Szomszéd-információ", "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#szomsz%C3%A9d-inform%C3%A1ci%C3%B3", - "relUrl": "/cs-rCZ/user/node-metrics.html#informace-o-sousedech" + "relUrl": "/hu-rHU/user/node-metrics.html#szomszéd-információ" },"3715": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#viewing-metrics", - "relUrl": "/cs-rCZ/user/node-metrics.html#viewing-metrics" + "relUrl": "/hu-rHU/user/node-metrics.html#viewing-metrics" },"3716": { "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 | 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#related-topics", - "relUrl": "/cs-rCZ/user/node-metrics.html#related-topics" + "relUrl": "/hu-rHU/user/node-metrics.html#related-topics" },"3717": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html", - "relUrl": "/fr-rFR/user/node-metrics.html" + "relUrl": "/ht-rHT/user/node-metrics.html" },"3718": { "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 | . | Utilisation du canal | Percentage of airtime consumed | . | Temps d’émission | Transmission time used by this node | . | Durée de fonctionnement | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#m%C3%A9triques-de-lappareil", + "title": "Device Metrics", + "content": "Basic operating information reported by each node: . | Metric | Deskripsyon | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | Itilizasyon Kanal | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#device-metrics", - "relUrl": "/fr-rFR/user/node-metrics.html#métriques-de-lappareil" + "relUrl": "/ht-rHT/user/node-metrics.html#device-metrics" },"3719": { "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 for easy trend analysis — 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", + "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 for easy trend analysis — 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": "/fr-rFR/user/node-metrics.html#métriques-denvironnement" + "relUrl": "/ht-rHT/user/node-metrics.html#environment-metrics" },"3720": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#air-quality-metrics", - "relUrl": "/fr-rFR/user/node-metrics.html#air-quality-metrics" + "relUrl": "/ht-rHT/user/node-metrics.html#air-quality-metrics" },"3721": { "doc": "Node Metrics", - "title": "Métriques de 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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#m%C3%A9triques-de-signal", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#signal-metrics", - "relUrl": "/fr-rFR/user/node-metrics.html#métriques-de-signal" + "relUrl": "/ht-rHT/user/node-metrics.html#signal-metrics" },"3722": { "doc": "Node Metrics", - "title": "Métriques d’alimentation", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Description | . | Bus Voltage | Supply voltage | . | Actif | Power draw in milliamps | . | Alimentation | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#m%C3%A9triques-dalimentation", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Deskripsyon | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#power-metrics", - "relUrl": "/fr-rFR/user/node-metrics.html#métriques-dalimentation" + "relUrl": "/ht-rHT/user/node-metrics.html#power-metrics" },"3723": { "doc": "Node Metrics", "title": "Traceroute", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#traceroute", + "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#traceroute", - "relUrl": "/fr-rFR/user/node-metrics.html#traceroute" + "relUrl": "/ht-rHT/user/node-metrics.html#traceroute" },"3724": { "doc": "Node Metrics", - "title": "Journal des positions", + "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/fr-rFR/user/node-metrics.html#journal-des-positions", + "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#jounal-pozisyon", - "relUrl": "/fr-rFR/user/node-metrics.html#journal-des-positions" + "relUrl": "/ht-rHT/user/node-metrics.html#jounal-pozisyon" },"3725": { "doc": "Node Metrics", - "title": "Informations sur les voisins", + "title": "Neighbor Info", "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#neighbor-info", - "relUrl": "/fr-rFR/user/node-metrics.html#informations-sur-les-voisins" + "relUrl": "/ht-rHT/user/node-metrics.html#neighbor-info" },"3726": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#viewing-metrics", - "relUrl": "/fr-rFR/user/node-metrics.html#viewing-metrics" + "relUrl": "/ht-rHT/user/node-metrics.html#viewing-metrics" },"3727": { "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 | 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#related-topics", - "relUrl": "/fr-rFR/user/node-metrics.html#related-topics" + "relUrl": "/ht-rHT/user/node-metrics.html#related-topics" },"3728": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html", - "relUrl": "/zh-rCN/user/node-metrics.html" + "relUrl": "/gl-rES/user/node-metrics.html" },"3729": { "doc": "Node Metrics", - "title": "设备数据", - "content": "Basic operating information reported by each node: . | 公制 | 说明 | . | 电池电量 | Current battery percentage | . | 电压 | Battery voltage reading | . | 频道利用率 | Percentage of airtime consumed | . | 广播时间 | Transmission time used by this node | . | 正常运行时间 | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E8%AE%BE%E5%A4%87%E6%95%B0%E6%8D%AE", + "title": "Device Metrics", + "content": "Basic operating information reported by each node: . | Metric | Descrición | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | Channel Utilization | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#device-metrics", - "relUrl": "/zh-rCN/user/node-metrics.html#设备数据" + "relUrl": "/gl-rES/user/node-metrics.html#device-metrics" },"3730": { "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 for easy trend analysis — 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", + "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 for easy trend analysis — 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": "/zh-rCN/user/node-metrics.html#传感器指标" + "relUrl": "/gl-rES/user/node-metrics.html#environment-metrics" },"3731": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", + "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#air-quality-metrics", - "relUrl": "/zh-rCN/user/node-metrics.html#air-quality-metrics" + "relUrl": "/gl-rES/user/node-metrics.html#air-quality-metrics" },"3732": { "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E4%BF%A1%E5%8F%B7%E5%BC%BA%E5%BA%A6", + "title": "Signal Metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#signal-metrics", - "relUrl": "/zh-rCN/user/node-metrics.html#信号强度" + "relUrl": "/gl-rES/user/node-metrics.html#signal-metrics" },"3733": { "doc": "Node Metrics", - "title": "电源计量", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | 公制 | 说明 | . | Bus Voltage | Supply voltage | . | 电流 | Power draw in milliamps | . | 电源 | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E7%94%B5%E6%BA%90%E8%AE%A1%E9%87%8F", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descrición | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#power-metrics", - "relUrl": "/zh-rCN/user/node-metrics.html#电源计量" + "relUrl": "/gl-rES/user/node-metrics.html#power-metrics" },"3734": { "doc": "Node Metrics", - "title": "追踪器", + "title": "Traza-ruta", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E8%BF%BD%E8%B8%AA%E5%99%A8", + "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#traza-ruta", - "relUrl": "/zh-rCN/user/node-metrics.html#追踪器" + "relUrl": "/gl-rES/user/node-metrics.html#traza-ruta" },"3735": { "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", + "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": "/zh-rCN/user/node-metrics.html#定位日志" + "relUrl": "/gl-rES/user/node-metrics.html#position-log" },"3736": { "doc": "Node Metrics", - "title": "邻居信息", + "title": "Neighbor Info", "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", + "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#neighbor-info", - "relUrl": "/zh-rCN/user/node-metrics.html#邻居信息" + "relUrl": "/gl-rES/user/node-metrics.html#neighbor-info" },"3737": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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", + "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#viewing-metrics", - "relUrl": "/zh-rCN/user/node-metrics.html#viewing-metrics" + "relUrl": "/gl-rES/user/node-metrics.html#viewing-metrics" },"3738": { "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 | 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", + "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#related-topics", - "relUrl": "/zh-rCN/user/node-metrics.html#related-topics" + "relUrl": "/gl-rES/user/node-metrics.html#related-topics" },"3739": { "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html", - "relUrl": "/srp/user/node-metrics.html" + "relUrl": "/tr-rTR/user/node-metrics.html" },"3740": { "doc": "Node Metrics", - "title": "Метрика уређаја", - "content": "Basic operating information reported by each node: . | Метрика | Опис | . | Ниво батерије | Current battery percentage | . | Напон | Battery voltage reading | . | Искоришћеност канала | Percentage of airtime consumed | . | Време емитовања | Transmission time used by this node | . | Време рада | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "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", + "title": "Device Metrics", + "content": "Basic operating information reported by each node: . | Metric | Açıklaması | . | Battery Level | Current battery percentage | . | Voltaj | Battery voltage reading | . | Kanal Kullanımı | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Çalışma Süresi | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#device-metrics", - "relUrl": "/srp/user/node-metrics.html#метрика-уређаја" + "relUrl": "/tr-rTR/user/node-metrics.html#device-metrics" },"3741": { "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 for easy trend analysis — 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", + "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 for easy trend analysis — 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": "/srp/user/node-metrics.html#метрике-сензора" + "relUrl": "/tr-rTR/user/node-metrics.html#environment-metrics" },"3742": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", - "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#air-quality-metrics", - "relUrl": "/srp/user/node-metrics.html#air-quality-metrics" + "relUrl": "/tr-rTR/user/node-metrics.html#air-quality-metrics" },"3743": { "doc": "Node Metrics", "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#signal-metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#signal-metrics", - "relUrl": "/srp/user/node-metrics.html#signal-metrics" + "relUrl": "/tr-rTR/user/node-metrics.html#signal-metrics" },"3744": { "doc": "Node Metrics", - "title": "Мерни подаци о снази", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Метрика | Опис | . | Bus Voltage | Supply voltage | . | Струја | Power draw in milliamps | . | Снага | Calculated wattage | . ", - "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", + "title": "Power Metrics", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Açıklaması | . | Bus Voltage | Supply voltage | . | Akım | Power draw in milliamps | . | Güç | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#power-metrics", - "relUrl": "/srp/user/node-metrics.html#мерни-подаци-о-снази" + "relUrl": "/tr-rTR/user/node-metrics.html#power-metrics" },"3745": { "doc": "Node Metrics", - "title": "Праћење руте", + "title": "Yol izle", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#yol-izle", - "relUrl": "/srp/user/node-metrics.html#праћење-руте" + "relUrl": "/tr-rTR/user/node-metrics.html#yol-izle" },"3746": { "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", + "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": "/srp/user/node-metrics.html#логови-позиција" + "relUrl": "/tr-rTR/user/node-metrics.html#konum-kayıtları" },"3747": { "doc": "Node Metrics", - "title": "Neighbor Info", + "title": "Komşu Bilgisi", "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#kom%C5%9Fu-bilgisi", - "relUrl": "/srp/user/node-metrics.html#neighbor-info" + "relUrl": "/tr-rTR/user/node-metrics.html#komşu-bilgisi" },"3748": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#viewing-metrics", - "relUrl": "/srp/user/node-metrics.html#viewing-metrics" + "relUrl": "/tr-rTR/user/node-metrics.html#viewing-metrics" },"3749": { "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 | 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#related-topics", - "relUrl": "/srp/user/node-metrics.html#related-topics" + "relUrl": "/tr-rTR/user/node-metrics.html#related-topics" },"3750": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html", - "relUrl": "/sq-rAL/user/node-metrics.html" + "relUrl": "/es-rES/user/node-metrics.html" },"3751": { "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 | . | Përdorimi i kanalit | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Uptime | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#device-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 | . | Utilización del canal | Percentage of airtime consumed | . | Airtime | Transmission time used by this node | . | Tiempo encendido | Time since last reboot | . Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time. 💡 Tip: Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis. ", + "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#m%C3%A9tricas-de-dispositivo", - "relUrl": "/sq-rAL/user/node-metrics.html#device-metrics" + "relUrl": "/es-rES/user/node-metrics.html#métricas-de-dispositivo" },"3752": { "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 for easy trend analysis — 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", + "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 for easy trend analysis — 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": "/sq-rAL/user/node-metrics.html#environment-metrics" + "relUrl": "/es-rES/user/node-metrics.html#métricas-de-entorno" },"3753": { "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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#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 your 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 to make air quality easy to read 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. If a node has no particulate or CO₂ sensor, the air-quality button won’t appear. See Telemetry & Sensors for supported hardware. ", + "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#air-quality-metrics", - "relUrl": "/sq-rAL/user/node-metrics.html#air-quality-metrics" + "relUrl": "/es-rES/user/node-metrics.html#air-quality-metrics" },"3754": { "doc": "Node Metrics", "title": "Signal Metrics", - "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#signal-metrics", + "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). RSSI is shown but is not part of the rating. Letting limit be 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. Use Request to ask the connected radio for a fresh Local Stats telemetry report, Clear to remove Local Stats logs for that node, and Save to export the visible Local Stats history as CSV. ", + "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#signal-metrics", - "relUrl": "/sq-rAL/user/node-metrics.html#signal-metrics" + "relUrl": "/es-rES/user/node-metrics.html#signal-metrics" },"3755": { "doc": "Node Metrics", - "title": "Power Metrics", - "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Përshkrimi | . | Bus Voltage | Supply voltage | . | Current | Power draw in milliamps | . | Power | Calculated wattage | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#power-metrics", + "title": "Métricas de Energía", + "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Métrico | Descripción | . | Bus Voltage | Supply voltage | . | Intensidad | Power draw in milliamps | . | Consumo | Calculated wattage | . ", + "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#m%C3%A9tricas-de-energ%C3%ADa", - "relUrl": "/sq-rAL/user/node-metrics.html#power-metrics" + "relUrl": "/es-rES/user/node-metrics.html#métricas-de-energía" },"3756": { "doc": "Node Metrics", "title": "Traceroute", "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen, tap Traceroute. | The app sends a traceroute request to the target node. | Results show each hop with SNR/RSSI values. | . Reading Traceroute Results . You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target . Each hop represents a relay node that forwarded the message. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#traceroute", + "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#traceroute", - "relUrl": "/sq-rAL/user/node-metrics.html#traceroute" + "relUrl": "/es-rES/user/node-metrics.html#traceroute" },"3757": { "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", + "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": "/sq-rAL/user/node-metrics.html#regjistri-i-pozitës" + "relUrl": "/es-rES/user/node-metrics.html#registro-de-posiciones" },"3758": { "doc": "Node Metrics", - "title": "Neighbor Info", + "title": "Información de Vecinos", "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", + "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#informaci%C3%B3n-de-vecinos", - "relUrl": "/sq-rAL/user/node-metrics.html#neighbor-info" + "relUrl": "/es-rES/user/node-metrics.html#información-de-vecinos" },"3759": { "doc": "Node Metrics", "title": "Viewing Metrics", "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Select the metric category from the detail tabs. | . The position tab shows 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", + "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#viewing-metrics", - "relUrl": "/sq-rAL/user/node-metrics.html#viewing-metrics" + "relUrl": "/es-rES/user/node-metrics.html#viewing-metrics" },"3760": { "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 | 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", + "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#related-topics", - "relUrl": "/sq-rAL/user/node-metrics.html#related-topics" + "relUrl": "/es-rES/user/node-metrics.html#related-topics" },"3761": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html", - - "relUrl": "/is-rIS/user/nodes.html" - },"3762": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Lýsing | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#node-list", - - "relUrl": "/is-rIS/user/nodes.html#node-list" - },"3763": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#quick-actions", - - "relUrl": "/is-rIS/user/nodes.html#quick-actions" - },"3764": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Lýsing | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#filtering--sorting", - - "relUrl": "/is-rIS/user/nodes.html#filtering--sorting" - },"3765": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#nodes-per-hop", - - "relUrl": "/is-rIS/user/nodes.html#nodes-per-hop" - },"3766": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | Distance | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#node-detail", - - "relUrl": "/is-rIS/user/nodes.html#node-detail" - },"3767": { - "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 | 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" - },"3768": { - "doc": "ノード", - "title": "ノード", - "content": "ノード画面には、メッシュネットワーク上で見えているすべてのデバイスが表示されます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html", - - "relUrl": "/ja-rJP/user/nodes.html" - },"3769": { - "doc": "ノード", - "title": "ノードリスト", - "content": "ノードリストには、無線機が受信したすべてのノードが、次の情報とともに表示されます： . | ノード名： ユーザーが設定した正式名称 | 短縮名： 4 文字の識別子 | 信号品質： 最後に受信したときの信号強度 | 最後の通信： 最後に通信してからの経過時間 | 距離： 推定距離（位置情報が共有されている場合） | バッテリー： リモートノードのバッテリー残量（テレメトリが有効な場合） | . ノードのステータス表示 . | バッジ | 意味 | . | 🟢 オンライン | 過去 2 時間以内に受信したノード | . | ⚪ オフライン | 2 時間を超えて受信していないノード | . | ⭐ お気に入り | ユーザーがお気に入りに設定したノード | . ノードは、過去 2 時間以内に受信していればオンライン、そうでなければオフラインとみなされます。「離席中」のような中間の段階はありません。 . ノードの役割 . ノードには、メッシュ上での動作に影響するさまざまな役割を設定できます： . | 役割 | 説明 | . | クライアント | 標準的なエンドユーザーのデバイス | . | クライアント・ベース | お気に入りノードの通信をルーター・レイトの優先度で扱い、それ以外の通信はクライアントとして扱います | . | クライアント・ミュート | 受信しますが、再送信はしません | . | クライアント・非表示 | クライアント・ミュートと同様で、さらにノードリストから隠れます | . | ルーター | メッセージの転送を優先し、中継のために起動し続けます | . | ルーター・レイト | 1 回だけ再送信するインフラノードですが、他のすべてのモードの後にのみ行います（補助的なカバレッジを提供します） | . | ルーター・クライアント | ⚠️ 非推奨（ファームウェア 2.3.15 で削除）。選択できなくなりました。代わりにルーターまたはクライアントを使用してください | . | リピーター | ⚠️ 非推奨（ファームウェア 2.7.11 で削除）。選択できなくなりました。代わりにルーターを使用してください | . | トラッカー | 一定間隔での位置報告に最適化されています | . | センサー | テレメトリ報告に最適化されています | . | TAK | TAK システムと相互運用します（CoT を送受信） | . | TAK Tracker | TAK の位置報告のみ | . | ロスト＆ファウンド | 回収のために位置を継続的に発信します | . 役割を選ぶ . ほとんどのユーザーは、デフォルトのクライアント役割のままにしてください。 次のような場合は、別の役割を検討してください： . | ルーター： 電源が安定した、固定された高所（屋上、丘の上など）にノードを設置している場合。 ルーターは他のノードのメッセージを中継するために常に起動し続け、メッシュのカバレッジ拡大に不可欠です。 バッテリー駆動のハンドヘルドデバイスではルーターを使用しないでください。 | ルーター・レイト： パケットを常に 1 回だけ再送信するインフラノードですが、他のすべてのルーティングモードの番が終わった後にのみ行います。 主要なルーターと競合することなく、ローカルのクラスターに補助的なカバレッジを提供します。 | クライアント・ベース： お気に入りノードとの間の通信をルーター・レイトの優先度で扱い（それらのメッセージが追加の中継カバレッジを得られるようにします）、それ以外はすべて通常のクライアントとして処理します。 | クライアント・ミュート： メッシュの通信を受信したいが、中継には貢献したくない場合。 監視専用のデバイスや、混雑した地域での輻輳軽減に便利です。 | トラッカー： GPS 位置の発信だけを目的とする無人デバイス（車両、ペット、資産など）。 発信の合間はスリープしてバッテリーを節約します。 | センサー： 環境テレメトリ（気温、湿度、大気質）を報告する無人デバイス。 電力プロファイルはトラッカーと同様です。 | TAK／TAK Tracker： ATAK／WinTAK システムと相互運用する場合にのみ必要です。 詳しくは TAK 連携 を参照してください。 | . 💡 ヒント： メッシュは、ほとんどのノードがクライアントまたはルーターのときに最も良く機能します。 ミュートノードが多すぎるとメッシュの耐障害性が低下し、混雑した地域にルーターが多すぎると輻輳を招くことがあります。 目安としては、地域内のクライアント 5〜10 台につきルーター 1 台です。 . 暗号化の表示 . ノードは、名前の横に暗号化ステータスのアイコンを表示します： . | アイコン | 意味 | . | 🔒 ロック | 通信は PKI（公開鍵基盤）を使用します。本人性が検証された、エンドツーエンドの暗号化です | . | 🔓 ロック解除 | 通信は共有チャンネルの PSK を使用します。暗号化されていますが、本人性は個別には検証されていません | . | ⚠️ 不一致 | 公開鍵の不一致。前回確認時からノードの鍵が変わっています（信頼する前に調べてください） | . 💡 ヒント： PKI 暗号化（ファームウェア 2.5 以降）は、各ノードが固有の鍵ペアを持つため、チャンネル PSK より強力なセキュリティを提供します。 鍵の不一致の警告が表示された場合、そのノードはリセットされたか、侵害された可能性があります。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#%E3%83%8E%E3%83%BC%E3%83%89%E3%83%AA%E3%82%B9%E3%83%88", - - "relUrl": "/ja-rJP/user/nodes.html#ノードリスト" - },"3770": { - "doc": "ノード", - "title": "クイック操作", - "content": "ノードリストから、次のことができます： . | ノードをタップすると詳細ページを表示します | 長押しでクイック操作を表示します： . | お気に入りに追加／解除 | 通知のミュート／解除 | ダイレクトメッセージを送信 | 経路をトレース | 無視／無視の解除 | ノードを削除 | . | . ", - "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#クイック操作" - },"3771": { - "doc": "ノード", - "title": "絞り込みと並べ替え", - "content": "テキスト検索 . 検索欄に入力すると、名前または短縮名でノードを絞り込めます。 絞り込みは、入力に応じてリアルタイムで更新されます。 . 絞り込みトグル . | 絞り込み | 説明 | . | オンラインのみ | 過去 2 時間以内に受信したノードのみを表示します | . | 直接のみ | 直接（中継されていない）接続のノードのみを表示します | . | 不明なノードを含む | まだユーザー情報を送信していないノードを表示します | . | インフラを除外 | インフラ役割のノード（ルーター、ルーター・レイト、クライアント・ベース）を非表示にします | . | MQTT を除外 | MQTT のインターネットブリッジ経由でのみ受信したノードを非表示にします | . | 無視したノードを表示 | 以前に非表示またはミュートにしたノードを表示します | . 並べ替えオプション . | 並べ替え | 説明 | . | 最後の通信（デフォルト） | 最近受信したノードを先頭に表示します | . | アルファベット順 | ノードの正式名称で並べ替えます | . | 距離 | 近いノードを先頭に表示します（位置情報の共有が必要） | . | ホップ数 | 中継ホップ数が少ないノードを先頭に表示します | . | チャンネル | チャンネルインデックスごとにグループ化します | . | MQTT 経由 | MQTT 経由と無線受信でグループ化します | . | お気に入り | お気に入りのノードを先頭に表示します | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#%E7%B5%9E%E3%82%8A%E8%BE%BC%E3%81%BF%E3%81%A8%E4%B8%A6%E3%81%B9%E6%9B%BF%E3%81%88", - - "relUrl": "/ja-rJP/user/nodes.html#絞り込みと並べ替え" - },"3772": { - "doc": "ノード", - "title": "ホップごとのノード数", - "content": "ノードリストのアプリバーにあるホップヒストグラムのアイコンをタップすると、各ホップ距離にいくつのノードがあるかを示す棒グラフが開きます（0 = 直接、1 = 中継 1 回、以下同様）。 グラフを最後の通信の期間（すべての期間、1 時間、8 時間、24 時間）で絞り込むと、現在のメッシュの様子と、より長い期間での様子を比較できます。 ローカルメッシュがどれだけ混雑し、どれだけ広がっているかを手早く把握できます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#%E3%83%9B%E3%83%83%E3%83%97%E3%81%94%E3%81%A8%E3%81%AE%E3%83%8E%E3%83%BC%E3%83%89%E6%95%B0", - - "relUrl": "/ja-rJP/user/nodes.html#ホップごとのノード数" - },"3773": { - "doc": "ノード", - "title": "ノードの詳細", - "content": "ノードをタップすると、詳しい情報を含む詳細ビューが開きます。 メトリクスとテレメトリの詳細については、ノードメトリクス を参照してください。 . 詳細画面には、デバイス情報、位置、操作ボタンが含まれます： . インラインのステータス表示で、主要なメトリクスをひと目で確認できます： . | 指標 | スクリーンショット | . | 信号品質 | | . | バッテリー残量 | | . | ホップ数 | | . | 最後の通信 | | . | 距離 | | . デバイスのリンク（「購入はこちら」） . ノードのハードウェアが認識されると、詳細ビューに折りたたみ式の**「購入はこちら」**セクションが表示され、そのデバイスを購入したり詳しく知ったりできる場所（ベンダーの製品ページ、製品バリエーション、AliExpress・Amazon・対応小売店などの地域のマーケットプレイスの掲載）が、あなたの国に合わせて絞り込まれて表示されます。 各リンクは msh.to のリダイレクトサービスを通じて開きます。 一致するリンクがないデバイスでは、このセクションは表示されません。 . すべてのリンクを一覧できる完全なディレクトリは、「設定 → ヘルプとドキュメント → デバイスのリンク」からも利用できます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#%E3%83%8E%E3%83%BC%E3%83%89%E3%81%AE%E8%A9%B3%E7%B4%B0", - - "relUrl": "/ja-rJP/user/nodes.html#ノードの詳細" - },"3774": { - "doc": "ノード", - "title": "関連トピック", - "content": ". | ノードメトリクス：各ノードの詳細なテレメトリダッシュボード | メッセージとチャンネル：ノードにダイレクトメッセージを送信 | マップとウェイポイント：ノードの位置を地図上で確認 | 探索：トポロジー探索のための経路トレースと隣接ノード情報 | 信号メーター：信号バーの意味を理解する | . ", - "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#関連トピック" - },"3775": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html", - - "relUrl": "/ca-rES/user/nodes.html" - },"3776": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Descripció | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#node-list", - - "relUrl": "/ca-rES/user/nodes.html#node-list" - },"3777": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#quick-actions", - - "relUrl": "/ca-rES/user/nodes.html#quick-actions" - },"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ó | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descripció | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Última notícia | | . | Distància | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#node-detail", - - "relUrl": "/ca-rES/user/nodes.html#node-detail" - },"3781": { - "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 | 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" - },"3782": { - "doc": "Чворови", - "title": "Чворови", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html", - - "relUrl": "/sr-rLatn/user/nodes.html" - },"3783": { - "doc": "Чворови", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Улога | Опис | . | Клијент | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Клијент мутиран | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Иконица | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#node-list", - - "relUrl": "/sr-rLatn/user/nodes.html#node-list" - },"3784": { - "doc": "Чворови", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#quick-actions", - - "relUrl": "/sr-rLatn/user/nodes.html#quick-actions" - },"3785": { - "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 | Опис | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Опис | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#filtering--sorting", - - "relUrl": "/sr-rLatn/user/nodes.html#filtering--sorting" - },"3786": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#nodes-per-hop", - - "relUrl": "/sr-rLatn/user/nodes.html#nodes-per-hop" - },"3787": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Poslednji put viđeno | | . | Udaljenost | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#node-detail", - - "relUrl": "/sr-rLatn/user/nodes.html#node-detail" - },"3788": { - "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 | 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" - },"3789": { - "doc": "노드", - "title": "노드", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html", - - "relUrl": "/ko-rKR/user/nodes.html" - },"3790": { - "doc": "노드", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | 역할 | 설명 | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#node-list", - - "relUrl": "/ko-rKR/user/nodes.html#node-list" - },"3791": { - "doc": "노드", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#quick-actions", - - "relUrl": "/ko-rKR/user/nodes.html#quick-actions" - },"3792": { - "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 . | 필터 | 설명 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | 설명 | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#filtering--sorting", - - "relUrl": "/ko-rKR/user/nodes.html#filtering--sorting" - },"3793": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#nodes-per-hop", - - "relUrl": "/ko-rKR/user/nodes.html#nodes-per-hop" - },"3794": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | 최근 수신 | | . | 거리 | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#node-detail", - - "relUrl": "/ko-rKR/user/nodes.html#node-detail" - },"3795": { - "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 | 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" - },"3796": { - "doc": "Noduri", - "title": "Noduri", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html", - - "relUrl": "/ro-rRO/user/nodes.html" - },"3797": { - "doc": "Noduri", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Descriere | . | Client | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#node-list", - - "relUrl": "/ro-rRO/user/nodes.html#node-list" - },"3798": { - "doc": "Noduri", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#quick-actions", - - "relUrl": "/ro-rRO/user/nodes.html#quick-actions" - },"3799": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descriere | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#filtering--sorting", - - "relUrl": "/ro-rRO/user/nodes.html#filtering--sorting" - },"3800": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#nodes-per-hop", - - "relUrl": "/ro-rRO/user/nodes.html#nodes-per-hop" - },"3801": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Ultima recepție | | . | Distanță | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#node-detail", - - "relUrl": "/ro-rRO/user/nodes.html#node-detail" - },"3802": { - "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 | 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" - },"3803": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html", - - "relUrl": "/ga-rIE/user/nodes.html" - },"3804": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Cur síos | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#node-list", - - "relUrl": "/ga-rIE/user/nodes.html#node-list" - },"3805": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#quick-actions", - - "relUrl": "/ga-rIE/user/nodes.html#quick-actions" - },"3806": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Cur síos | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#filtering--sorting", - - "relUrl": "/ga-rIE/user/nodes.html#filtering--sorting" - },"3807": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#nodes-per-hop", - - "relUrl": "/ga-rIE/user/nodes.html#nodes-per-hop" - },"3808": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Deiridh chluinmhu | | . | Sáth | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#node-detail", - - "relUrl": "/ga-rIE/user/nodes.html#node-detail" - },"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 | 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" - },"3810": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html", - - "relUrl": "/iw-rIL/user/nodes.html" - },"3811": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | תיאור | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#node-list", - - "relUrl": "/iw-rIL/user/nodes.html#node-list" - },"3812": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#quick-actions", - - "relUrl": "/iw-rIL/user/nodes.html#quick-actions" - },"3813": { - "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 . | פילטר | תיאור | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | תיאור | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#filtering--sorting", - - "relUrl": "/iw-rIL/user/nodes.html#filtering--sorting" - },"3814": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#nodes-per-hop", - - "relUrl": "/iw-rIL/user/nodes.html#nodes-per-hop" - },"3815": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | מרחק | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#node-detail", - - "relUrl": "/iw-rIL/user/nodes.html#node-detail" - },"3816": { - "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 | 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" - },"3817": { - "doc": "Noder", - "title": "Noder", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html", - - "relUrl": "/sv-rSE/user/nodes.html" - },"3818": { - "doc": "Noder", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Roll | Beskrivning | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#node-list", - - "relUrl": "/sv-rSE/user/nodes.html#node-list" - },"3819": { - "doc": "Noder", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Ta bort nod | . | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#quick-actions", - - "relUrl": "/sv-rSE/user/nodes.html#quick-actions" - },"3820": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Beskrivning | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#filtering--sorting", - - "relUrl": "/sv-rSE/user/nodes.html#filtering--sorting" - },"3821": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#nodes-per-hop", - - "relUrl": "/sv-rSE/user/nodes.html#nodes-per-hop" - },"3822": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Batterinivå | | . | Hop count | | . | Senast hörd | | . | Avstånd | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#node-detail", - - "relUrl": "/sv-rSE/user/nodes.html#node-detail" - },"3823": { - "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 | 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" - },"3824": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html", - - "relUrl": "/ht-rHT/user/nodes.html" - },"3825": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Deskripsyon | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#node-list", - - "relUrl": "/ht-rHT/user/nodes.html#node-list" - },"3826": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#quick-actions", - - "relUrl": "/ht-rHT/user/nodes.html#quick-actions" - },"3827": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Deskripsyon | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#filtering--sorting", - - "relUrl": "/ht-rHT/user/nodes.html#filtering--sorting" - },"3828": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#nodes-per-hop", - - "relUrl": "/ht-rHT/user/nodes.html#nodes-per-hop" - },"3829": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Dènye fwa li tande | | . | Distans | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#node-detail", - - "relUrl": "/ht-rHT/user/nodes.html#node-detail" - },"3830": { - "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 | 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" - },"3831": { - "doc": "Laitteet", - "title": "Laitteet", - "content": "Radiot-näyttö näyttää kaikki verkossasi näkyvät laitteet. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html", - - "relUrl": "/fi-rFI/user/nodes.html" - },"3832": { - "doc": "Laitteet", - "title": "Radiolista", - "content": "Radioluettelo näyttää kaikki radiot, joista radiosi on vastaanottanut tietoja, mukaan lukien: . | Radion nimi — käyttäjän määrittämä pitkä nimi | Lyhyt nimi — 4-merkkinen tunniste | Signaalin laatu — viimeksi vastaanotetun signaalin voimakkuus | 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ä) | . Radion tilailmaisimet . | Tunniste | Tarkoitus | . | 🟢 Verkossa | Radio kuultu viimeisen 2 tunnin aikana | . | Ei verkkossa | Radiosta ei ole kuultu yli 2 tuntiin | . | ⭐ Suosikki | Käyttäjän suosikiksi merkitsemä radio | . Radio katsotaan verkossa olevaksi, jos siitä on kuultu viimeisten 2 tunnin aikana. Muussa tapauksessa se katsotaan poissa verkosta olevaksi — erillistä “poissa”-tilaa ei ole. Radion roolit . Radioille voidaan määrittää erilaisia rooleja, jotka vaikuttavat niiden toimintaan verkossa: . | Rooli | Kuvaus | . | Client | Tavallinen loppukäyttäjän laite | . | 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 | . | Kadonnut ja löydetty | Jatkuva sijaintimajakka löytämistä varten | . Roolin valitseminen . 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. Älä käytä Router-roolia akkukäyttöisissä käsilaitteissa. | 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. Hyödyllinen vain valvontaan käytettäville laitteille tai ruuhkien vähentämiseen tiheästi rakennetuilla alueilla. | Tracker — Valvomaton laite, jonka ainoa tarkoitus on lähettää GPS-sijaintiaan (esim. ajoneuvo, lemmikki tai omaisuus). Nukkuu lähetysten välillä akun säästämiseksi. | Sensor — Valvomaton laite, joka raportoi ympäristötelemetriaa (lämpötila, kosteus, ilmanlaatu). 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 -rooleja heikentää verkon toimintavarmuutta, kun taas liian suuri määrä Router-rooleja tiheässä verkossa voi aiheuttaa ruuhkaa. Hyvä nyrkkisääntö on yksi Router jokaista 5–10 Client-roolia kohden alueellasi. Salausilmaisimet . Radiot näyttävät nimensä vieressä salauksen tilaa kuvaavat kuvakkeet: . | Kuvake | Merkitys | . | 🔒 Lukittu | Yhteys käyttää PKI:tä (julkisen avaimen infrastruktuuria) — päästä päähän salattu ja varmennetulla identiteetillä suojattu. | . | 🔓 Lukitsematon | Yhteys käyttää PKI:tä (julkisen avaimen infrastruktuuria) — päästä päähän salattu ja varmennetulla identiteetillä suojattu. | . | ⚠️ Ei täsmää | Julkinen avain ei täsmää — radion avain on muuttunut viime näkemän jälkeen (tutki ennen luottamista). | . 💡 Vinkki: PKI-salaus (laiteohjelmisto 2.5+) tarjoaa vahvemman suojauksen kuin kanavan PSK-avain, koska jokaisella radiolla on oma yksilöllinen avainparinsa. Jos näet avaimen täsmäämättömyysvaroituksen, radio on voitu nollata tai sen tietoturva on voinut vaarantua. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#radiolista", - - "relUrl": "/fi-rFI/user/nodes.html#radiolista" - },"3833": { - "doc": "Laitteet", - "title": "Pikatoiminnot", - "content": "Radioluettelosta voit: . | Napauttaa radiota avataksesi sen tietosivun | Pitkä painallus pikatoimintoja varten: . | Merkitse tai poista suosikki | Mykistä tai poista mykistys ilmoituksista | Lähetä yksityisviesti | Reitinselvitys | Ohita tai poista ohitus | Poista laite | . | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#pikatoiminnot", - - "relUrl": "/fi-rFI/user/nodes.html#pikatoiminnot" - },"3834": { - "doc": "Laitteet", - "title": "Suodatus ja lajittelu", - "content": "Tekstihaku . Kirjoita hakukenttään suodattaaksesi radioita nimen tai lyhyen nimen perusteella. Suodatus päivittyy reaaliajassa kirjoittaessasi. Suodatusvalinnat . | Suodatus | Kuvaus | . | Vain verkossa olevat | Näytä vain radiot, joista on kuultu viimeisten 2 tunnin aikana | . | Vain suorat | Näytä vain radiot, joihin on suora yhteys (ei välitetty yhteys) | . | Näytä tuntemattomat | Näytä radiot, jotka eivät ole vielä lähettäneet käyttäjätietoja | . | Ohita infrastruktuurilaitteet | Piilota infrastruktuuriroolit (Router, Router Late, Client Base) | . | Rajaa MQTT pois | Piilottaa radiot, joista on kuultu vain MQTT-internetsillan kautta | . | Näytä vain huomioimattomat radiot | Näytä radiot, jotka olet aiemmin ohittanut tai mykistänyt | . Lajitteluvaihtoehdot . | Lajittelu | Kuvaus | . | Viimeksi kuultu (oletus) | Näytä viimeksi kuullut radiot ensin | . | Aakkosjärjestys | 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 | . | MQTT:n kautta | Ryhmitelty MQTT:n kautta kuultuihin ja radiolla kuultuihin | . | Suosikkien kautta | Suosikkiradiot ensin | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#suodatus-ja-lajittelu", - - "relUrl": "/fi-rFI/user/nodes.html#suodatus-ja-lajittelu" - },"3835": { - "doc": "Laitteet", - "title": "Radiot hyppymäärän mukaan", - "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). Suodata kaavio Viimeksi kuultu -ajanjakson mukaan — Kaikki ajat, 1 tunti, 8 tuntia tai 24 tuntia — nähdäksesi, miltä mesh-verkko näyttää juuri nyt verrattuna pidempään ajanjaksoon. Tämä on nopea tapa arvioida, kuinka laaja ja kuormittunut paikallinen mesh-verkkosi on. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#radiot-hyppym%C3%A4%C3%A4r%C3%A4n-mukaan", - - "relUrl": "/fi-rFI/user/nodes.html#radiot-hyppymäärän-mukaan" - },"3836": { - "doc": "Laitteet", - "title": "Radion tiedot", - "content": "Radion napauttaminen avaa tietonäkymän, jossa on kattavat tiedot. Katso Radion mittarit saadaksesi täydelliset tiedot mittareista ja telemetriasta. Tietonäyttö sisältää laitetiedot, sijainnin ja toimintopainikkeet: . 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 | | . Laite-linkit (“Haluan sellaisen”) . 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. Kaikkien linkkien selattava hakemisto löytyy myös kohdasta Asetukset → Ohje ja dokumentaatio → Laitelinkit. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#radion-tiedot", - - "relUrl": "/fi-rFI/user/nodes.html#radion-tiedot" - },"3837": { - "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 | Haku — reitinselvitys- ja naapuritiedot verkon topologian tutkimiseen | 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" - },"3838": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html", - - "relUrl": "/gl-rES/user/nodes.html" - },"3839": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Descrición | . | Cliente | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#node-list", - - "relUrl": "/gl-rES/user/nodes.html#node-list" - },"3840": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#quick-actions", - - "relUrl": "/gl-rES/user/nodes.html#quick-actions" - },"3841": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descrición | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#filtering--sorting", - - "relUrl": "/gl-rES/user/nodes.html#filtering--sorting" - },"3842": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#nodes-per-hop", - - "relUrl": "/gl-rES/user/nodes.html#nodes-per-hop" - },"3843": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Última escoita | | . | Distancia | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#node-detail", - - "relUrl": "/gl-rES/user/nodes.html#node-detail" - },"3844": { - "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 | 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" - },"3845": { - "doc": "Вузли", - "title": "Вузли", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html", - - "relUrl": "/uk-rUA/user/nodes.html" - },"3846": { - "doc": "Вузли", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Роль | Опис | . | Клієнт | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#node-list", - - "relUrl": "/uk-rUA/user/nodes.html#node-list" - },"3847": { - "doc": "Вузли", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#quick-actions", - - "relUrl": "/uk-rUA/user/nodes.html#quick-actions" - },"3848": { - "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 . | Фільтри | Опис | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Опис | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Стрибків | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#filtering--sorting", - - "relUrl": "/uk-rUA/user/nodes.html#filtering--sorting" - },"3849": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#nodes-per-hop", - - "relUrl": "/uk-rUA/user/nodes.html#nodes-per-hop" - },"3850": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Рівень заряду батареї | | . | Hop count | | . | Востаннє в мережі | | . | Відстань | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#node-detail", - - "relUrl": "/uk-rUA/user/nodes.html#node-detail" - },"3851": { - "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 | 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" - },"3852": { "doc": "Knoten", "title": "Knoten", "content": "The Nodes screen displays all devices visible on your mesh network. ", "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html", "relUrl": "/de-rDE/user/nodes.html" - },"3853": { + },"3762": { "doc": "Knoten", "title": "Node List", "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Abzeichen | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rolle | Beschreibung | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client - 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — 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 devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Symbol | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#node-list", "relUrl": "/de-rDE/user/nodes.html#node-list" - },"3854": { + },"3763": { "doc": "Knoten", "title": "Quick Actions", "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Knoten entfernen | . | . ", "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#quick-actions", "relUrl": "/de-rDE/user/nodes.html#quick-actions" - },"3855": { + },"3764": { "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sortieren | Beschreibung | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#filtering--sorting", "relUrl": "/de-rDE/user/nodes.html#filtering--sorting" - },"3856": { + },"3765": { "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#nodes-per-hop", "relUrl": "/de-rDE/user/nodes.html#nodes-per-hop" - },"3857": { + },"3766": { "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Bildschirmfoto | . | Signal quality | | . | Akkustand | | . | Hop count | | . | Zuletzt gehört | | . | Distanz | | . 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 under Settings → Help & Documentation → Device Links. ", "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#node-detail", "relUrl": "/de-rDE/user/nodes.html#node-detail" - },"3858": { + },"3767": { "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 | 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" - },"3859": { + },"3768": { "doc": "Nodes", "title": "Nodes", "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html", + "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html", - "relUrl": "/hr-rHR/user/nodes.html" - },"3860": { + "relUrl": "/ca-rES/user/nodes.html" + },"3769": { "doc": "Nodes", "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Opis | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#node-list", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Descripció | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#node-list", - "relUrl": "/hr-rHR/user/nodes.html#node-list" - },"3861": { + "relUrl": "/ca-rES/user/nodes.html#node-list" + },"3770": { "doc": "Nodes", "title": "Quick Actions", "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#quick-actions", + "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#quick-actions", - "relUrl": "/hr-rHR/user/nodes.html#quick-actions" - },"3862": { + "relUrl": "/ca-rES/user/nodes.html#quick-actions" + },"3771": { "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Opis | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#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ó | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descripció | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#filtering--sorting", - "relUrl": "/hr-rHR/user/nodes.html#filtering--sorting" - },"3863": { + "relUrl": "/ca-rES/user/nodes.html#filtering--sorting" + },"3772": { "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#nodes-per-hop", + "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#nodes-per-hop", - "relUrl": "/hr-rHR/user/nodes.html#nodes-per-hop" - },"3864": { + "relUrl": "/ca-rES/user/nodes.html#nodes-per-hop" + },"3773": { "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Posljednje čuo | | . | Udaljenost | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#node-detail", + "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Última notícia | | . | Distància | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#node-detail", - "relUrl": "/hr-rHR/user/nodes.html#node-detail" - },"3865": { + "relUrl": "/ca-rES/user/nodes.html#node-detail" + },"3774": { "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 | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#related-topics", - "relUrl": "/hr-rHR/user/nodes.html#related-topics" - },"3866": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html", - - "relUrl": "/lt-rLT/user/nodes.html" - },"3867": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Aprašymas | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#node-list", - - "relUrl": "/lt-rLT/user/nodes.html#node-list" - },"3868": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#quick-actions", - - "relUrl": "/lt-rLT/user/nodes.html#quick-actions" - },"3869": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Aprašymas | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#filtering--sorting", - - "relUrl": "/lt-rLT/user/nodes.html#filtering--sorting" - },"3870": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#nodes-per-hop", - - "relUrl": "/lt-rLT/user/nodes.html#nodes-per-hop" - },"3871": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Seniausiai girdėtas | | . | Atstumas | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#node-detail", - - "relUrl": "/lt-rLT/user/nodes.html#node-detail" - },"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 | 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" - },"3873": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/en/user/nodes.html", - - "relUrl": "/en/user/nodes.html" - },"3874": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Description | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/en/user/nodes.html#node-list", - - "relUrl": "/en/user/nodes.html#node-list" - },"3875": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/en/user/nodes.html#quick-actions", - - "relUrl": "/en/user/nodes.html#quick-actions" - },"3876": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Description | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/en/user/nodes.html#filtering--sorting", - - "relUrl": "/en/user/nodes.html#filtering--sorting" - },"3877": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/en/user/nodes.html#nodes-per-hop", - - "relUrl": "/en/user/nodes.html#nodes-per-hop" - },"3878": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | Distance | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/en/user/nodes.html#node-detail", - - "relUrl": "/en/user/nodes.html#node-detail" - },"3879": { - "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 | 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" - },"3880": { - "doc": "Csomópontok", - "title": "Csomópontok", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html", - - "relUrl": "/hu-rHU/user/nodes.html" - },"3881": { - "doc": "Csomópontok", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Szerepkör | Leírás | . | Kliens | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#node-list", - - "relUrl": "/hu-rHU/user/nodes.html#node-list" - },"3882": { - "doc": "Csomópontok", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#quick-actions", - - "relUrl": "/hu-rHU/user/nodes.html#quick-actions" - },"3883": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Leírás | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#filtering--sorting", - - "relUrl": "/hu-rHU/user/nodes.html#filtering--sorting" - },"3884": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#nodes-per-hop", - - "relUrl": "/hu-rHU/user/nodes.html#nodes-per-hop" - },"3885": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Utoljára hallott | | . | Távolság | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#node-detail", - - "relUrl": "/hu-rHU/user/nodes.html#node-detail" - },"3886": { - "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 | 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" - },"3887": { - "doc": "Възли", - "title": "Възли", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html", - - "relUrl": "/bg-rBG/user/nodes.html" - },"3888": { - "doc": "Възли", - "title": "Списък с възли", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Роля | Описание | . | Клиент | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Скрит клиент | Like Client Mute, plus hides from node list | . | Рутер | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Тракер | Optimized for position reporting at regular intervals | . | Сензор | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#%D1%81%D0%BF%D0%B8%D1%81%D1%8A%D0%BA-%D1%81-%D0%B2%D1%8A%D0%B7%D0%BB%D0%B8", - - "relUrl": "/bg-rBG/user/nodes.html#списък-с-възли" - },"3889": { - "doc": "Възли", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Премахване на възела | . | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#quick-actions", - - "relUrl": "/bg-rBG/user/nodes.html#quick-actions" - },"3890": { - "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 . | Филтър | Описание | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Описание | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#filtering--sorting", - - "relUrl": "/bg-rBG/user/nodes.html#filtering--sorting" - },"3891": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#nodes-per-hop", - - "relUrl": "/bg-rBG/user/nodes.html#nodes-per-hop" - },"3892": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Екранна снимка | . | Signal quality | | . | Ниво на батерията | | . | Hop count | | . | Последно чут | | . | Разстояние | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#node-detail", - - "relUrl": "/bg-rBG/user/nodes.html#node-detail" - },"3893": { - "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 | 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" - },"3894": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html", - - "relUrl": "/sl-rSI/user/nodes.html" - },"3895": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Opis | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#node-list", - - "relUrl": "/sl-rSI/user/nodes.html#node-list" - },"3896": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#quick-actions", - - "relUrl": "/sl-rSI/user/nodes.html#quick-actions" - },"3897": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Opis | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#filtering--sorting", - - "relUrl": "/sl-rSI/user/nodes.html#filtering--sorting" - },"3898": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#nodes-per-hop", - - "relUrl": "/sl-rSI/user/nodes.html#nodes-per-hop" - },"3899": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Nazadnje slišano | | . | Razdalja | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#node-detail", - - "relUrl": "/sl-rSI/user/nodes.html#node-detail" - },"3900": { - "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 | 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" - },"3901": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html", - - "relUrl": "/pt-rPT/user/nodes.html" - },"3902": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Papel | Descrição | . | Cliente | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#node-list", - - "relUrl": "/pt-rPT/user/nodes.html#node-list" - },"3903": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#quick-actions", - - "relUrl": "/pt-rPT/user/nodes.html#quick-actions" - },"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 . | Filtrar | Descrição | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descrição | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#filtering--sorting", - - "relUrl": "/pt-rPT/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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#nodes-per-hop", - - "relUrl": "/pt-rPT/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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Último recebido | | . | Distância | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#node-detail", - - "relUrl": "/pt-rPT/user/nodes.html#node-detail" - },"3907": { - "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 | 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" - },"3908": { + "relUrl": "/ca-rES/user/nodes.html#related-topics" + },"3775": { "doc": "Nodes", "title": "Nodes", "content": "The Nodes screen displays all devices visible on your mesh network. ", "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html", "relUrl": "/be-rBY/user/nodes.html" - },"3909": { + },"3776": { "doc": "Nodes", "title": "Node List", "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Апісанне | . | CLIENT | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | CLIENT MUTE | Receives but doesn’t retransmit | . | CLIENT HIDDEN | Like Client Mute, plus hides from node list | . | ROUTER | Prioritizes message forwarding; stays awake to relay | . | ROUTER LATE | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | TRACKER | Optimized for position reporting at regular intervals | . | SENSOR | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK TRACKER | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#node-list", "relUrl": "/be-rBY/user/nodes.html#node-list" - },"3910": { + },"3777": { "doc": "Nodes", "title": "Quick Actions", "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#quick-actions", "relUrl": "/be-rBY/user/nodes.html#quick-actions" - },"3911": { + },"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 . | Фільтраваць | Апісанне | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Апісанне | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#filtering--sorting", "relUrl": "/be-rBY/user/nodes.html#filtering--sorting" - },"3912": { + },"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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#nodes-per-hop", "relUrl": "/be-rBY/user/nodes.html#nodes-per-hop" - },"3913": { + },"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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Апошні раз пачуты | | . | Адлегласць | | . 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 under Settings → Help & Documentation → Device Links. ", "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#node-detail", "relUrl": "/be-rBY/user/nodes.html#node-detail" - },"3914": { + },"3781": { "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 | 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" - },"3915": { + },"3782": { + "doc": "Вузли", + "title": "Вузли", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html", + + "relUrl": "/uk-rUA/user/nodes.html" + },"3783": { + "doc": "Вузли", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Роль | Опис | . | Клієнт | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#node-list", + + "relUrl": "/uk-rUA/user/nodes.html#node-list" + },"3784": { + "doc": "Вузли", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#quick-actions", + + "relUrl": "/uk-rUA/user/nodes.html#quick-actions" + },"3785": { + "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 . | Фільтри | Опис | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Опис | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Стрибків | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#filtering--sorting", + + "relUrl": "/uk-rUA/user/nodes.html#filtering--sorting" + },"3786": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#nodes-per-hop", + + "relUrl": "/uk-rUA/user/nodes.html#nodes-per-hop" + },"3787": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Рівень заряду батареї | | . | Hop count | | . | Востаннє в мережі | | . | Відстань | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#node-detail", + + "relUrl": "/uk-rUA/user/nodes.html#node-detail" + },"3788": { + "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 | 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" + },"3789": { + "doc": "节点", + "title": "节点", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html", + + "relUrl": "/zh-rCN/user/nodes.html" + },"3790": { + "doc": "节点", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | 角色 | 说明 | . | 客户端 | Standard end-user device | . | 客户群 | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | 图标 | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#node-list", + + "relUrl": "/zh-rCN/user/nodes.html#node-list" + },"3791": { + "doc": "节点", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | 删除节点 | . | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#quick-actions", + + "relUrl": "/zh-rCN/user/nodes.html#quick-actions" + },"3792": { + "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 . | 搜索节点 | 说明 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | 说明 | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#filtering--sorting", + + "relUrl": "/zh-rCN/user/nodes.html#filtering--sorting" + },"3793": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#nodes-per-hop", + + "relUrl": "/zh-rCN/user/nodes.html#nodes-per-hop" + },"3794": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | 电池电量 | | . | Hop count | | . | 最后听到 | | . | 距离 | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#node-detail", + + "relUrl": "/zh-rCN/user/nodes.html#node-detail" + },"3795": { + "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 | 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" + },"3796": { + "doc": "Възли", + "title": "Възли", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html", + + "relUrl": "/bg-rBG/user/nodes.html" + },"3797": { + "doc": "Възли", + "title": "Списък с възли", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Роля | Описание | . | Клиент | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Скрит клиент | Like Client Mute, plus hides from node list | . | Рутер | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Тракер | Optimized for position reporting at regular intervals | . | Сензор | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#%D1%81%D0%BF%D0%B8%D1%81%D1%8A%D0%BA-%D1%81-%D0%B2%D1%8A%D0%B7%D0%BB%D0%B8", + + "relUrl": "/bg-rBG/user/nodes.html#списък-с-възли" + },"3798": { + "doc": "Възли", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Премахване на възела | . | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#quick-actions", + + "relUrl": "/bg-rBG/user/nodes.html#quick-actions" + },"3799": { + "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 . | Филтър | Описание | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Описание | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#filtering--sorting", + + "relUrl": "/bg-rBG/user/nodes.html#filtering--sorting" + },"3800": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#nodes-per-hop", + + "relUrl": "/bg-rBG/user/nodes.html#nodes-per-hop" + },"3801": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Екранна снимка | . | Signal quality | | . | Ниво на батерията | | . | Hop count | | . | Последно чут | | . | Разстояние | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#node-detail", + + "relUrl": "/bg-rBG/user/nodes.html#node-detail" + },"3802": { + "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 | 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" + },"3803": { + "doc": "節點", + "title": "節點", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html", + + "relUrl": "/zh-rTW/user/nodes.html" + },"3804": { + "doc": "節點", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | 角色 | 描述說明 | . | 用戶端 | Standard end-user device | . | 客戶端基礎模式 | 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 & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#node-list", + + "relUrl": "/zh-rTW/user/nodes.html#node-list" + },"3805": { + "doc": "節點", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | 移除節點 | . | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#quick-actions", + + "relUrl": "/zh-rTW/user/nodes.html#quick-actions" + },"3806": { + "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 . | 過濾器 | 描述說明 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | 描述說明 | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#filtering--sorting", + + "relUrl": "/zh-rTW/user/nodes.html#filtering--sorting" + },"3807": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#nodes-per-hop", + + "relUrl": "/zh-rTW/user/nodes.html#nodes-per-hop" + },"3808": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | 螢幕截圖 | . | Signal quality | | . | 電池電量 | | . | Hop count | | . | 最近一次收到排序 | | . | 距離 | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#node-detail", + + "relUrl": "/zh-rTW/user/nodes.html#node-detail" + },"3809": { + "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 | 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" + },"3810": { + "doc": "Чворови", + "title": "Чворови", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "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 radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Улога | Опис | . | Клијент | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Клијент мутиран | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Иконица | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "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 | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#quick-actions", + + "relUrl": "/sr-rLatn/user/nodes.html#quick-actions" + },"3813": { + "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 | Опис | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Опис | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#filtering--sorting", + + "relUrl": "/sr-rLatn/user/nodes.html#filtering--sorting" + },"3814": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#nodes-per-hop", + + "relUrl": "/sr-rLatn/user/nodes.html#nodes-per-hop" + },"3815": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Poslednji put viđeno | | . | Udaljenost | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#node-detail", + + "relUrl": "/sr-rLatn/user/nodes.html#node-detail" + },"3816": { + "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 | 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" + },"3817": { + "doc": "Uzly", + "title": "Uzly", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html", + + "relUrl": "/cs-rCZ/user/nodes.html" + },"3818": { + "doc": "Uzly", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Popis | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Senzor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#node-list", + + "relUrl": "/cs-rCZ/user/nodes.html#node-list" + },"3819": { + "doc": "Uzly", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#quick-actions", + + "relUrl": "/cs-rCZ/user/nodes.html#quick-actions" + },"3820": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Popis | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#filtering--sorting", + + "relUrl": "/cs-rCZ/user/nodes.html#filtering--sorting" + },"3821": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#nodes-per-hop", + + "relUrl": "/cs-rCZ/user/nodes.html#nodes-per-hop" + },"3822": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Naposledy slyšen | | . | Vzdálenost | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#node-detail", + + "relUrl": "/cs-rCZ/user/nodes.html#node-detail" + },"3823": { + "doc": "Uzly", + "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 | 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#related-topics", + + "relUrl": "/cs-rCZ/user/nodes.html#related-topics" + },"3824": { + "doc": "Nodes", + "title": "Nodes", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/en/user/nodes.html", + + "relUrl": "/en/user/nodes.html" + },"3825": { + "doc": "Nodes", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Description | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/en/user/nodes.html#node-list", + + "relUrl": "/en/user/nodes.html#node-list" + },"3826": { + "doc": "Nodes", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/en/user/nodes.html#quick-actions", + + "relUrl": "/en/user/nodes.html#quick-actions" + },"3827": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Description | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/en/user/nodes.html#filtering--sorting", + + "relUrl": "/en/user/nodes.html#filtering--sorting" + },"3828": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/en/user/nodes.html#nodes-per-hop", + + "relUrl": "/en/user/nodes.html#nodes-per-hop" + },"3829": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | Distance | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/en/user/nodes.html#node-detail", + + "relUrl": "/en/user/nodes.html#node-detail" + },"3830": { + "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 | 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" + },"3831": { + "doc": "Nodes", + "title": "Nodes", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html", + + "relUrl": "/sl-rSI/user/nodes.html" + },"3832": { + "doc": "Nodes", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Opis | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#node-list", + + "relUrl": "/sl-rSI/user/nodes.html#node-list" + },"3833": { + "doc": "Nodes", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#quick-actions", + + "relUrl": "/sl-rSI/user/nodes.html#quick-actions" + },"3834": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Opis | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#filtering--sorting", + + "relUrl": "/sl-rSI/user/nodes.html#filtering--sorting" + },"3835": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#nodes-per-hop", + + "relUrl": "/sl-rSI/user/nodes.html#nodes-per-hop" + },"3836": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Nazadnje slišano | | . | Razdalja | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#node-detail", + + "relUrl": "/sl-rSI/user/nodes.html#node-detail" + },"3837": { + "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 | 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" + },"3838": { + "doc": "Nodi", + "title": "Nodi", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html", + + "relUrl": "/it-rIT/user/nodes.html" + },"3839": { + "doc": "Nodi", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Ruolo | Descrizione | . | Client | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#node-list", + + "relUrl": "/it-rIT/user/nodes.html#node-list" + },"3840": { + "doc": "Nodi", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Rimuovi Nodo | . | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#quick-actions", + + "relUrl": "/it-rIT/user/nodes.html#quick-actions" + },"3841": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descrizione | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#filtering--sorting", + + "relUrl": "/it-rIT/user/nodes.html#filtering--sorting" + },"3842": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#nodes-per-hop", + + "relUrl": "/it-rIT/user/nodes.html#nodes-per-hop" + },"3843": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Livello batteria | | . | Hop count | | . | Ricevuto più di recente | | . | Distanza | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#node-detail", + + "relUrl": "/it-rIT/user/nodes.html#node-detail" + },"3844": { + "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 | 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" + },"3845": { "doc": "Nós", "title": "Nós", "content": "The Nodes screen displays all devices visible on your mesh network. ", "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html", "relUrl": "/pt-rBR/user/nodes.html" - },"3916": { + },"3846": { "doc": "Nós", "title": "Node List", "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Função | Descrição | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#node-list", "relUrl": "/pt-rBR/user/nodes.html#node-list" - },"3917": { + },"3847": { "doc": "Nós", "title": "Quick Actions", "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#quick-actions", "relUrl": "/pt-rBR/user/nodes.html#quick-actions" - },"3918": { + },"3848": { "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descrição | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#filtering--sorting", "relUrl": "/pt-rBR/user/nodes.html#filtering--sorting" - },"3919": { + },"3849": { "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#nodes-per-hop", "relUrl": "/pt-rBR/user/nodes.html#nodes-per-hop" - },"3920": { + },"3850": { "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Visto pela última vez | | . | Distância | | . 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 under Settings → Help & Documentation → Device Links. ", "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#node-detail", "relUrl": "/pt-rBR/user/nodes.html#node-detail" - },"3921": { + },"3851": { "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 | 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" - },"3922": { + },"3852": { "doc": "Nodes", "title": "Nodes", "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html", + "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html", - "relUrl": "/el-rGR/user/nodes.html" - },"3923": { + "relUrl": "/is-rIS/user/nodes.html" + },"3853": { "doc": "Nodes", "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Περιγραφή | . | Client | Standard end-user device | . | Πελάτης Βάση | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#node-list", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Lýsing | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#node-list", - "relUrl": "/el-rGR/user/nodes.html#node-list" - },"3924": { + "relUrl": "/is-rIS/user/nodes.html#node-list" + },"3854": { "doc": "Nodes", "title": "Quick Actions", "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#quick-actions", + "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#quick-actions", - "relUrl": "/el-rGR/user/nodes.html#quick-actions" - },"3925": { + "relUrl": "/is-rIS/user/nodes.html#quick-actions" + },"3855": { "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 . | Φίλτρο | Περιγραφή | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Περιγραφή | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Lýsing | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#filtering--sorting", - "relUrl": "/el-rGR/user/nodes.html#filtering--sorting" - },"3926": { + "relUrl": "/is-rIS/user/nodes.html#filtering--sorting" + },"3856": { "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#nodes-per-hop", + "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#nodes-per-hop", - "relUrl": "/el-rGR/user/nodes.html#nodes-per-hop" - },"3927": { + "relUrl": "/is-rIS/user/nodes.html#nodes-per-hop" + },"3857": { "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | Απόσταση | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#node-detail", + "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | Distance | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#node-detail", - "relUrl": "/el-rGR/user/nodes.html#node-detail" - },"3928": { + "relUrl": "/is-rIS/user/nodes.html#node-detail" + },"3858": { "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 | 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", + "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#related-topics", - "relUrl": "/el-rGR/user/nodes.html#related-topics" - },"3929": { - "doc": "Nodos", - "title": "Nodos", + "relUrl": "/is-rIS/user/nodes.html#related-topics" + },"3859": { + "doc": "Nœuds", + "title": "Nœuds", "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/es-rES/user/nodes.html", + "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html", - "relUrl": "/es-rES/user/nodes.html" - },"3930": { - "doc": "Nodos", + "relUrl": "/fr-rFR/user/nodes.html" + },"3860": { + "doc": "Nœuds", "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rol | Descripción | . | Cliente | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#node-list", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rôle | Description | . | Client | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#node-list", - "relUrl": "/es-rES/user/nodes.html#node-list" - },"3931": { - "doc": "Nodos", + "relUrl": "/fr-rFR/user/nodes.html#node-list" + },"3861": { + "doc": "Nœuds", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Supprimer le nœud | . | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#quick-actions", + + "relUrl": "/fr-rFR/user/nodes.html#quick-actions" + },"3862": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Description | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#filtering--sorting", + + "relUrl": "/fr-rFR/user/nodes.html#filtering--sorting" + },"3863": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#nodes-per-hop", + + "relUrl": "/fr-rFR/user/nodes.html#nodes-per-hop" + },"3864": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Niveau de batterie | | . | Hop count | | . | Dernière écoute | | . | Distance | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#node-detail", + + "relUrl": "/fr-rFR/user/nodes.html#node-detail" + },"3865": { + "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 | 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" + },"3866": { + "doc": "Чворови", + "title": "Чворови", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/srp/user/nodes.html", + + "relUrl": "/srp/user/nodes.html" + },"3867": { + "doc": "Чворови", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Улога | Опис | . | Клијент | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Клијент мутиран | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Иконица | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/srp/user/nodes.html#node-list", + + "relUrl": "/srp/user/nodes.html#node-list" + },"3868": { + "doc": "Чворови", "title": "Quick Actions", "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#quick-actions", + "url": "/Meshtastic-Android/main/srp/user/nodes.html#quick-actions", - "relUrl": "/es-rES/user/nodes.html#quick-actions" - },"3932": { - "doc": "Nodos", + "relUrl": "/srp/user/nodes.html#quick-actions" + },"3869": { + "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 . | Filtro | Descripción | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descripción | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#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 . | Филтер | Опис | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Опис | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/srp/user/nodes.html#filtering--sorting", - "relUrl": "/es-rES/user/nodes.html#filtering--sorting" - },"3933": { - "doc": "Nodos", + "relUrl": "/srp/user/nodes.html#filtering--sorting" + },"3870": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#nodes-per-hop", + "url": "/Meshtastic-Android/main/srp/user/nodes.html#nodes-per-hop", - "relUrl": "/es-rES/user/nodes.html#nodes-per-hop" - },"3934": { - "doc": "Nodos", + "relUrl": "/srp/user/nodes.html#nodes-per-hop" + },"3871": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Última escucha | | . | Distancia | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#node-detail", + "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Последње откривање | | . | Раздаљина | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/srp/user/nodes.html#node-detail", - "relUrl": "/es-rES/user/nodes.html#node-detail" - },"3935": { - "doc": "Nodos", + "relUrl": "/srp/user/nodes.html#node-detail" + },"3872": { + "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 | 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", + "url": "/Meshtastic-Android/main/srp/user/nodes.html#related-topics", - "relUrl": "/es-rES/user/nodes.html#related-topics" - },"3936": { - "doc": "Nodelar", - "title": "Nodelar", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html", - - "relUrl": "/tr-rTR/user/nodes.html" - },"3937": { - "doc": "Nodelar", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rol | Açıklaması | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#node-list", - - "relUrl": "/tr-rTR/user/nodes.html#node-list" - },"3938": { - "doc": "Nodelar", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Node sil | . | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#quick-actions", - - "relUrl": "/tr-rTR/user/nodes.html#quick-actions" - },"3939": { - "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ı | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Açıklaması | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#filtering--sorting", - - "relUrl": "/tr-rTR/user/nodes.html#filtering--sorting" - },"3940": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#nodes-per-hop", - - "relUrl": "/tr-rTR/user/nodes.html#nodes-per-hop" - },"3941": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Son duyulma | | . | Mesafe | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#node-detail", - - "relUrl": "/tr-rTR/user/nodes.html#node-detail" - },"3942": { - "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 | 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" - },"3943": { + "relUrl": "/srp/user/nodes.html#related-topics" + },"3873": { "doc": "Nodes", "title": "Nodes", "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html", + "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html", - "relUrl": "/no-rNO/user/nodes.html" - },"3944": { + "relUrl": "/sk-rSK/user/nodes.html" + },"3874": { "doc": "Nodes", "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Beskrivelse | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#node-list", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rola | Popis | . | Klient | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#node-list", - "relUrl": "/no-rNO/user/nodes.html#node-list" - },"3945": { + "relUrl": "/sk-rSK/user/nodes.html#node-list" + },"3875": { "doc": "Nodes", "title": "Quick Actions", "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#quick-actions", + "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#quick-actions", - "relUrl": "/no-rNO/user/nodes.html#quick-actions" - },"3946": { + "relUrl": "/sk-rSK/user/nodes.html#quick-actions" + },"3876": { "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Beskrivelse | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Popis | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#filtering--sorting", - "relUrl": "/no-rNO/user/nodes.html#filtering--sorting" - },"3947": { + "relUrl": "/sk-rSK/user/nodes.html#filtering--sorting" + },"3877": { "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#nodes-per-hop", + "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#nodes-per-hop", - "relUrl": "/no-rNO/user/nodes.html#nodes-per-hop" - },"3948": { + "relUrl": "/sk-rSK/user/nodes.html#nodes-per-hop" + },"3878": { "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Sist hørt | | . | Distanse | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#node-detail", + "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Posledný príjem | | . | Vzdialenosť | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#node-detail", - "relUrl": "/no-rNO/user/nodes.html#node-detail" - },"3949": { + "relUrl": "/sk-rSK/user/nodes.html#node-detail" + },"3879": { "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 | 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", + "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#related-topics", - "relUrl": "/no-rNO/user/nodes.html#related-topics" - },"3950": { + "relUrl": "/sk-rSK/user/nodes.html#related-topics" + },"3880": { + "doc": "Laitteet", + "title": "Laitteet", + "content": "Radiot-näyttö näyttää kaikki verkossasi näkyvät laitteet. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html", + + "relUrl": "/fi-rFI/user/nodes.html" + },"3881": { + "doc": "Laitteet", + "title": "Radiolista", + "content": "Radioluettelo näyttää kaikki radiot, joista radiosi on vastaanottanut tietoja, mukaan lukien: . | Radion nimi — käyttäjän määrittämä pitkä nimi | Lyhyt nimi — 4-merkkinen tunniste | Signaalin laatu — viimeksi vastaanotetun signaalin voimakkuus | 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ä) | . Radion tilailmaisimet . | Tunniste | Tarkoitus | . | 🟢 Verkossa | Radio kuultu viimeisen 2 tunnin aikana | . | Ei verkkossa | Radiosta ei ole kuultu yli 2 tuntiin | . | ⭐ Suosikki | Käyttäjän suosikiksi merkitsemä radio | . Radio katsotaan verkossa olevaksi, jos siitä on kuultu viimeisten 2 tunnin aikana. Muussa tapauksessa se katsotaan poissa verkosta olevaksi — erillistä “poissa”-tilaa ei ole. Radion roolit . Radioille voidaan määrittää erilaisia rooleja, jotka vaikuttavat niiden toimintaan verkossa: . | Rooli | Kuvaus | . | Client | Tavallinen loppukäyttäjän laite | . | 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 | . | Kadonnut ja löydetty | Jatkuva sijaintimajakka löytämistä varten | . Roolin valitseminen . 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. Älä käytä Router-roolia akkukäyttöisissä käsilaitteissa. | 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. Hyödyllinen vain valvontaan käytettäville laitteille tai ruuhkien vähentämiseen tiheästi rakennetuilla alueilla. | Tracker — Valvomaton laite, jonka ainoa tarkoitus on lähettää GPS-sijaintiaan (esim. ajoneuvo, lemmikki tai omaisuus). Nukkuu lähetysten välillä akun säästämiseksi. | Sensor — Valvomaton laite, joka raportoi ympäristötelemetriaa (lämpötila, kosteus, ilmanlaatu). 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 -rooleja heikentää verkon toimintavarmuutta, kun taas liian suuri määrä Router-rooleja tiheässä verkossa voi aiheuttaa ruuhkaa. Hyvä nyrkkisääntö on yksi Router jokaista 5–10 Client-roolia kohden alueellasi. Salausilmaisimet . Radiot näyttävät nimensä vieressä salauksen tilaa kuvaavat kuvakkeet: . | Kuvake | Merkitys | . | 🔒 Lukittu | Yhteys käyttää PKI:tä (julkisen avaimen infrastruktuuria) — päästä päähän salattu ja varmennetulla identiteetillä suojattu. | . | 🔓 Lukitsematon | Yhteys käyttää PKI:tä (julkisen avaimen infrastruktuuria) — päästä päähän salattu ja varmennetulla identiteetillä suojattu. | . | ⚠️ Ei täsmää | Julkinen avain ei täsmää — radion avain on muuttunut viime näkemän jälkeen (tutki ennen luottamista). | . 💡 Vinkki: PKI-salaus (laiteohjelmisto 2.5+) tarjoaa vahvemman suojauksen kuin kanavan PSK-avain, koska jokaisella radiolla on oma yksilöllinen avainparinsa. Jos näet avaimen täsmäämättömyysvaroituksen, radio on voitu nollata tai sen tietoturva on voinut vaarantua. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#radiolista", + + "relUrl": "/fi-rFI/user/nodes.html#radiolista" + },"3882": { + "doc": "Laitteet", + "title": "Pikatoiminnot", + "content": "Radioluettelosta voit: . | Napauttaa radiota avataksesi sen tietosivun | Pitkä painallus pikatoimintoja varten: . | Merkitse tai poista suosikki | Mykistä tai poista mykistys ilmoituksista | Lähetä yksityisviesti | Reitinselvitys | Ohita tai poista ohitus | Poista laite | . | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#pikatoiminnot", + + "relUrl": "/fi-rFI/user/nodes.html#pikatoiminnot" + },"3883": { + "doc": "Laitteet", + "title": "Suodatus ja lajittelu", + "content": "Tekstihaku . Kirjoita hakukenttään suodattaaksesi radioita nimen tai lyhyen nimen perusteella. Suodatus päivittyy reaaliajassa kirjoittaessasi. Suodatusvalinnat . | Suodatus | Kuvaus | . | Vain verkossa olevat | Näytä vain radiot, joista on kuultu viimeisten 2 tunnin aikana | . | Vain suorat | Näytä vain radiot, joihin on suora yhteys (ei välitetty yhteys) | . | Näytä tuntemattomat | Näytä radiot, jotka eivät ole vielä lähettäneet käyttäjätietoja | . | Ohita infrastruktuurilaitteet | Piilota infrastruktuuriroolit (Router, Router Late, Client Base) | . | Rajaa MQTT pois | Piilottaa radiot, joista on kuultu vain MQTT-internetsillan kautta | . | Näytä vain huomioimattomat radiot | Näytä radiot, jotka olet aiemmin ohittanut tai mykistänyt | . Lajitteluvaihtoehdot . | Lajittelu | Kuvaus | . | Viimeksi kuultu (oletus) | Näytä viimeksi kuullut radiot ensin | . | Aakkosjärjestys | 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 | . | MQTT:n kautta | Ryhmitelty MQTT:n kautta kuultuihin ja radiolla kuultuihin | . | Suosikkien kautta | Suosikkiradiot ensin | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#suodatus-ja-lajittelu", + + "relUrl": "/fi-rFI/user/nodes.html#suodatus-ja-lajittelu" + },"3884": { + "doc": "Laitteet", + "title": "Radiot hyppymäärän mukaan", + "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). Suodata kaavio Viimeksi kuultu -ajanjakson mukaan — Kaikki ajat, 1 tunti, 8 tuntia tai 24 tuntia — nähdäksesi, miltä mesh-verkko näyttää juuri nyt verrattuna pidempään ajanjaksoon. Tämä on nopea tapa arvioida, kuinka laaja ja kuormittunut paikallinen mesh-verkkosi on. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#radiot-hyppym%C3%A4%C3%A4r%C3%A4n-mukaan", + + "relUrl": "/fi-rFI/user/nodes.html#radiot-hyppymäärän-mukaan" + },"3885": { + "doc": "Laitteet", + "title": "Radion tiedot", + "content": "Radion napauttaminen avaa tietonäkymän, jossa on kattavat tiedot. Katso Radion mittarit saadaksesi täydelliset tiedot mittareista ja telemetriasta. Tietonäyttö sisältää laitetiedot, sijainnin ja toimintopainikkeet: . 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 | | . Laite-linkit (“Haluan sellaisen”) . 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. Kaikkien linkkien selattava hakemisto löytyy myös kohdasta Asetukset → Ohje ja dokumentaatio → Laitelinkit. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#radion-tiedot", + + "relUrl": "/fi-rFI/user/nodes.html#radion-tiedot" + },"3886": { + "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 | Haku — reitinselvitys- ja naapuritiedot verkon topologian tutkimiseen | 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" + },"3887": { "doc": "Ноды", "title": "Ноды", "content": "Экран нод показывает все устройства, видимые в твоей mesh-сети. ", "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html", "relUrl": "/ru-rRU/user/nodes.html" - },"3951": { + },"3888": { "doc": "Ноды", "title": "Список узлов", "content": "Список нод показывает все ноды, которые услышало твоё радиоустройство, включая: . | Имя ноды — длинное имя, настроенное пользователем | Короткое имя — 4-символьный идентификатор | Качество сигнала — последний уровень принимаемого сигнала | Последнее услышанное — время с последнего общения | Расстояние — предполагаемое расстояние (если позиции общие) | Батарея — уровень заряда батареи удалённой ноды (если включена телеметрия) | . Индикаторы состояния ноды . | Значок | Значение | . | 🟢 Онлайн | Нода слышна за последние 2 часа | . | ⚪ Оффлайн | Нода не отвечала больше 2 часов | . | ⭐ Избранный | Нода отмечена пользователем как избранная | . Нода считается онлайн, если с ней связывались в последние 2 часа, и офлайн в противном случае — отдельного статуса «отошёл» нет. Роли ноды . У нод можно настраивать разные роли, которые влияют на их поведение в сети: . | Роль | Описание | . | Client | Стандартное пользовательское устройство | . | 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 & Found | Непрерывный маяк для поиска | . Выбор роли . Большинству пользователей стоит оставить роль Client по умолчанию. Рассмотри другую роль, когда: . | Router — У тебя есть узел в фиксированном, высоком месте с надежным источником питания (крыша, вершина холма). Router постоянно бодрствуют, чтобы пересылать сообщения для других, и они необходимы для расширения покрытия сети. Не используй Router на портативных устройствах с батареей. | Router Late — инфраструктурная нода, которая всегда пересылает пакеты только один раз, но только после того, как все другие режимы маршрутизации выполнили свои ходы. Обеспечивает дополнительное покрытие для локальных кластеров, не конкурируя с основными роутерами. | Client Base — обрабатывает трафик от/к вашим избранным нодам с приоритетом Router Late (обеспечивая этим сообщениям дополнительное ретранслирование), а всё остальное обрабатывает как обычный Client. | Client Mute — хочешь принимать трафик сети, но не участвовать в его ретрансляции. Полезно для устройств только для мониторинга или чтобы уменьшить нагрузку в густонаселённых местах. | Tracker — это устройство, которое работает само по себе и его единственная цель — передавать местоположение по GPS (например, автомобиль, питомец или имущество). Спит между передачами для экономии батареи. | Sensor — это автономное устройство, которое отслеживает показатели окружающей среды (температуру, влажность, качество воздуха). Похожий профиль мощности на Tracker. | TAK / TAK Tracker — нужно только если работать с системами ATAK/WinTAK. Смотри Интеграция TAK для подробностей. | . 💡 Совет: Сеть работает лучше, когда большинство нод Client или Router. Слишком много нод Mute снижает устойчивость сети; слишком много роутеров в плотной зоне может вызвать перегрузку. Хорошее практическое правило: один роутер на 5–10 клиентов в вашей зоне. Индикаторы шифрования . У нод рядом с именем отображаются значки статуса шифрования: . | Значок | Значение | . | 🔒 Заблокировано | Связь использует PKI (инфраструктуру публичных ключей) — сквозное шифрование с проверкой идентичности | . | 🔓 Разблокировано | Связь использует общий канал PSK — зашифровано, но личность не проверяется индивидуально | . | ⚠️ Несовпадение | Несовпадение открытого ключа — ключ ноды изменился с последнего раза (разберитесь, прежде чем доверять) | . 💡 Совет: Шифрование PKI (прошивка 2.5+) обеспечивает более надёжную защиту, чем общий PSK для канала, потому что у каждой ноды есть уникальная пара ключей. Если видишь предупреждение о несоответствии ключа, нода могла быть сброшена или скомпрометирована. ", "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#%D1%81%D0%BF%D0%B8%D1%81%D0%BE%D0%BA-%D1%83%D0%B7%D0%BB%D0%BE%D0%B2", "relUrl": "/ru-rRU/user/nodes.html#список-узлов" - },"3952": { + },"3889": { "doc": "Ноды", "title": "Быстрые действия", "content": "Из списка нод ты можешь: . | Нажмите на ноду, чтобы увидеть её страницу с деталями | Долгое нажатие для быстрых действий: . | Отметить/убрать из избранного | Отключить/включить уведомления | Отправить личное сообщение | Трассировка | Игнорировать/разблокировать | Удалить ноду | . | . ", "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#быстрые-действия" - },"3953": { + },"3890": { "doc": "Ноды", "title": "Фильтрация и сортировка", "content": "Поиск текста . Введи в поле поиска, чтобы отфильтровать ноды по имени или короткому имени. Фильтр обновляется в реальном времени по мере набора текста. Переключатели фильтра . | Фильтр | Описание | . | Только онлайн | Показывать только ноды, услышанные за последние 2 часа | . | Только прямые | Показывать только ноды с прямыми (без посредников) соединениями | . | Включить неизвестные | Показать ноды, которые еще не отправили информацию о пользователе | . | Исключить инфраструктуру | Скрыть ноды с инфраструктурными ролями (Router, Router Late, Client Base) | . | Исключить MQTT | Скрыть ноды, слышимые только через интернет-мост MQTT | . | Показать игнорируемые | Показать ноды, которые ты раньше скрывал или заглушал | . Параметры сортировки . | Сортировка | Описание | . | Последнее слышанное (по умолчанию) | Сначала недавно слышимые ноды | . | По алфавиту | Сортировать по полному имени ноды | . | Расстояние | Сначала ближайшие ноды (требуется обмен позициями) | . | Меньше хопов | Сначала с наименьшим количеством ретрансляций | . | Канал | Группировать по индексу канала | . | Через MQTT | Сгруппировать по MQTT и радиоприему | . | Избранное | Сначала избранные ноды | . ", "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#%D1%84%D0%B8%D0%BB%D1%8C%D1%82%D1%80%D0%B0%D1%86%D0%B8%D1%8F-%D0%B8-%D1%81%D0%BE%D1%80%D1%82%D0%B8%D1%80%D0%BE%D0%B2%D0%BA%D0%B0", "relUrl": "/ru-rRU/user/nodes.html#фильтрация-и-сортировка" - },"3954": { + },"3891": { "doc": "Ноды", "title": "Нод на хоп", "content": "Нажми на значок гистограммы хопов в панели приложений списка нод, чтобы открыть столбчатую диаграмму того, сколько нод находится на каждом расстоянии хопа (0 = напрямую, 1 = через один ретранслятор и так далее). Отфильтруй график по окну последнего услышанного — за всё время, 1 час, 8 часов или 24 часа — чтобы посмотреть, как сейчас выглядит сеть по сравнению с более длительным периодом. Это быстрый способ понять, насколько занята и разветвлена твоя местная сеть. ", "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#%D0%BD%D0%BE%D0%B4-%D0%BD%D0%B0-%D1%85%D0%BE%D0%BF", "relUrl": "/ru-rRU/user/nodes.html#нод-на-хоп" - },"3955": { + },"3892": { "doc": "Ноды", "title": "Детали ноды", "content": "Нажатие на ноду открывает подробный вид с полной информацией. Смотри Метрики ноды для полной информации о метриках и телеметрии. Экран с деталями включает информацию об устройстве, его местоположение и кнопки действий: . Встроенные индикаторы статуса показывают ключевые показатели с первого взгляда: . | Индикатор | Снимок экрана | . | Качество сигнала | | . | Уровень заряда батареи | | . | Количество хопов | | . | Последний раз слышен | | . | Расстояние | | . Ссылки на устройства (“Хочу такое”) . Когда оборудование ноды распознано, в детальном просмотре появляется сворачиваемый раздел “Хочу такой”, содержащий ссылки на места, где можно купить или узнать больше об этом устройстве: страницу продукта у производителя, варианты продукта и объявления на региональных торговых площадках (например, AliExpress, Amazon и у поддерживаемых продавцов), отфильтрованные по твоей стране. Каждая ссылка открывается через сервис перенаправления msh.to. Устройства без подходящих ссылок не показывают этот раздел. Полный, просматриваемый каталог всех ссылок также доступен в Настройки → Справка и документация → Ссылки на устройства. ", "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#%D0%B4%D0%B5%D1%82%D0%B0%D0%BB%D0%B8-%D0%BD%D0%BE%D0%B4%D1%8B", "relUrl": "/ru-rRU/user/nodes.html#детали-ноды" - },"3956": { + },"3893": { "doc": "Ноды", "title": "Связанные темы", "content": ". | Метрики ноды — подробные телеметрические панели для каждой ноды | Сообщения и каналы — отправь личное сообщение ноде | Карта и путевые точки — просмот позиции нод на карте | Обнаружение — трассировка и информация о соседях для изучения топологии | Индикатор сигнала — пойми, что означают полоски сигнала | . ", "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#связанные-темы" - },"3957": { + },"3894": { + "doc": "노드", + "title": "노드", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html", + + "relUrl": "/ko-rKR/user/nodes.html" + },"3895": { + "doc": "노드", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | 역할 | 설명 | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#node-list", + + "relUrl": "/ko-rKR/user/nodes.html#node-list" + },"3896": { + "doc": "노드", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#quick-actions", + + "relUrl": "/ko-rKR/user/nodes.html#quick-actions" + },"3897": { + "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 . | 필터 | 설명 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | 설명 | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#filtering--sorting", + + "relUrl": "/ko-rKR/user/nodes.html#filtering--sorting" + },"3898": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#nodes-per-hop", + + "relUrl": "/ko-rKR/user/nodes.html#nodes-per-hop" + },"3899": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | 최근 수신 | | . | 거리 | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#node-detail", + + "relUrl": "/ko-rKR/user/nodes.html#node-detail" + },"3900": { + "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 | 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" + },"3901": { "doc": "Nodes", "title": "Nodes", "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html", + "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html", - "relUrl": "/nl-rNL/user/nodes.html" - },"3958": { + "relUrl": "/hr-rHR/user/nodes.html" + },"3902": { "doc": "Nodes", "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Functie | Beschrijving | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#node-list", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Opis | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#node-list", - "relUrl": "/nl-rNL/user/nodes.html#node-list" - },"3959": { + "relUrl": "/hr-rHR/user/nodes.html#node-list" + },"3903": { "doc": "Nodes", "title": "Quick Actions", "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#quick-actions", + "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#quick-actions", - "relUrl": "/nl-rNL/user/nodes.html#quick-actions" - },"3960": { + "relUrl": "/hr-rHR/user/nodes.html#quick-actions" + },"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 . | Filter | Beschrijving | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Beschrijving | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Opis | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#filtering--sorting", - "relUrl": "/nl-rNL/user/nodes.html#filtering--sorting" - },"3961": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#nodes-per-hop", + "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#nodes-per-hop", - "relUrl": "/nl-rNL/user/nodes.html#nodes-per-hop" - },"3962": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Laatst gehoord | | . | Afstand | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#node-detail", + "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Posljednje čuo | | . | Udaljenost | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#node-detail", - "relUrl": "/nl-rNL/user/nodes.html#node-detail" - },"3963": { + "relUrl": "/hr-rHR/user/nodes.html#node-detail" + },"3907": { "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 | 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", + "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#related-topics", - "relUrl": "/nl-rNL/user/nodes.html#related-topics" + "relUrl": "/hr-rHR/user/nodes.html#related-topics" + },"3908": { + "doc": "Nodes", + "title": "Nodes", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html", + + "relUrl": "/sq-rAL/user/nodes.html" + },"3909": { + "doc": "Nodes", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Përshkrimi | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#node-list", + + "relUrl": "/sq-rAL/user/nodes.html#node-list" + },"3910": { + "doc": "Nodes", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#quick-actions", + + "relUrl": "/sq-rAL/user/nodes.html#quick-actions" + },"3911": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Përshkrimi | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#filtering--sorting", + + "relUrl": "/sq-rAL/user/nodes.html#filtering--sorting" + },"3912": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#nodes-per-hop", + + "relUrl": "/sq-rAL/user/nodes.html#nodes-per-hop" + },"3913": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | I fundit që u dëgjua | | . | Distanca | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#node-detail", + + "relUrl": "/sq-rAL/user/nodes.html#node-detail" + },"3914": { + "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 | 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" + },"3915": { + "doc": "Nodes", + "title": "Nodes", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html", + + "relUrl": "/no-rNO/user/nodes.html" + },"3916": { + "doc": "Nodes", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Beskrivelse | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#node-list", + + "relUrl": "/no-rNO/user/nodes.html#node-list" + },"3917": { + "doc": "Nodes", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#quick-actions", + + "relUrl": "/no-rNO/user/nodes.html#quick-actions" + },"3918": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Beskrivelse | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#filtering--sorting", + + "relUrl": "/no-rNO/user/nodes.html#filtering--sorting" + },"3919": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#nodes-per-hop", + + "relUrl": "/no-rNO/user/nodes.html#nodes-per-hop" + },"3920": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Sist hørt | | . | Distanse | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#node-detail", + + "relUrl": "/no-rNO/user/nodes.html#node-detail" + },"3921": { + "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 | 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" + },"3922": { + "doc": "Nodes", + "title": "Nodes", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html", + + "relUrl": "/lt-rLT/user/nodes.html" + },"3923": { + "doc": "Nodes", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Aprašymas | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#node-list", + + "relUrl": "/lt-rLT/user/nodes.html#node-list" + },"3924": { + "doc": "Nodes", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#quick-actions", + + "relUrl": "/lt-rLT/user/nodes.html#quick-actions" + },"3925": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Aprašymas | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#filtering--sorting", + + "relUrl": "/lt-rLT/user/nodes.html#filtering--sorting" + },"3926": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#nodes-per-hop", + + "relUrl": "/lt-rLT/user/nodes.html#nodes-per-hop" + },"3927": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Seniausiai girdėtas | | . | Atstumas | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#node-detail", + + "relUrl": "/lt-rLT/user/nodes.html#node-detail" + },"3928": { + "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 | 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" + },"3929": { + "doc": "Nodes", + "title": "Nodes", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html", + + "relUrl": "/ar-rSA/user/nodes.html" + },"3930": { + "doc": "Nodes", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | الوصف | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#node-list", + + "relUrl": "/ar-rSA/user/nodes.html#node-list" + },"3931": { + "doc": "Nodes", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#quick-actions", + + "relUrl": "/ar-rSA/user/nodes.html#quick-actions" + },"3932": { + "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 . | عربي | الوصف | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | الوصف | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#filtering--sorting", + + "relUrl": "/ar-rSA/user/nodes.html#filtering--sorting" + },"3933": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#nodes-per-hop", + + "relUrl": "/ar-rSA/user/nodes.html#nodes-per-hop" + },"3934": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | آخر ظهور | | . | المسافة | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#node-detail", + + "relUrl": "/ar-rSA/user/nodes.html#node-detail" + },"3935": { + "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 | 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" + },"3936": { + "doc": "Nodes", + "title": "Nodes", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html", + + "relUrl": "/pt-rPT/user/nodes.html" + },"3937": { + "doc": "Nodes", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Papel | Descrição | . | Cliente | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#node-list", + + "relUrl": "/pt-rPT/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 | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#quick-actions", + + "relUrl": "/pt-rPT/user/nodes.html#quick-actions" + },"3939": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descrição | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#filtering--sorting", + + "relUrl": "/pt-rPT/user/nodes.html#filtering--sorting" + },"3940": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#nodes-per-hop", + + "relUrl": "/pt-rPT/user/nodes.html#nodes-per-hop" + },"3941": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Último recebido | | . | Distância | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#node-detail", + + "relUrl": "/pt-rPT/user/nodes.html#node-detail" + },"3942": { + "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 | 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" + },"3943": { + "doc": "Nodes", + "title": "Nodes", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html", + + "relUrl": "/iw-rIL/user/nodes.html" + },"3944": { + "doc": "Nodes", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | תיאור | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#node-list", + + "relUrl": "/iw-rIL/user/nodes.html#node-list" + },"3945": { + "doc": "Nodes", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#quick-actions", + + "relUrl": "/iw-rIL/user/nodes.html#quick-actions" + },"3946": { + "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 . | פילטר | תיאור | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | תיאור | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#filtering--sorting", + + "relUrl": "/iw-rIL/user/nodes.html#filtering--sorting" + },"3947": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#nodes-per-hop", + + "relUrl": "/iw-rIL/user/nodes.html#nodes-per-hop" + },"3948": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | מרחק | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#node-detail", + + "relUrl": "/iw-rIL/user/nodes.html#node-detail" + },"3949": { + "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 | 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" + },"3950": { + "doc": "Nodes", + "title": "Nodes", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html", + + "relUrl": "/el-rGR/user/nodes.html" + },"3951": { + "doc": "Nodes", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Περιγραφή | . | Client | Standard end-user device | . | Πελάτης Βάση | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#node-list", + + "relUrl": "/el-rGR/user/nodes.html#node-list" + },"3952": { + "doc": "Nodes", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#quick-actions", + + "relUrl": "/el-rGR/user/nodes.html#quick-actions" + },"3953": { + "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 . | Φίλτρο | Περιγραφή | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Περιγραφή | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#filtering--sorting", + + "relUrl": "/el-rGR/user/nodes.html#filtering--sorting" + },"3954": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#nodes-per-hop", + + "relUrl": "/el-rGR/user/nodes.html#nodes-per-hop" + },"3955": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | Απόσταση | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#node-detail", + + "relUrl": "/el-rGR/user/nodes.html#node-detail" + },"3956": { + "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 | 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" + },"3957": { + "doc": "Noduri", + "title": "Noduri", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html", + + "relUrl": "/ro-rRO/user/nodes.html" + },"3958": { + "doc": "Noduri", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Descriere | . | Client | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#node-list", + + "relUrl": "/ro-rRO/user/nodes.html#node-list" + },"3959": { + "doc": "Noduri", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#quick-actions", + + "relUrl": "/ro-rRO/user/nodes.html#quick-actions" + },"3960": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descriere | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#filtering--sorting", + + "relUrl": "/ro-rRO/user/nodes.html#filtering--sorting" + },"3961": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#nodes-per-hop", + + "relUrl": "/ro-rRO/user/nodes.html#nodes-per-hop" + },"3962": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Ultima recepție | | . | Distanță | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#node-detail", + + "relUrl": "/ro-rRO/user/nodes.html#node-detail" + },"3963": { + "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 | 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" },"3964": { "doc": "Sõlmed", "title": "Sõlmed", @@ -27796,1902 +27796,1902 @@ "relUrl": "/et-rEE/user/nodes.html#related-topics" },"3971": { - "doc": "Nodi", - "title": "Nodi", + "doc": "Nodes", + "title": "Nodes", "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html", + "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html", - "relUrl": "/it-rIT/user/nodes.html" + "relUrl": "/ga-rIE/user/nodes.html" },"3972": { - "doc": "Nodi", + "doc": "Nodes", "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Ruolo | Descrizione | . | Client | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#node-list", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Cur síos | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#node-list", - "relUrl": "/it-rIT/user/nodes.html#node-list" + "relUrl": "/ga-rIE/user/nodes.html#node-list" },"3973": { - "doc": "Nodi", + "doc": "Nodes", "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Rimuovi Nodo | . | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#quick-actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#quick-actions", - "relUrl": "/it-rIT/user/nodes.html#quick-actions" + "relUrl": "/ga-rIE/user/nodes.html#quick-actions" },"3974": { - "doc": "Nodi", + "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 | Descrizione | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descrizione | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Cur síos | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#filtering--sorting", - "relUrl": "/it-rIT/user/nodes.html#filtering--sorting" + "relUrl": "/ga-rIE/user/nodes.html#filtering--sorting" },"3975": { - "doc": "Nodi", + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#nodes-per-hop", + "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#nodes-per-hop", - "relUrl": "/it-rIT/user/nodes.html#nodes-per-hop" + "relUrl": "/ga-rIE/user/nodes.html#nodes-per-hop" },"3976": { - "doc": "Nodi", + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Livello batteria | | . | Hop count | | . | Ricevuto più di recente | | . | Distanza | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#node-detail", + "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Deiridh chluinmhu | | . | Sáth | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#node-detail", - "relUrl": "/it-rIT/user/nodes.html#node-detail" + "relUrl": "/ga-rIE/user/nodes.html#node-detail" },"3977": { - "doc": "Nodi", + "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 | 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#related-topics", - "relUrl": "/it-rIT/user/nodes.html#related-topics" + "relUrl": "/ga-rIE/user/nodes.html#related-topics" },"3978": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html", - - "relUrl": "/ar-rSA/user/nodes.html" - },"3979": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | الوصف | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#node-list", - - "relUrl": "/ar-rSA/user/nodes.html#node-list" - },"3980": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#quick-actions", - - "relUrl": "/ar-rSA/user/nodes.html#quick-actions" - },"3981": { - "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 . | عربي | الوصف | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | الوصف | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#filtering--sorting", - - "relUrl": "/ar-rSA/user/nodes.html#filtering--sorting" - },"3982": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#nodes-per-hop", - - "relUrl": "/ar-rSA/user/nodes.html#nodes-per-hop" - },"3983": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | آخر ظهور | | . | المسافة | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#node-detail", - - "relUrl": "/ar-rSA/user/nodes.html#node-detail" - },"3984": { - "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 | 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" - },"3985": { - "doc": "Nodes", - "title": "Nodes", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html", - - "relUrl": "/sk-rSK/user/nodes.html" - },"3986": { - "doc": "Nodes", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rola | Popis | . | Klient | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#node-list", - - "relUrl": "/sk-rSK/user/nodes.html#node-list" - },"3987": { - "doc": "Nodes", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#quick-actions", - - "relUrl": "/sk-rSK/user/nodes.html#quick-actions" - },"3988": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Popis | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#filtering--sorting", - - "relUrl": "/sk-rSK/user/nodes.html#filtering--sorting" - },"3989": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#nodes-per-hop", - - "relUrl": "/sk-rSK/user/nodes.html#nodes-per-hop" - },"3990": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Posledný príjem | | . | Vzdialenosť | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#node-detail", - - "relUrl": "/sk-rSK/user/nodes.html#node-detail" - },"3991": { - "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 | 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" - },"3992": { "doc": "Węzły", "title": "Węzły", "content": "The Nodes screen displays all devices visible on your mesh network. ", "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html", "relUrl": "/pl-rPL/user/nodes.html" - },"3993": { + },"3979": { "doc": "Węzły", "title": "Node List", "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rola | Opis | . | Klient | Standard end-user device | . | 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 & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#node-list", "relUrl": "/pl-rPL/user/nodes.html#node-list" - },"3994": { + },"3980": { "doc": "Węzły", "title": "Quick Actions", "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Usuń węzeł | . | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#quick-actions", "relUrl": "/pl-rPL/user/nodes.html#quick-actions" - },"3995": { + },"3981": { "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Opis | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#filtering--sorting", "relUrl": "/pl-rPL/user/nodes.html#filtering--sorting" - },"3996": { + },"3982": { "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#nodes-per-hop", "relUrl": "/pl-rPL/user/nodes.html#nodes-per-hop" - },"3997": { + },"3983": { "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Poziom naładowania baterii | | . | Hop count | | . | Aktywność | | . | Odległość | | . 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 under Settings → Help & Documentation → Device Links. ", "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#node-detail", "relUrl": "/pl-rPL/user/nodes.html#node-detail" - },"3998": { + },"3984": { "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 | 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" - },"3999": { - "doc": "節點", - "title": "節點", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html", - - "relUrl": "/zh-rTW/user/nodes.html" - },"4000": { - "doc": "節點", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | 角色 | 描述說明 | . | 用戶端 | Standard end-user device | . | 客戶端基礎模式 | 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 & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#node-list", - - "relUrl": "/zh-rTW/user/nodes.html#node-list" - },"4001": { - "doc": "節點", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | 移除節點 | . | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#quick-actions", - - "relUrl": "/zh-rTW/user/nodes.html#quick-actions" - },"4002": { - "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 . | 過濾器 | 描述說明 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | 描述說明 | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#filtering--sorting", - - "relUrl": "/zh-rTW/user/nodes.html#filtering--sorting" - },"4003": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#nodes-per-hop", - - "relUrl": "/zh-rTW/user/nodes.html#nodes-per-hop" - },"4004": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | 螢幕截圖 | . | Signal quality | | . | 電池電量 | | . | Hop count | | . | 最近一次收到排序 | | . | 距離 | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#node-detail", - - "relUrl": "/zh-rTW/user/nodes.html#node-detail" - },"4005": { - "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 | 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" - },"4006": { - "doc": "Uzly", - "title": "Uzly", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html", - - "relUrl": "/cs-rCZ/user/nodes.html" - },"4007": { - "doc": "Uzly", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Popis | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Senzor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#node-list", - - "relUrl": "/cs-rCZ/user/nodes.html#node-list" - },"4008": { - "doc": "Uzly", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#quick-actions", - - "relUrl": "/cs-rCZ/user/nodes.html#quick-actions" - },"4009": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Popis | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#filtering--sorting", - - "relUrl": "/cs-rCZ/user/nodes.html#filtering--sorting" - },"4010": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#nodes-per-hop", - - "relUrl": "/cs-rCZ/user/nodes.html#nodes-per-hop" - },"4011": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Naposledy slyšen | | . | Vzdálenost | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#node-detail", - - "relUrl": "/cs-rCZ/user/nodes.html#node-detail" - },"4012": { - "doc": "Uzly", - "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 | 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#related-topics", - - "relUrl": "/cs-rCZ/user/nodes.html#related-topics" - },"4013": { - "doc": "Nœuds", - "title": "Nœuds", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html", - - "relUrl": "/fr-rFR/user/nodes.html" - },"4014": { - "doc": "Nœuds", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rôle | Description | . | Client | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#node-list", - - "relUrl": "/fr-rFR/user/nodes.html#node-list" - },"4015": { - "doc": "Nœuds", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Supprimer le nœud | . | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#quick-actions", - - "relUrl": "/fr-rFR/user/nodes.html#quick-actions" - },"4016": { - "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Description | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#filtering--sorting", - - "relUrl": "/fr-rFR/user/nodes.html#filtering--sorting" - },"4017": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#nodes-per-hop", - - "relUrl": "/fr-rFR/user/nodes.html#nodes-per-hop" - },"4018": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Niveau de batterie | | . | Hop count | | . | Dernière écoute | | . | Distance | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#node-detail", - - "relUrl": "/fr-rFR/user/nodes.html#node-detail" - },"4019": { - "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 | 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" - },"4020": { - "doc": "节点", - "title": "节点", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html", - - "relUrl": "/zh-rCN/user/nodes.html" - },"4021": { - "doc": "节点", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | 角色 | 说明 | . | 客户端 | Standard end-user device | . | 客户群 | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | 图标 | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#node-list", - - "relUrl": "/zh-rCN/user/nodes.html#node-list" - },"4022": { - "doc": "节点", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | 删除节点 | . | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#quick-actions", - - "relUrl": "/zh-rCN/user/nodes.html#quick-actions" - },"4023": { - "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 . | 搜索节点 | 说明 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | 说明 | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#filtering--sorting", - - "relUrl": "/zh-rCN/user/nodes.html#filtering--sorting" - },"4024": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#nodes-per-hop", - - "relUrl": "/zh-rCN/user/nodes.html#nodes-per-hop" - },"4025": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | 电池电量 | | . | Hop count | | . | 最后听到 | | . | 距离 | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#node-detail", - - "relUrl": "/zh-rCN/user/nodes.html#node-detail" - },"4026": { - "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 | 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" - },"4027": { - "doc": "Чворови", - "title": "Чворови", - "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/srp/user/nodes.html", - - "relUrl": "/srp/user/nodes.html" - },"4028": { - "doc": "Чворови", - "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Улога | Опис | . | Клијент | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Клијент мутиран | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Иконица | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/srp/user/nodes.html#node-list", - - "relUrl": "/srp/user/nodes.html#node-list" - },"4029": { - "doc": "Чворови", - "title": "Quick Actions", - "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/srp/user/nodes.html#quick-actions", - - "relUrl": "/srp/user/nodes.html#quick-actions" - },"4030": { - "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 . | Филтер | Опис | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Опис | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/srp/user/nodes.html#filtering--sorting", - - "relUrl": "/srp/user/nodes.html#filtering--sorting" - },"4031": { - "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/srp/user/nodes.html#nodes-per-hop", - - "relUrl": "/srp/user/nodes.html#nodes-per-hop" - },"4032": { - "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Последње откривање | | . | Раздаљина | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/srp/user/nodes.html#node-detail", - - "relUrl": "/srp/user/nodes.html#node-detail" - },"4033": { - "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 | 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" - },"4034": { + },"3985": { "doc": "Nodes", "title": "Nodes", "content": "The Nodes screen displays all devices visible on your mesh network. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html", + "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html", - "relUrl": "/sq-rAL/user/nodes.html" - },"4035": { + "relUrl": "/nl-rNL/user/nodes.html" + },"3986": { "doc": "Nodes", "title": "Node List", - "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Përshkrimi | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#node-list", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Functie | Beschrijving | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#node-list", - "relUrl": "/sq-rAL/user/nodes.html#node-list" - },"4036": { + "relUrl": "/nl-rNL/user/nodes.html#node-list" + },"3987": { "doc": "Nodes", "title": "Quick Actions", "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#quick-actions", + "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#quick-actions", - "relUrl": "/sq-rAL/user/nodes.html#quick-actions" - },"4037": { + "relUrl": "/nl-rNL/user/nodes.html#quick-actions" + },"3988": { "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Përshkrimi | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Beschrijving | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#filtering--sorting", - "relUrl": "/sq-rAL/user/nodes.html#filtering--sorting" - },"4038": { + "relUrl": "/nl-rNL/user/nodes.html#filtering--sorting" + },"3989": { "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#nodes-per-hop", + "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#nodes-per-hop", - "relUrl": "/sq-rAL/user/nodes.html#nodes-per-hop" - },"4039": { + "relUrl": "/nl-rNL/user/nodes.html#nodes-per-hop" + },"3990": { "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | I fundit që u dëgjua | | . | Distanca | | . 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 under Settings → Help & Documentation → Device Links. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#node-detail", + "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Laatst gehoord | | . | Afstand | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#node-detail", - "relUrl": "/sq-rAL/user/nodes.html#node-detail" - },"4040": { + "relUrl": "/nl-rNL/user/nodes.html#node-detail" + },"3991": { "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 | 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", + "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#related-topics", - "relUrl": "/sq-rAL/user/nodes.html#related-topics" + "relUrl": "/nl-rNL/user/nodes.html#related-topics" + },"3992": { + "doc": "Noder", + "title": "Noder", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html", + + "relUrl": "/sv-rSE/user/nodes.html" + },"3993": { + "doc": "Noder", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Roll | Beskrivning | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#node-list", + + "relUrl": "/sv-rSE/user/nodes.html#node-list" + },"3994": { + "doc": "Noder", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Ta bort nod | . | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#quick-actions", + + "relUrl": "/sv-rSE/user/nodes.html#quick-actions" + },"3995": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Beskrivning | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#filtering--sorting", + + "relUrl": "/sv-rSE/user/nodes.html#filtering--sorting" + },"3996": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#nodes-per-hop", + + "relUrl": "/sv-rSE/user/nodes.html#nodes-per-hop" + },"3997": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Batterinivå | | . | Hop count | | . | Senast hörd | | . | Avstånd | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#node-detail", + + "relUrl": "/sv-rSE/user/nodes.html#node-detail" + },"3998": { + "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 | 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" + },"3999": { + "doc": "ノード", + "title": "ノード", + "content": "ノード画面には、メッシュネットワーク上で見えているすべてのデバイスが表示されます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html", + + "relUrl": "/ja-rJP/user/nodes.html" + },"4000": { + "doc": "ノード", + "title": "ノードリスト", + "content": "ノードリストには、無線機が受信したすべてのノードが、次の情報とともに表示されます： . | ノード名： ユーザーが設定した正式名称 | 短縮名： 4 文字の識別子 | 信号品質： 最後に受信したときの信号強度 | 最後の通信： 最後に通信してからの経過時間 | 距離： 推定距離（位置情報が共有されている場合） | バッテリー： リモートノードのバッテリー残量（テレメトリが有効な場合） | . ノードのステータス表示 . | バッジ | 意味 | . | 🟢 オンライン | 過去 2 時間以内に受信したノード | . | ⚪ オフライン | 2 時間を超えて受信していないノード | . | ⭐ お気に入り | ユーザーがお気に入りに設定したノード | . ノードは、過去 2 時間以内に受信していればオンライン、そうでなければオフラインとみなされます。「離席中」のような中間の段階はありません。 . ノードの役割 . ノードには、メッシュ上での動作に影響するさまざまな役割を設定できます： . | 役割 | 説明 | . | クライアント | 標準的なエンドユーザーのデバイス | . | クライアント・ベース | お気に入りノードの通信をルーター・レイトの優先度で扱い、それ以外の通信はクライアントとして扱います | . | クライアント・ミュート | 受信しますが、再送信はしません | . | クライアント・非表示 | クライアント・ミュートと同様で、さらにノードリストから隠れます | . | ルーター | メッセージの転送を優先し、中継のために起動し続けます | . | ルーター・レイト | 1 回だけ再送信するインフラノードですが、他のすべてのモードの後にのみ行います（補助的なカバレッジを提供します） | . | ルーター・クライアント | ⚠️ 非推奨（ファームウェア 2.3.15 で削除）。選択できなくなりました。代わりにルーターまたはクライアントを使用してください | . | リピーター | ⚠️ 非推奨（ファームウェア 2.7.11 で削除）。選択できなくなりました。代わりにルーターを使用してください | . | トラッカー | 一定間隔での位置報告に最適化されています | . | センサー | テレメトリ報告に最適化されています | . | TAK | TAK システムと相互運用します（CoT を送受信） | . | TAK Tracker | TAK の位置報告のみ | . | ロスト＆ファウンド | 回収のために位置を継続的に発信します | . 役割を選ぶ . ほとんどのユーザーは、デフォルトのクライアント役割のままにしてください。 次のような場合は、別の役割を検討してください： . | ルーター： 電源が安定した、固定された高所（屋上、丘の上など）にノードを設置している場合。 ルーターは他のノードのメッセージを中継するために常に起動し続け、メッシュのカバレッジ拡大に不可欠です。 バッテリー駆動のハンドヘルドデバイスではルーターを使用しないでください。 | ルーター・レイト： パケットを常に 1 回だけ再送信するインフラノードですが、他のすべてのルーティングモードの番が終わった後にのみ行います。 主要なルーターと競合することなく、ローカルのクラスターに補助的なカバレッジを提供します。 | クライアント・ベース： お気に入りノードとの間の通信をルーター・レイトの優先度で扱い（それらのメッセージが追加の中継カバレッジを得られるようにします）、それ以外はすべて通常のクライアントとして処理します。 | クライアント・ミュート： メッシュの通信を受信したいが、中継には貢献したくない場合。 監視専用のデバイスや、混雑した地域での輻輳軽減に便利です。 | トラッカー： GPS 位置の発信だけを目的とする無人デバイス（車両、ペット、資産など）。 発信の合間はスリープしてバッテリーを節約します。 | センサー： 環境テレメトリ（気温、湿度、大気質）を報告する無人デバイス。 電力プロファイルはトラッカーと同様です。 | TAK／TAK Tracker： ATAK／WinTAK システムと相互運用する場合にのみ必要です。 詳しくは TAK 連携 を参照してください。 | . 💡 ヒント： メッシュは、ほとんどのノードがクライアントまたはルーターのときに最も良く機能します。 ミュートノードが多すぎるとメッシュの耐障害性が低下し、混雑した地域にルーターが多すぎると輻輳を招くことがあります。 目安としては、地域内のクライアント 5〜10 台につきルーター 1 台です。 . 暗号化の表示 . ノードは、名前の横に暗号化ステータスのアイコンを表示します： . | アイコン | 意味 | . | 🔒 ロック | 通信は PKI（公開鍵基盤）を使用します。本人性が検証された、エンドツーエンドの暗号化です | . | 🔓 ロック解除 | 通信は共有チャンネルの PSK を使用します。暗号化されていますが、本人性は個別には検証されていません | . | ⚠️ 不一致 | 公開鍵の不一致。前回確認時からノードの鍵が変わっています（信頼する前に調べてください） | . 💡 ヒント： PKI 暗号化（ファームウェア 2.5 以降）は、各ノードが固有の鍵ペアを持つため、チャンネル PSK より強力なセキュリティを提供します。 鍵の不一致の警告が表示された場合、そのノードはリセットされたか、侵害された可能性があります。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#%E3%83%8E%E3%83%BC%E3%83%89%E3%83%AA%E3%82%B9%E3%83%88", + + "relUrl": "/ja-rJP/user/nodes.html#ノードリスト" + },"4001": { + "doc": "ノード", + "title": "クイック操作", + "content": "ノードリストから、次のことができます： . | ノードをタップすると詳細ページを表示します | 長押しでクイック操作を表示します： . | お気に入りに追加／解除 | 通知のミュート／解除 | ダイレクトメッセージを送信 | 経路をトレース | 無視／無視の解除 | ノードを削除 | . | . ", + "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#クイック操作" + },"4002": { + "doc": "ノード", + "title": "絞り込みと並べ替え", + "content": "テキスト検索 . 検索欄に入力すると、名前または短縮名でノードを絞り込めます。 絞り込みは、入力に応じてリアルタイムで更新されます。 . 絞り込みトグル . | 絞り込み | 説明 | . | オンラインのみ | 過去 2 時間以内に受信したノードのみを表示します | . | 直接のみ | 直接（中継されていない）接続のノードのみを表示します | . | 不明なノードを含む | まだユーザー情報を送信していないノードを表示します | . | インフラを除外 | インフラ役割のノード（ルーター、ルーター・レイト、クライアント・ベース）を非表示にします | . | MQTT を除外 | MQTT のインターネットブリッジ経由でのみ受信したノードを非表示にします | . | 無視したノードを表示 | 以前に非表示またはミュートにしたノードを表示します | . 並べ替えオプション . | 並べ替え | 説明 | . | 最後の通信（デフォルト） | 最近受信したノードを先頭に表示します | . | アルファベット順 | ノードの正式名称で並べ替えます | . | 距離 | 近いノードを先頭に表示します（位置情報の共有が必要） | . | ホップ数 | 中継ホップ数が少ないノードを先頭に表示します | . | チャンネル | チャンネルインデックスごとにグループ化します | . | MQTT 経由 | MQTT 経由と無線受信でグループ化します | . | お気に入り | お気に入りのノードを先頭に表示します | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#%E7%B5%9E%E3%82%8A%E8%BE%BC%E3%81%BF%E3%81%A8%E4%B8%A6%E3%81%B9%E6%9B%BF%E3%81%88", + + "relUrl": "/ja-rJP/user/nodes.html#絞り込みと並べ替え" + },"4003": { + "doc": "ノード", + "title": "ホップごとのノード数", + "content": "ノードリストのアプリバーにあるホップヒストグラムのアイコンをタップすると、各ホップ距離にいくつのノードがあるかを示す棒グラフが開きます（0 = 直接、1 = 中継 1 回、以下同様）。 グラフを最後の通信の期間（すべての期間、1 時間、8 時間、24 時間）で絞り込むと、現在のメッシュの様子と、より長い期間での様子を比較できます。 ローカルメッシュがどれだけ混雑し、どれだけ広がっているかを手早く把握できます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#%E3%83%9B%E3%83%83%E3%83%97%E3%81%94%E3%81%A8%E3%81%AE%E3%83%8E%E3%83%BC%E3%83%89%E6%95%B0", + + "relUrl": "/ja-rJP/user/nodes.html#ホップごとのノード数" + },"4004": { + "doc": "ノード", + "title": "ノードの詳細", + "content": "ノードをタップすると、詳しい情報を含む詳細ビューが開きます。 メトリクスとテレメトリの詳細については、ノードメトリクス を参照してください。 . 詳細画面には、デバイス情報、位置、操作ボタンが含まれます： . インラインのステータス表示で、主要なメトリクスをひと目で確認できます： . | 指標 | スクリーンショット | . | 信号品質 | | . | バッテリー残量 | | . | ホップ数 | | . | 最後の通信 | | . | 距離 | | . デバイスのリンク（「購入はこちら」） . ノードのハードウェアが認識されると、詳細ビューに折りたたみ式の**「購入はこちら」**セクションが表示され、そのデバイスを購入したり詳しく知ったりできる場所（ベンダーの製品ページ、製品バリエーション、AliExpress・Amazon・対応小売店などの地域のマーケットプレイスの掲載）が、あなたの国に合わせて絞り込まれて表示されます。 各リンクは msh.to のリダイレクトサービスを通じて開きます。 一致するリンクがないデバイスでは、このセクションは表示されません。 . すべてのリンクを一覧できる完全なディレクトリは、「設定 → ヘルプとドキュメント → デバイスのリンク」からも利用できます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#%E3%83%8E%E3%83%BC%E3%83%89%E3%81%AE%E8%A9%B3%E7%B4%B0", + + "relUrl": "/ja-rJP/user/nodes.html#ノードの詳細" + },"4005": { + "doc": "ノード", + "title": "関連トピック", + "content": ". | ノードメトリクス：各ノードの詳細なテレメトリダッシュボード | メッセージとチャンネル：ノードにダイレクトメッセージを送信 | マップとウェイポイント：ノードの位置を地図上で確認 | 探索：トポロジー探索のための経路トレースと隣接ノード情報 | 信号メーター：信号バーの意味を理解する | . ", + "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#関連トピック" + },"4006": { + "doc": "Csomópontok", + "title": "Csomópontok", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html", + + "relUrl": "/hu-rHU/user/nodes.html" + },"4007": { + "doc": "Csomópontok", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Szerepkör | Leírás | . | Kliens | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#node-list", + + "relUrl": "/hu-rHU/user/nodes.html#node-list" + },"4008": { + "doc": "Csomópontok", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#quick-actions", + + "relUrl": "/hu-rHU/user/nodes.html#quick-actions" + },"4009": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Leírás | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#filtering--sorting", + + "relUrl": "/hu-rHU/user/nodes.html#filtering--sorting" + },"4010": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#nodes-per-hop", + + "relUrl": "/hu-rHU/user/nodes.html#nodes-per-hop" + },"4011": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Utoljára hallott | | . | Távolság | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#node-detail", + + "relUrl": "/hu-rHU/user/nodes.html#node-detail" + },"4012": { + "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 | 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" + },"4013": { + "doc": "Nodes", + "title": "Nodes", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html", + + "relUrl": "/ht-rHT/user/nodes.html" + },"4014": { + "doc": "Nodes", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Deskripsyon | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#node-list", + + "relUrl": "/ht-rHT/user/nodes.html#node-list" + },"4015": { + "doc": "Nodes", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#quick-actions", + + "relUrl": "/ht-rHT/user/nodes.html#quick-actions" + },"4016": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Deskripsyon | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#filtering--sorting", + + "relUrl": "/ht-rHT/user/nodes.html#filtering--sorting" + },"4017": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#nodes-per-hop", + + "relUrl": "/ht-rHT/user/nodes.html#nodes-per-hop" + },"4018": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Dènye fwa li tande | | . | Distans | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#node-detail", + + "relUrl": "/ht-rHT/user/nodes.html#node-detail" + },"4019": { + "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 | 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" + },"4020": { + "doc": "Nodes", + "title": "Nodes", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html", + + "relUrl": "/gl-rES/user/nodes.html" + },"4021": { + "doc": "Nodes", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Descrición | . | Cliente | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#node-list", + + "relUrl": "/gl-rES/user/nodes.html#node-list" + },"4022": { + "doc": "Nodes", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#quick-actions", + + "relUrl": "/gl-rES/user/nodes.html#quick-actions" + },"4023": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descrición | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#filtering--sorting", + + "relUrl": "/gl-rES/user/nodes.html#filtering--sorting" + },"4024": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#nodes-per-hop", + + "relUrl": "/gl-rES/user/nodes.html#nodes-per-hop" + },"4025": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Última escoita | | . | Distancia | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#node-detail", + + "relUrl": "/gl-rES/user/nodes.html#node-detail" + },"4026": { + "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 | 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" + },"4027": { + "doc": "Nodelar", + "title": "Nodelar", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html", + + "relUrl": "/tr-rTR/user/nodes.html" + },"4028": { + "doc": "Nodelar", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rol | Açıklaması | . | Client | Standard end-user device | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#node-list", + + "relUrl": "/tr-rTR/user/nodes.html#node-list" + },"4029": { + "doc": "Nodelar", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Node sil | . | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#quick-actions", + + "relUrl": "/tr-rTR/user/nodes.html#quick-actions" + },"4030": { + "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ı | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Açıklaması | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#filtering--sorting", + + "relUrl": "/tr-rTR/user/nodes.html#filtering--sorting" + },"4031": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#nodes-per-hop", + + "relUrl": "/tr-rTR/user/nodes.html#nodes-per-hop" + },"4032": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Son duyulma | | . | Mesafe | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#node-detail", + + "relUrl": "/tr-rTR/user/nodes.html#node-detail" + },"4033": { + "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 | 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" + },"4034": { + "doc": "Nodos", + "title": "Nodos", + "content": "The Nodes screen displays all devices visible on your mesh network. ", + "url": "/Meshtastic-Android/main/es-rES/user/nodes.html", + + "relUrl": "/es-rES/user/nodes.html" + },"4035": { + "doc": "Nodos", + "title": "Node List", + "content": "The node list shows every node your radio has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — last heard signal strength | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Node Status Indicators . | Badge | Meaning | . | 🟢 Online | Node heard within the last 2 hours | . | ⚪ Offline | Node not heard for over 2 hours | . | ⭐ Favorite | Node marked as favorite by the user | . A node is considered online if it was heard within the last 2 hours, and offline otherwise — there is no separate “away” tier. Node Roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rol | Descripción | . | Cliente | Standard end-user device | . | 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 | . | Lost & Found | Continuous position beacon for recovery | . Choosing a Role . Most users should keep the default Client role. Consider a different role when: . | Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld devices. | Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers. | Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas. | Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Encryption Indicators . Nodes display encryption status icons next to their name: . | Icon | Meaning | . | 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | . | 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | . | ⚠️ Mismatch | Public key mismatch — the node’s key has changed since last seen (investigate before trusting) | . 💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. ", + "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#node-list", + + "relUrl": "/es-rES/user/nodes.html#node-list" + },"4036": { + "doc": "Nodos", + "title": "Quick Actions", + "content": "From the node list, you can: . | Tap a node to view its detail page | Long-press for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove node | . | . ", + "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#quick-actions", + + "relUrl": "/es-rES/user/nodes.html#quick-actions" + },"4037": { + "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 | . | Only online | Show only nodes heard within the last 2 hours | . | Only direct | Show only nodes with direct (non-relayed) connections | . | Include unknown | Show nodes that haven’t sent user info yet | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base) | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Show ignored | Show nodes you’ve previously dismissed or muted | . Sort Options . | Sort | Descripción | . | Last heard (default) | Most recently heard nodes first | . | Alphabetical | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | Via MQTT | Grouped by MQTT vs. radio-heard | . | Favorites | Favorited nodes first | . ", + "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#filtering--sorting", + + "relUrl": "/es-rES/user/nodes.html#filtering--sorting" + },"4038": { + "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 time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ", + "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#nodes-per-hop", + + "relUrl": "/es-rES/user/nodes.html#nodes-per-hop" + },"4039": { + "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. The detail screen includes device info, position, and action buttons: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Última escucha | | . | Distancia | | . 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 under Settings → Help & Documentation → Device Links. ", + "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#node-detail", + + "relUrl": "/es-rES/user/nodes.html#node-detail" + },"4040": { + "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 | 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" },"4041": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html", - - "relUrl": "/is-rIS/user/onboarding.html" - },"4042": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html#first-launch", - - "relUrl": "/is-rIS/user/onboarding.html#first-launch" - },"4043": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html#permissions", - - "relUrl": "/is-rIS/user/onboarding.html#permissions" - },"4044": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html#after-setup", - - "relUrl": "/is-rIS/user/onboarding.html#after-setup" - },"4045": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/is-rIS/user/onboarding.html#whats-next" - },"4046": { - "doc": "はじめに", - "title": "はじめに", - "content": "Meshtastic へようこそ！ このガイドでは、Meshtastic Android アプリの初期設定を順を追って説明します。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html", - - "relUrl": "/ja-rJP/user/onboarding.html" - },"4047": { - "doc": "はじめに", - "title": "初回起動", - "content": "アプリを初めて開くと、必要な権限と設定を構成するための導入フローが案内されます。 各ステップは順番に完了することも、スキップして後で Android の設定で権限を構成することもできます。 . ようこそ画面 . ようこそ画面では、Meshtastic とその主な機能を紹介します： . | オフグリッドのメッシュ通信 | 携帯電話やインターネットは不要 | エンドツーエンドで暗号化されたメッセージング | . 開始するをタップして、セットアップフローを進めます。 . ", - "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#初回起動" - },"4048": { - "doc": "はじめに", - "title": "権限", - "content": "アプリはセットアップ中にいくつかの権限を要求します。 それぞれに特定の目的があり、一部は主要な機能に必要です。 . Bluetooth の権限 . Bluetooth は、スマートフォンと Meshtastic 無線機の主な接続方法です： . | Bluetooth スキャン：近くの Meshtastic 無線機を検出します | Bluetooth 接続：ペアリング済みの無線機との接続を確立して維持します | . プロンプトが表示されたら、両方の権限を許可してください。 Bluetooth がない場合は、代わりに USB または TCP 接続を使用する必要があります。 . 位置情報の権限 . ⚠️ なぜ Bluetooth に位置情報が必要なのですか？ Android では、近くの Bluetooth Low Energy デバイスを検出するために位置情報の権限が必要です。 これは Android システムの要件であり、Meshtastic 固有の仕様ではありません。 . Meshtastic は、次の目的でも位置情報を使用します： . | メッシュマップ上に自分の位置を表示する | 他のノードまでの距離を計算する | 他のメッシュメンバーと GPS 座標を共有する（有効な場合） | . お好みに応じて、**「アプリの使用中のみ」または「常に許可」**を選択してください： . | アプリの使用中のみ：アプリが開いているときだけ位置情報を更新します | 常に許可：常時メッシュに存在するために、バックグラウンドでの位置情報更新を有効にします | . 拒否すると、Bluetooth スキャンが機能せず、ノードは位置情報を報告しません。 . 通知の権限 . 通知は、次のことをお知らせします： . | チャンネルおよびダイレクトメッセージの受信 | メッシュに参加する新しいノード | リモートノードのバッテリー低下 | . 💡 ヒント： 通知の設定は、後で Android のシステム設定で細かく調整できます。アプリはカテゴリごとに個別の通知チャンネルを作成する（さらに、バックグラウンドサービスなどの内部用のものもいくつか作成する）ため、個別に有効化したり消音したりできます。 . 重要なアラートの権限 . 対応デバイスでは、アプリが重要なアラートの権限を要求することがあります： . | これらは、サイレントモードを突破できる高優先度の通知です | 緊急のメッシュアラートや至急のメッセージに役立ちます | 突破通知が不要な場合は、このステップをスキップできます | 後で Android の通知設定で構成または取り消しができます | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html#%E6%A8%A9%E9%99%90", - - "relUrl": "/ja-rJP/user/onboarding.html#権限" - },"4049": { - "doc": "はじめに", - "title": "セットアップ後", - "content": "権限を許可すると、アプリはメイン画面に移行します。 最初に行うべきことは、Meshtastic 無線機への接続です。詳しい手順は接続を参照してください。 . 💡 ヒント： セットアップ中に権限をスキップした場合は、後で**「Android 設定 → アプリ → Meshtastic → 権限」**から許可できます。 不足している権限が、使おうとする機能を妨げる場合は、アプリが再度確認を求めます。 . ", - "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#セットアップ後" - },"4050": { - "doc": "はじめに", - "title": "次のステップ", - "content": "無線機に接続したら、次を確認してみましょう： . | 接続：最初の無線機デバイスをペアリングする | メッセージとチャンネル：最初のメッセージを送信する | ノード：メッシュに参加しているノードを確認する | マップとウェイポイント：ノードの位置を表示する | 設定：無線機とユーザープロフィールを構成する | . Meshtastic は初めてですか？ meshtastic.org の入門ガイドでは、ハードウェアの選択、無線機の初期設定、最初のメッシュのセットアップについて説明しています。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html#%E6%AC%A1%E3%81%AE%E3%82%B9%E3%83%86%E3%83%83%E3%83%97", - - "relUrl": "/ja-rJP/user/onboarding.html#次のステップ" - },"4051": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html", - - "relUrl": "/ca-rES/user/onboarding.html" - },"4052": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#first-launch", - - "relUrl": "/ca-rES/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#permissions", - - "relUrl": "/ca-rES/user/onboarding.html#permissions" - },"4054": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#after-setup", - - "relUrl": "/ca-rES/user/onboarding.html#after-setup" - },"4055": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/ca-rES/user/onboarding.html#whats-next" - },"4056": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html", - - "relUrl": "/sr-rLatn/user/onboarding.html" - },"4057": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html#first-launch", - - "relUrl": "/sr-rLatn/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html#permissions", - - "relUrl": "/sr-rLatn/user/onboarding.html#permissions" - },"4059": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html#after-setup", - - "relUrl": "/sr-rLatn/user/onboarding.html#after-setup" - },"4060": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/sr-rLatn/user/onboarding.html#whats-next" - },"4061": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html", - - "relUrl": "/ko-rKR/user/onboarding.html" - },"4062": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html#first-launch", - - "relUrl": "/ko-rKR/user/onboarding.html#first-launch" - },"4063": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html#permissions", - - "relUrl": "/ko-rKR/user/onboarding.html#permissions" - },"4064": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html#after-setup", - - "relUrl": "/ko-rKR/user/onboarding.html#after-setup" - },"4065": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/ko-rKR/user/onboarding.html#whats-next" - },"4066": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html", - - "relUrl": "/ro-rRO/user/onboarding.html" - },"4067": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html#first-launch", - - "relUrl": "/ro-rRO/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html#permissions", - - "relUrl": "/ro-rRO/user/onboarding.html#permissions" - },"4069": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html#after-setup", - - "relUrl": "/ro-rRO/user/onboarding.html#after-setup" - },"4070": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/ro-rRO/user/onboarding.html#whats-next" - },"4071": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html", - - "relUrl": "/ga-rIE/user/onboarding.html" - },"4072": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html#first-launch", - - "relUrl": "/ga-rIE/user/onboarding.html#first-launch" - },"4073": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html#permissions", - - "relUrl": "/ga-rIE/user/onboarding.html#permissions" - },"4074": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html#after-setup", - - "relUrl": "/ga-rIE/user/onboarding.html#after-setup" - },"4075": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/ga-rIE/user/onboarding.html#whats-next" - },"4076": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html", - - "relUrl": "/iw-rIL/user/onboarding.html" - },"4077": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html#first-launch", - - "relUrl": "/iw-rIL/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html#permissions", - - "relUrl": "/iw-rIL/user/onboarding.html#permissions" - },"4079": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html#after-setup", - - "relUrl": "/iw-rIL/user/onboarding.html#after-setup" - },"4080": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/iw-rIL/user/onboarding.html#whats-next" - },"4081": { - "doc": "Kom igång", - "title": "Kom igång", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html", - - "relUrl": "/sv-rSE/user/onboarding.html" - },"4082": { - "doc": "Kom igång", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html#first-launch", - - "relUrl": "/sv-rSE/user/onboarding.html#first-launch" - },"4083": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html#permissions", - - "relUrl": "/sv-rSE/user/onboarding.html#permissions" - },"4084": { - "doc": "Kom igång", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html#after-setup", - - "relUrl": "/sv-rSE/user/onboarding.html#after-setup" - },"4085": { - "doc": "Kom igång", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/sv-rSE/user/onboarding.html#whats-next" - },"4086": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html", - - "relUrl": "/ht-rHT/user/onboarding.html" - },"4087": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html#first-launch", - - "relUrl": "/ht-rHT/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html#permissions", - - "relUrl": "/ht-rHT/user/onboarding.html#permissions" - },"4089": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html#after-setup", - - "relUrl": "/ht-rHT/user/onboarding.html#after-setup" - },"4090": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/ht-rHT/user/onboarding.html#whats-next" - },"4091": { - "doc": "Aloittaminen", - "title": "Aloittaminen", - "content": "Tervetuloa Meshtasticiin! Tämä opas opastaa sinut Meshtastic Android -sovelluksen alkuasetusten läpi. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/onboarding.html", - - "relUrl": "/fi-rFI/user/onboarding.html" - },"4092": { - "doc": "Aloittaminen", - "title": "Ensimmäinen käynnistys", - "content": "Kun avaat sovelluksen ensimmäistä kertaa, sinut ohjataan käyttöönottoprosessin läpi, joka auttaa määrittämään tarvittavat käyttöoikeudet ja asetukset. Voit suorittaa jokaisen vaiheen järjestyksessä tai ohittaa ne ja määrittää käyttöoikeudet myöhemmin Androidin asetuksissa. Aloitusnäkymä . Tervetulonäyttö esittelee Meshtasticin ja sen tärkeimmät ominaisuudet: . | Matkapuhelinverkosta riippumaton mesh-viestintä | Ei vaadi matkapuhelinverkkoa tai internetyhteyttä | Päästä päähän salattu viestintä | . Napauta “Aloita” jatkaaksesi käyttöönottoprosessia. ", - "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" - },"4093": { - "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 on ensisijainen yhteystapa puhelimesi ja Meshtastic-radion välillä: . | Bluetooth-skannaus — etsi lähellä olevia Meshtastic-radioita | Bluetooth-yhteys — muodosta ja ylläpidä yhteyksiä pariliitettyihin radioihin | . Myönnä molemmat käyttöoikeudet pyydettäessä. Ilman Bluetoothia sinun on käytettävä sen sijaan USB- tai TCP-yhteyksiä. Sijaintikäyttöoikeus . ⚠️ Miksi sijaintikäyttöoikeus tarvitaan Bluetoothille? Android vaatii sijaintikäyttöoikeuden lähellä olevien Bluetooth Low Energy -laitteiden löytämiseen. Tämä on Android-järjestelmän vaatimus, eikä Meshtasticin erityinen valinta. 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” tai “Aina” oman mieltymyksesi mukaan: . | Sovelluksen käytön aikana — sijainti päivittyy vain silloin, kun sovellus on avoinna | Aina — mahdollistaa sijainnin päivittämisen taustalla jatkuvaa verkon läsnäoloa varten | . Jos käyttöoikeus evätään, Bluetooth-skannaus ei toimi eikä radiosi raportoi sijaintia. 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 . Tuetuilla laitteilla sovellus voi pyytää käyttöoikeutta kriittisiin hälytyksiin: . | Nämä ovat korkean prioriteetin ilmoituksia, jotka voivat ohittaa Älä häiritse -tilan | Hyödyllinen hätätilanteiden verkkohälytyksille tai kiireellisille viesteille | Voit ohittaa tämän vaiheen, jos et tarvitse ilmoituksia, jotka ohittavat Älä häiritse -tilan | Voit määrittää tai peruuttaa tämän myöhemmin Androidin ilmoitusasetuksissa | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/onboarding.html#k%C3%A4ytt%C3%B6oikeudet", - - "relUrl": "/fi-rFI/user/onboarding.html#käyttöoikeudet" - },"4094": { - "doc": "Aloittaminen", - "title": "Määrityksen jälkeen", - "content": "Kun käyttöoikeudet on myönnetty, sovellus siirtyy pääkäyttöliittymään. Ensimmäinen toimenpiteesi pitäisi olla yhteyden muodostaminen Meshtastic-radioon — katso Yhteydet yksityiskohtaisia ohjeita varten. 💡 Vinkki: Jos ohitit käyttöoikeuksia määrityksen aikana, voit myöntää ne myöhemmin kohdassa Androidin asetukset → Sovellukset → Meshtastic → Käyttöoikeudet. Sovellus pyytää sinulta uudelleen käyttöoikeutta, jos puuttuva käyttöoikeus estää käyttämästä ominaisuutta, jota yrität käyttää. ", - "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" - },"4095": { - "doc": "Aloittaminen", - "title": "Mitä seuraavaksi?", - "content": "Kun olet muodostanut yhteyden radioon, tutustu seuraaviin: . | Yhteydet — yhdistä ensimmäinen radiolaitteesi | Viestit ja kanavat — lähetä ensimmäinen viestisi | Radiot — katso, ketkä ovat verkossasi | Kartta ja reittipisteet — tarkastele radioiden sijainteja | Asetukset — määritä radiosi ja käyttäjäprofiilisi | . 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#mit%C3%A4-seuraavaksi", - - "relUrl": "/fi-rFI/user/onboarding.html#mitä-seuraavaksi" - },"4096": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html", - - "relUrl": "/gl-rES/user/onboarding.html" - },"4097": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html#first-launch", - - "relUrl": "/gl-rES/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html#permissions", - - "relUrl": "/gl-rES/user/onboarding.html#permissions" - },"4099": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html#after-setup", - - "relUrl": "/gl-rES/user/onboarding.html#after-setup" - },"4100": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/gl-rES/user/onboarding.html#whats-next" - },"4101": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html", - - "relUrl": "/uk-rUA/user/onboarding.html" - },"4102": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#first-launch", - - "relUrl": "/uk-rUA/user/onboarding.html#first-launch" - },"4103": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#permissions", - - "relUrl": "/uk-rUA/user/onboarding.html#permissions" - },"4104": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#after-setup", - - "relUrl": "/uk-rUA/user/onboarding.html#after-setup" - },"4105": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/uk-rUA/user/onboarding.html#whats-next" - },"4106": { "doc": "Erste Schritte", "title": "Erste Schritte", "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", "url": "/Meshtastic-Android/main/de-rDE/user/onboarding.html", "relUrl": "/de-rDE/user/onboarding.html" - },"4107": { + },"4042": { "doc": "Erste Schritte", "title": "First Launch", "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", "url": "/Meshtastic-Android/main/de-rDE/user/onboarding.html#first-launch", "relUrl": "/de-rDE/user/onboarding.html#first-launch" - },"4108": { + },"4043": { "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", "url": "/Meshtastic-Android/main/de-rDE/user/onboarding.html#permissions", "relUrl": "/de-rDE/user/onboarding.html#permissions" - },"4109": { + },"4044": { "doc": "Erste Schritte", "title": "After Setup", "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", "url": "/Meshtastic-Android/main/de-rDE/user/onboarding.html#after-setup", "relUrl": "/de-rDE/user/onboarding.html#after-setup" - },"4110": { + },"4045": { "doc": "Erste Schritte", "title": "What’s Next?", "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", "relUrl": "/de-rDE/user/onboarding.html#whats-next" - },"4111": { + },"4046": { "doc": "Getting Started", "title": "Getting Started", "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html", + "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html", - "relUrl": "/hr-rHR/user/onboarding.html" - },"4112": { + "relUrl": "/ca-rES/user/onboarding.html" + },"4047": { "doc": "Getting Started", "title": "First Launch", "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html#first-launch", + "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#first-launch", - "relUrl": "/hr-rHR/user/onboarding.html#first-launch" - },"4113": { + "relUrl": "/ca-rES/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html#permissions", + "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#permissions", - "relUrl": "/hr-rHR/user/onboarding.html#permissions" - },"4114": { + "relUrl": "/ca-rES/user/onboarding.html#permissions" + },"4049": { "doc": "Getting Started", "title": "After Setup", "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html#after-setup", + "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#after-setup", - "relUrl": "/hr-rHR/user/onboarding.html#after-setup" - },"4115": { + "relUrl": "/ca-rES/user/onboarding.html#after-setup" + },"4050": { "doc": "Getting Started", "title": "What’s Next?", "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#whats-next", - "relUrl": "/hr-rHR/user/onboarding.html#whats-next" - },"4116": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html", - - "relUrl": "/lt-rLT/user/onboarding.html" - },"4117": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html#first-launch", - - "relUrl": "/lt-rLT/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html#permissions", - - "relUrl": "/lt-rLT/user/onboarding.html#permissions" - },"4119": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html#after-setup", - - "relUrl": "/lt-rLT/user/onboarding.html#after-setup" - },"4120": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/lt-rLT/user/onboarding.html#whats-next" - },"4121": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/en/user/onboarding.html", - - "relUrl": "/en/user/onboarding.html" - },"4122": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/en/user/onboarding.html#first-launch", - - "relUrl": "/en/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/en/user/onboarding.html#permissions", - - "relUrl": "/en/user/onboarding.html#permissions" - },"4124": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/en/user/onboarding.html#after-setup", - - "relUrl": "/en/user/onboarding.html#after-setup" - },"4125": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/en/user/onboarding.html#whats-next" - },"4126": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html", - - "relUrl": "/hu-rHU/user/onboarding.html" - },"4127": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html#first-launch", - - "relUrl": "/hu-rHU/user/onboarding.html#first-launch" - },"4128": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html#permissions", - - "relUrl": "/hu-rHU/user/onboarding.html#permissions" - },"4129": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html#after-setup", - - "relUrl": "/hu-rHU/user/onboarding.html#after-setup" - },"4130": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/hu-rHU/user/onboarding.html#whats-next" - },"4131": { - "doc": "Първи стъпки", - "title": "Първи стъпки", - "content": "Добре дошли в Meshtastic! Това ръководство ви превежда през първоначалната настройка на приложението Meshtastic за Android. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html", - - "relUrl": "/bg-rBG/user/onboarding.html" - },"4132": { - "doc": "Първи стъпки", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html#first-launch", - - "relUrl": "/bg-rBG/user/onboarding.html#first-launch" - },"4133": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html#permissions", - - "relUrl": "/bg-rBG/user/onboarding.html#permissions" - },"4134": { - "doc": "Първи стъпки", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html#after-setup", - - "relUrl": "/bg-rBG/user/onboarding.html#after-setup" - },"4135": { - "doc": "Първи стъпки", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/bg-rBG/user/onboarding.html#whats-next" - },"4136": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html", - - "relUrl": "/sl-rSI/user/onboarding.html" - },"4137": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html#first-launch", - - "relUrl": "/sl-rSI/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html#permissions", - - "relUrl": "/sl-rSI/user/onboarding.html#permissions" - },"4139": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html#after-setup", - - "relUrl": "/sl-rSI/user/onboarding.html#after-setup" - },"4140": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/sl-rSI/user/onboarding.html#whats-next" - },"4141": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html", - - "relUrl": "/pt-rPT/user/onboarding.html" - },"4142": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html#first-launch", - - "relUrl": "/pt-rPT/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html#permissions", - - "relUrl": "/pt-rPT/user/onboarding.html#permissions" - },"4144": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html#after-setup", - - "relUrl": "/pt-rPT/user/onboarding.html#after-setup" - },"4145": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/pt-rPT/user/onboarding.html#whats-next" - },"4146": { + "relUrl": "/ca-rES/user/onboarding.html#whats-next" + },"4051": { "doc": "Начало работы", "title": "Начало работы", "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", "url": "/Meshtastic-Android/main/be-rBY/user/onboarding.html", "relUrl": "/be-rBY/user/onboarding.html" - },"4147": { + },"4052": { "doc": "Начало работы", "title": "First Launch", "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", "url": "/Meshtastic-Android/main/be-rBY/user/onboarding.html#first-launch", "relUrl": "/be-rBY/user/onboarding.html#first-launch" - },"4148": { + },"4053": { "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", "url": "/Meshtastic-Android/main/be-rBY/user/onboarding.html#permissions", "relUrl": "/be-rBY/user/onboarding.html#permissions" - },"4149": { + },"4054": { "doc": "Начало работы", "title": "After Setup", "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", "url": "/Meshtastic-Android/main/be-rBY/user/onboarding.html#after-setup", "relUrl": "/be-rBY/user/onboarding.html#after-setup" - },"4150": { + },"4055": { "doc": "Начало работы", "title": "What’s Next?", "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", "relUrl": "/be-rBY/user/onboarding.html#whats-next" - },"4151": { + },"4056": { "doc": "Getting Started", "title": "Getting Started", "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html", + "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html", - "relUrl": "/pt-rBR/user/onboarding.html" - },"4152": { + "relUrl": "/uk-rUA/user/onboarding.html" + },"4057": { "doc": "Getting Started", "title": "First Launch", "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html#first-launch", + "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#first-launch", - "relUrl": "/pt-rBR/user/onboarding.html#first-launch" - },"4153": { + "relUrl": "/uk-rUA/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html#permissions", + "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#permissions", - "relUrl": "/pt-rBR/user/onboarding.html#permissions" - },"4154": { + "relUrl": "/uk-rUA/user/onboarding.html#permissions" + },"4059": { "doc": "Getting Started", "title": "After Setup", "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html#after-setup", + "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#after-setup", - "relUrl": "/pt-rBR/user/onboarding.html#after-setup" - },"4155": { + "relUrl": "/uk-rUA/user/onboarding.html#after-setup" + },"4060": { "doc": "Getting Started", "title": "What’s Next?", "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#whats-next", - "relUrl": "/pt-rBR/user/onboarding.html#whats-next" - },"4156": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html", - - "relUrl": "/el-rGR/user/onboarding.html" - },"4157": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html#first-launch", - - "relUrl": "/el-rGR/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html#permissions", - - "relUrl": "/el-rGR/user/onboarding.html#permissions" - },"4159": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html#after-setup", - - "relUrl": "/el-rGR/user/onboarding.html#after-setup" - },"4160": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/el-rGR/user/onboarding.html#whats-next" - },"4161": { - "doc": "Primeros Pasos", - "title": "Primeros Pasos", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html", - - "relUrl": "/es-rES/user/onboarding.html" - },"4162": { - "doc": "Primeros Pasos", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html#first-launch", - - "relUrl": "/es-rES/user/onboarding.html#first-launch" - },"4163": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html#permissions", - - "relUrl": "/es-rES/user/onboarding.html#permissions" - },"4164": { - "doc": "Primeros Pasos", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html#after-setup", - - "relUrl": "/es-rES/user/onboarding.html#after-setup" - },"4165": { - "doc": "Primeros Pasos", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/es-rES/user/onboarding.html#whats-next" - },"4166": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html", - - "relUrl": "/tr-rTR/user/onboarding.html" - },"4167": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html#first-launch", - - "relUrl": "/tr-rTR/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html#permissions", - - "relUrl": "/tr-rTR/user/onboarding.html#permissions" - },"4169": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html#after-setup", - - "relUrl": "/tr-rTR/user/onboarding.html#after-setup" - },"4170": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/tr-rTR/user/onboarding.html#whats-next" - },"4171": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html", - - "relUrl": "/no-rNO/user/onboarding.html" - },"4172": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html#first-launch", - - "relUrl": "/no-rNO/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html#permissions", - - "relUrl": "/no-rNO/user/onboarding.html#permissions" - },"4174": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html#after-setup", - - "relUrl": "/no-rNO/user/onboarding.html#after-setup" - },"4175": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/no-rNO/user/onboarding.html#whats-next" - },"4176": { - "doc": "Начало работы", - "title": "Начало работы", - "content": "Добро пожаловать в Meshtastic! Это руководство проведет тебя через начальную настройку приложения Meshtastic для Android. ", - "url": "/Meshtastic-Android/main/ru-rRU/user/onboarding.html", - - "relUrl": "/ru-rRU/user/onboarding.html" - },"4177": { - "doc": "Начало работы", - "title": "Первый запуск", - "content": "Когда ты запускаешь приложение впервые, то будет предложено пройти через начальный процесс, который поможет настроить основные разрешения и параметры. Каждый шаг нужно выполнить по порядку, или же можешь пропустить его и настроить разрешения позже в настройках Android. Экран приветствия . Экран приветствия представляет Meshtastic и его основные возможности: . | Автономная mesh-связь | Не требуется мобильная связь или интернет | Сквозное шифрование сообщений | . Нажми Начать для перехода к настройке. ", - "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#первый-запуск" - },"4178": { - "doc": "Начало работы", - "title": "Разрешения", - "content": "Приложение запрашивает несколько разрешений во время настройки. Каждое из них служит определенной цели, и некоторые необходимы для основной функциональности. Разрешения Bluetooth . Bluetooth является основным методом соединения между телефоном и радиостанцией Meshtastic: . | Сканирование Bluetooth — обнаружение ближайших радиостанций Meshtastic | Подключение по Bluetooth — установка и поддержание соединения с сопряжёнными радиоустройствами | . Предоставь оба разрешения при запросе. Без Bluetooth тебе придется использовать USB или TCP соединения. Разрешение на доступ к местоположению . ⚠️ Почему для Bluetooth требуется местоположение? Android требует разрешение на определение местоположения для обнаружения устройств Bluetooth Low Energy поблизости. Это требование системы Android, а не специфический выбор Meshtastic. Meshtastic также использует местоположение для: . | Показ вашего положения на карте | Вычисление расстояний до других нод | Обмен GPS-координатами с другими участниками сети (если включено) | . Предоставь доступ “При использовании приложения” или “Всегда” в зависимости от своих предпочтений: . | При использовании приложения — обновление местоположения происходит только когда приложение открыто | Всегда — включает обновления позиции в фоновом режиме для активного присутствия в сети | . Если доступ будет запрещен, сканирование Bluetooth не будет работать, и нода не будет сообщать о положении. Разрешение на уведомления . Уведомления оповещают тебя о: . | Входящие сообщения из каналов и личных сообщений | Новые ноды, присоединившиеся к сети | Низкий заряд на удаленной ноде | . 💡 Совет: Ты можешь тонко настроить уведомления позже в настройках системы — приложение создает отдельный канал уведомлений по категориям (плюс несколько внутренних, как фоновая служба), поэтому ты можешь включить или заглушить их по отдельности. Разрешение на критические уведомления . На поддерживаемых устройствах приложение может запрашивать разрешение на критические уведомления: . | Это уведомления высокого приоритета, которые могут прерывать режим “Не беспокоить” | Полезно для экстренных уведомлений в mesh-сети или срочных сообщений | Вы можете пропустить этот шаг, если не нужны уведомления о прорывах | Настроить или отменить можно позже в настройках уведомлений 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#разрешения" - },"4179": { - "doc": "Начало работы", - "title": "После настройки", - "content": "Как только разрешения предоставлены, приложение переходит к основному интерфейсу. Ваше первое действие должно заключаться в подключении к радиостанции Meshtastic — см. Подключения для подробных инструкций. 💡 Совет: Если ты пропустил какие-либо разрешения во время настройки, то можешь выдать их позже через Настройки Android → Приложения → Meshtastic → Разрешения. Приложение снова запросит у тебя разрешение, если отсутствующее разрешение блокирует функцию, которую ты пытаешься использовать. ", - "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#после-настройки" - },"4180": { - "doc": "Начало работы", - "title": "Что дальше?", - "content": "После подключения к радиостанции, исследуй: . | Подключения — соедини своё первое радиоустройство | Сообщения и каналы — отправь своё первое сообщение | Ноды — посмотри, кто есть в сети | Карта и контрольные точки — просмотр позиций нод | Настройки — настрой своё устройство и профиль пользователя | . Новичок в Meshtastic? Руководство по началу работы на meshtastic.org охватывает выбор оборудования, начальную настройку радиостанции и первую установку сети. ", - "url": "/Meshtastic-Android/main/ru-rRU/user/onboarding.html#%D1%87%D1%82%D0%BE-%D0%B4%D0%B0%D0%BB%D1%8C%D1%88%D0%B5", - - "relUrl": "/ru-rRU/user/onboarding.html#что-дальше" - },"4181": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html", - - "relUrl": "/nl-rNL/user/onboarding.html" - },"4182": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html#first-launch", - - "relUrl": "/nl-rNL/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html#permissions", - - "relUrl": "/nl-rNL/user/onboarding.html#permissions" - },"4184": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html#after-setup", - - "relUrl": "/nl-rNL/user/onboarding.html#after-setup" - },"4185": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/nl-rNL/user/onboarding.html#whats-next" - },"4186": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Tere tulemast Meshtasticusse! See juhend juhendab sind Meshtastic Androidi rakenduse esmasel seadistamisel. ", - "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html", - - "relUrl": "/et-rEE/user/onboarding.html" - },"4187": { - "doc": "Getting Started", - "title": "First Launch", - "content": "Rakenduse esmakordsel avamisel juhendatakse sind sissejuhatavas voos, mis aitab konfigureerida olulisi õigusi ja sätteid. Iga sammu saab läbida järjekorras või võid selle vahele jätta ja õigused hiljem Androidi seadetes konfigureerida. Tervituskuva . Tervituskuval tutvustatakse Meshtasticut ja selle põhifunktsioone: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Puuduta Alusta seadistusvoo jätkamiseks. ", - "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html#first-launch", - - "relUrl": "/et-rEE/user/onboarding.html#first-launch" - },"4188": { - "doc": "Getting Started", - "title": "Permissions", - "content": "Rakendus küsib seadistamise ajal mitmeid lube. Each one serves a specific purpose, and some are required for core functionality. Sinihamba load . Sinihammas on peamine ühendusmeetod sinu telefoni ja Meshtastic raadio vahel: . | Bluetoothi ​​skann – avasta lähedalasuvad Meshtastic raadiod | Sinihamba ühendus – loo ja halda seotud seadmete ühendusi | . Grant both permissions when prompted. Ilma sinihambata peate kasutama USB- või TCP-ühendusi. Asukoha luba . ⚠️ Miks on sinihamba ​​jaoks vaja asukohateavet? Android vajab lähedalasuvate sinihamba madala energia seadmete avastamiseks asukohale juurdepääsu luba. See on Androidi süsteeminõue, mitte Meshtastic põhine valik. Meshtastic kasutab sinu asukohta ka järgmiseks: . | Kuvatakse asukoht kärgvõrgu kaardil | Calculating distances to other nodes | GPS koordinaatide jagamine teiste võrgusilma liikmetega (kui lubatud) | . Grant “While using the app” or “Always” depending on your preference: . | Rakenduse kasutamise ajal – asukohta uuendatakse kui rakendus on avatud | Alati – lubab taustal asukoha värskendusi, et kärgvõrgu oleks alati sisse lülitatud | . Kui keelatud, siis sinihamba otsing ei toimi ja sõlm ei edasta asukohta. 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 . On supported devices, the app may request permission for critical alerts: . | Need on kõrge prioriteediga märguanded, mis võivad režiimist „Ära sega” läbi murda | Useful for emergency mesh alerts or urgent messages | Võid selle sammu vahele jätta, kui te kõrge prioriteediga märguandeid ei vaja | Seadistada või tühistada hiljem Androidi teavitusseadetes | . ", - "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html#permissions", - - "relUrl": "/et-rEE/user/onboarding.html#permissions" - },"4189": { - "doc": "Getting Started", - "title": "Peale seadistamist", - "content": "Kui load on antud, läheb rakendus üle põhiliidesele. Esimene samm peaks olema ühenduse loomine Meshtastic raadioga – üksikasjalike juhiste saamiseks vaata [Ühendused] (connections). 💡 Vihje: Kui jätsid seadistamise ajal mõne õiguse andmata, saad selle hiljem anda jaotises Androidi seaded → Rakendused → Meshtastic → Load. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html#peale-seadistamist", - - "relUrl": "/et-rEE/user/onboarding.html#peale-seadistamist" - },"4190": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Kui raadioga on ühendus loodud, uuri: . | [Ühendused(connections) — seo oma esimene raadioseade | Sõnumid ja kanalid — saada oma esimene sõnum | Seadmed — vaata, kes on sinu võrgus | Kaart ja teekonnapunktid — vaata sõlmede asukohti | Seaded — raadio ja kasutajaprofiili seadistamine | . 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#whats-next", - - "relUrl": "/et-rEE/user/onboarding.html#whats-next" - },"4191": { - "doc": "Come iniziare", - "title": "Come iniziare", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html", - - "relUrl": "/it-rIT/user/onboarding.html" - },"4192": { - "doc": "Come iniziare", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html#first-launch", - - "relUrl": "/it-rIT/user/onboarding.html#first-launch" - },"4193": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html#permissions", - - "relUrl": "/it-rIT/user/onboarding.html#permissions" - },"4194": { - "doc": "Come iniziare", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html#after-setup", - - "relUrl": "/it-rIT/user/onboarding.html#after-setup" - },"4195": { - "doc": "Come iniziare", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/it-rIT/user/onboarding.html#whats-next" - },"4196": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html", - - "relUrl": "/ar-rSA/user/onboarding.html" - },"4197": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html#first-launch", - - "relUrl": "/ar-rSA/user/onboarding.html#first-launch" - },"4198": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html#permissions", - - "relUrl": "/ar-rSA/user/onboarding.html#permissions" - },"4199": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html#after-setup", - - "relUrl": "/ar-rSA/user/onboarding.html#after-setup" - },"4200": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/ar-rSA/user/onboarding.html#whats-next" - },"4201": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html", - - "relUrl": "/sk-rSK/user/onboarding.html" - },"4202": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html#first-launch", - - "relUrl": "/sk-rSK/user/onboarding.html#first-launch" - },"4203": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html#permissions", - - "relUrl": "/sk-rSK/user/onboarding.html#permissions" - },"4204": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html#after-setup", - - "relUrl": "/sk-rSK/user/onboarding.html#after-setup" - },"4205": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/sk-rSK/user/onboarding.html#whats-next" - },"4206": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html", - - "relUrl": "/pl-rPL/user/onboarding.html" - },"4207": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html#first-launch", - - "relUrl": "/pl-rPL/user/onboarding.html#first-launch" - },"4208": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html#permissions", - - "relUrl": "/pl-rPL/user/onboarding.html#permissions" - },"4209": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html#after-setup", - - "relUrl": "/pl-rPL/user/onboarding.html#after-setup" - },"4210": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/pl-rPL/user/onboarding.html#whats-next" - },"4211": { - "doc": "新手入門", - "title": "# 入門指南", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "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#-入門指南" - },"4212": { - "doc": "新手入門", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#first-launch", - - "relUrl": "/zh-rTW/user/onboarding.html#first-launch" - },"4213": { - "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#permissions", - - "relUrl": "/zh-rTW/user/onboarding.html#permissions" - },"4214": { - "doc": "新手入門", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#after-setup", - - "relUrl": "/zh-rTW/user/onboarding.html#after-setup" - },"4215": { - "doc": "新手入門", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/zh-rTW/user/onboarding.html#whats-next" - },"4216": { - "doc": "新手入門", - "title": "新手入門", - "content": " ", - "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html", - - "relUrl": "/zh-rTW/user/onboarding.html" - },"4217": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html", - - "relUrl": "/cs-rCZ/user/onboarding.html" - },"4218": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html#first-launch", - - "relUrl": "/cs-rCZ/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html#permissions", - - "relUrl": "/cs-rCZ/user/onboarding.html#permissions" - },"4220": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html#after-setup", - - "relUrl": "/cs-rCZ/user/onboarding.html#after-setup" - },"4221": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/cs-rCZ/user/onboarding.html#whats-next" - },"4222": { - "doc": "Getting Started", - "title": "Getting Started", - "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html", - - "relUrl": "/fr-rFR/user/onboarding.html" - },"4223": { - "doc": "Getting Started", - "title": "First Launch", - "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html#first-launch", - - "relUrl": "/fr-rFR/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html#permissions", - - "relUrl": "/fr-rFR/user/onboarding.html#permissions" - },"4225": { - "doc": "Getting Started", - "title": "After Setup", - "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html#after-setup", - - "relUrl": "/fr-rFR/user/onboarding.html#after-setup" - },"4226": { - "doc": "Getting Started", - "title": "What’s Next?", - "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", - - "relUrl": "/fr-rFR/user/onboarding.html#whats-next" - },"4227": { + "relUrl": "/uk-rUA/user/onboarding.html#whats-next" + },"4061": { "doc": "Getting Started", "title": "Getting Started", "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", "url": "/Meshtastic-Android/main/zh-rCN/user/onboarding.html", "relUrl": "/zh-rCN/user/onboarding.html" - },"4228": { + },"4062": { "doc": "Getting Started", "title": "First Launch", "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", "url": "/Meshtastic-Android/main/zh-rCN/user/onboarding.html#first-launch", "relUrl": "/zh-rCN/user/onboarding.html#first-launch" - },"4229": { + },"4063": { "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", "url": "/Meshtastic-Android/main/zh-rCN/user/onboarding.html#permissions", "relUrl": "/zh-rCN/user/onboarding.html#permissions" - },"4230": { + },"4064": { "doc": "Getting Started", "title": "After Setup", "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", "url": "/Meshtastic-Android/main/zh-rCN/user/onboarding.html#after-setup", "relUrl": "/zh-rCN/user/onboarding.html#after-setup" - },"4231": { + },"4065": { "doc": "Getting Started", "title": "What’s Next?", "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", "relUrl": "/zh-rCN/user/onboarding.html#whats-next" - },"4232": { + },"4066": { + "doc": "Първи стъпки", + "title": "Първи стъпки", + "content": "Добре дошли в Meshtastic! Това ръководство ви превежда през първоначалната настройка на приложението Meshtastic за Android. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html", + + "relUrl": "/bg-rBG/user/onboarding.html" + },"4067": { + "doc": "Първи стъпки", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html#first-launch", + + "relUrl": "/bg-rBG/user/onboarding.html#first-launch" + },"4068": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html#permissions", + + "relUrl": "/bg-rBG/user/onboarding.html#permissions" + },"4069": { + "doc": "Първи стъпки", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html#after-setup", + + "relUrl": "/bg-rBG/user/onboarding.html#after-setup" + },"4070": { + "doc": "Първи стъпки", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/bg-rBG/user/onboarding.html#whats-next" + },"4071": { + "doc": "新手入門", + "title": "# 入門指南", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "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#-入門指南" + },"4072": { + "doc": "新手入門", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#first-launch", + + "relUrl": "/zh-rTW/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#permissions", + + "relUrl": "/zh-rTW/user/onboarding.html#permissions" + },"4074": { + "doc": "新手入門", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#after-setup", + + "relUrl": "/zh-rTW/user/onboarding.html#after-setup" + },"4075": { + "doc": "新手入門", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/zh-rTW/user/onboarding.html#whats-next" + },"4076": { + "doc": "新手入門", + "title": "新手入門", + "content": " ", + "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html", + + "relUrl": "/zh-rTW/user/onboarding.html" + },"4077": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html", + + "relUrl": "/sr-rLatn/user/onboarding.html" + },"4078": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html#first-launch", + + "relUrl": "/sr-rLatn/user/onboarding.html#first-launch" + },"4079": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html#permissions", + + "relUrl": "/sr-rLatn/user/onboarding.html#permissions" + },"4080": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html#after-setup", + + "relUrl": "/sr-rLatn/user/onboarding.html#after-setup" + },"4081": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/sr-rLatn/user/onboarding.html#whats-next" + },"4082": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html", + + "relUrl": "/cs-rCZ/user/onboarding.html" + },"4083": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html#first-launch", + + "relUrl": "/cs-rCZ/user/onboarding.html#first-launch" + },"4084": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html#permissions", + + "relUrl": "/cs-rCZ/user/onboarding.html#permissions" + },"4085": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html#after-setup", + + "relUrl": "/cs-rCZ/user/onboarding.html#after-setup" + },"4086": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/cs-rCZ/user/onboarding.html#whats-next" + },"4087": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/en/user/onboarding.html", + + "relUrl": "/en/user/onboarding.html" + },"4088": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/en/user/onboarding.html#first-launch", + + "relUrl": "/en/user/onboarding.html#first-launch" + },"4089": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/en/user/onboarding.html#permissions", + + "relUrl": "/en/user/onboarding.html#permissions" + },"4090": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/en/user/onboarding.html#after-setup", + + "relUrl": "/en/user/onboarding.html#after-setup" + },"4091": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/en/user/onboarding.html#whats-next" + },"4092": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html", + + "relUrl": "/sl-rSI/user/onboarding.html" + },"4093": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html#first-launch", + + "relUrl": "/sl-rSI/user/onboarding.html#first-launch" + },"4094": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html#permissions", + + "relUrl": "/sl-rSI/user/onboarding.html#permissions" + },"4095": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html#after-setup", + + "relUrl": "/sl-rSI/user/onboarding.html#after-setup" + },"4096": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/sl-rSI/user/onboarding.html#whats-next" + },"4097": { + "doc": "Come iniziare", + "title": "Come iniziare", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html", + + "relUrl": "/it-rIT/user/onboarding.html" + },"4098": { + "doc": "Come iniziare", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html#first-launch", + + "relUrl": "/it-rIT/user/onboarding.html#first-launch" + },"4099": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html#permissions", + + "relUrl": "/it-rIT/user/onboarding.html#permissions" + },"4100": { + "doc": "Come iniziare", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html#after-setup", + + "relUrl": "/it-rIT/user/onboarding.html#after-setup" + },"4101": { + "doc": "Come iniziare", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/it-rIT/user/onboarding.html#whats-next" + },"4102": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html", + + "relUrl": "/pt-rBR/user/onboarding.html" + },"4103": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html#first-launch", + + "relUrl": "/pt-rBR/user/onboarding.html#first-launch" + },"4104": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html#permissions", + + "relUrl": "/pt-rBR/user/onboarding.html#permissions" + },"4105": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html#after-setup", + + "relUrl": "/pt-rBR/user/onboarding.html#after-setup" + },"4106": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/pt-rBR/user/onboarding.html#whats-next" + },"4107": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html", + + "relUrl": "/is-rIS/user/onboarding.html" + },"4108": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html#first-launch", + + "relUrl": "/is-rIS/user/onboarding.html#first-launch" + },"4109": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html#permissions", + + "relUrl": "/is-rIS/user/onboarding.html#permissions" + },"4110": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html#after-setup", + + "relUrl": "/is-rIS/user/onboarding.html#after-setup" + },"4111": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/is-rIS/user/onboarding.html#whats-next" + },"4112": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html", + + "relUrl": "/fr-rFR/user/onboarding.html" + },"4113": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html#first-launch", + + "relUrl": "/fr-rFR/user/onboarding.html#first-launch" + },"4114": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html#permissions", + + "relUrl": "/fr-rFR/user/onboarding.html#permissions" + },"4115": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html#after-setup", + + "relUrl": "/fr-rFR/user/onboarding.html#after-setup" + },"4116": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/fr-rFR/user/onboarding.html#whats-next" + },"4117": { "doc": "Getting Started", "title": "Getting Started", "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", "url": "/Meshtastic-Android/main/srp/user/onboarding.html", "relUrl": "/srp/user/onboarding.html" - },"4233": { + },"4118": { "doc": "Getting Started", "title": "First Launch", "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", "url": "/Meshtastic-Android/main/srp/user/onboarding.html#first-launch", "relUrl": "/srp/user/onboarding.html#first-launch" - },"4234": { + },"4119": { "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", "url": "/Meshtastic-Android/main/srp/user/onboarding.html#permissions", "relUrl": "/srp/user/onboarding.html#permissions" - },"4235": { + },"4120": { "doc": "Getting Started", "title": "After Setup", "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", "url": "/Meshtastic-Android/main/srp/user/onboarding.html#after-setup", "relUrl": "/srp/user/onboarding.html#after-setup" - },"4236": { + },"4121": { "doc": "Getting Started", "title": "What’s Next?", "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", "relUrl": "/srp/user/onboarding.html#whats-next" - },"4237": { + },"4122": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html", + + "relUrl": "/sk-rSK/user/onboarding.html" + },"4123": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html#first-launch", + + "relUrl": "/sk-rSK/user/onboarding.html#first-launch" + },"4124": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html#permissions", + + "relUrl": "/sk-rSK/user/onboarding.html#permissions" + },"4125": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html#after-setup", + + "relUrl": "/sk-rSK/user/onboarding.html#after-setup" + },"4126": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/sk-rSK/user/onboarding.html#whats-next" + },"4127": { + "doc": "Aloittaminen", + "title": "Aloittaminen", + "content": "Tervetuloa Meshtasticiin! Tämä opas opastaa sinut Meshtastic Android -sovelluksen alkuasetusten läpi. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/onboarding.html", + + "relUrl": "/fi-rFI/user/onboarding.html" + },"4128": { + "doc": "Aloittaminen", + "title": "Ensimmäinen käynnistys", + "content": "Kun avaat sovelluksen ensimmäistä kertaa, sinut ohjataan käyttöönottoprosessin läpi, joka auttaa määrittämään tarvittavat käyttöoikeudet ja asetukset. Voit suorittaa jokaisen vaiheen järjestyksessä tai ohittaa ne ja määrittää käyttöoikeudet myöhemmin Androidin asetuksissa. Aloitusnäkymä . Tervetulonäyttö esittelee Meshtasticin ja sen tärkeimmät ominaisuudet: . | Matkapuhelinverkosta riippumaton mesh-viestintä | Ei vaadi matkapuhelinverkkoa tai internetyhteyttä | Päästä päähän salattu viestintä | . Napauta “Aloita” jatkaaksesi käyttöönottoprosessia. ", + "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" + },"4129": { + "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 on ensisijainen yhteystapa puhelimesi ja Meshtastic-radion välillä: . | Bluetooth-skannaus — etsi lähellä olevia Meshtastic-radioita | Bluetooth-yhteys — muodosta ja ylläpidä yhteyksiä pariliitettyihin radioihin | . Myönnä molemmat käyttöoikeudet pyydettäessä. Ilman Bluetoothia sinun on käytettävä sen sijaan USB- tai TCP-yhteyksiä. Sijaintikäyttöoikeus . ⚠️ Miksi sijaintikäyttöoikeus tarvitaan Bluetoothille? Android vaatii sijaintikäyttöoikeuden lähellä olevien Bluetooth Low Energy -laitteiden löytämiseen. Tämä on Android-järjestelmän vaatimus, eikä Meshtasticin erityinen valinta. 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” tai “Aina” oman mieltymyksesi mukaan: . | Sovelluksen käytön aikana — sijainti päivittyy vain silloin, kun sovellus on avoinna | Aina — mahdollistaa sijainnin päivittämisen taustalla jatkuvaa verkon läsnäoloa varten | . Jos käyttöoikeus evätään, Bluetooth-skannaus ei toimi eikä radiosi raportoi sijaintia. 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 . Tuetuilla laitteilla sovellus voi pyytää käyttöoikeutta kriittisiin hälytyksiin: . | Nämä ovat korkean prioriteetin ilmoituksia, jotka voivat ohittaa Älä häiritse -tilan | Hyödyllinen hätätilanteiden verkkohälytyksille tai kiireellisille viesteille | Voit ohittaa tämän vaiheen, jos et tarvitse ilmoituksia, jotka ohittavat Älä häiritse -tilan | Voit määrittää tai peruuttaa tämän myöhemmin Androidin ilmoitusasetuksissa | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/onboarding.html#k%C3%A4ytt%C3%B6oikeudet", + + "relUrl": "/fi-rFI/user/onboarding.html#käyttöoikeudet" + },"4130": { + "doc": "Aloittaminen", + "title": "Määrityksen jälkeen", + "content": "Kun käyttöoikeudet on myönnetty, sovellus siirtyy pääkäyttöliittymään. Ensimmäinen toimenpiteesi pitäisi olla yhteyden muodostaminen Meshtastic-radioon — katso Yhteydet yksityiskohtaisia ohjeita varten. 💡 Vinkki: Jos ohitit käyttöoikeuksia määrityksen aikana, voit myöntää ne myöhemmin kohdassa Androidin asetukset → Sovellukset → Meshtastic → Käyttöoikeudet. Sovellus pyytää sinulta uudelleen käyttöoikeutta, jos puuttuva käyttöoikeus estää käyttämästä ominaisuutta, jota yrität käyttää. ", + "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" + },"4131": { + "doc": "Aloittaminen", + "title": "Mitä seuraavaksi?", + "content": "Kun olet muodostanut yhteyden radioon, tutustu seuraaviin: . | Yhteydet — yhdistä ensimmäinen radiolaitteesi | Viestit ja kanavat — lähetä ensimmäinen viestisi | Radiot — katso, ketkä ovat verkossasi | Kartta ja reittipisteet — tarkastele radioiden sijainteja | Asetukset — määritä radiosi ja käyttäjäprofiilisi | . 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#mit%C3%A4-seuraavaksi", + + "relUrl": "/fi-rFI/user/onboarding.html#mitä-seuraavaksi" + },"4132": { + "doc": "Начало работы", + "title": "Начало работы", + "content": "Добро пожаловать в Meshtastic! Это руководство проведет тебя через начальную настройку приложения Meshtastic для Android. ", + "url": "/Meshtastic-Android/main/ru-rRU/user/onboarding.html", + + "relUrl": "/ru-rRU/user/onboarding.html" + },"4133": { + "doc": "Начало работы", + "title": "Первый запуск", + "content": "Когда ты запускаешь приложение впервые, то будет предложено пройти через начальный процесс, который поможет настроить основные разрешения и параметры. Каждый шаг нужно выполнить по порядку, или же можешь пропустить его и настроить разрешения позже в настройках Android. Экран приветствия . Экран приветствия представляет Meshtastic и его основные возможности: . | Автономная mesh-связь | Не требуется мобильная связь или интернет | Сквозное шифрование сообщений | . Нажми Начать для перехода к настройке. ", + "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#первый-запуск" + },"4134": { + "doc": "Начало работы", + "title": "Разрешения", + "content": "Приложение запрашивает несколько разрешений во время настройки. Каждое из них служит определенной цели, и некоторые необходимы для основной функциональности. Разрешения Bluetooth . Bluetooth является основным методом соединения между телефоном и радиостанцией Meshtastic: . | Сканирование Bluetooth — обнаружение ближайших радиостанций Meshtastic | Подключение по Bluetooth — установка и поддержание соединения с сопряжёнными радиоустройствами | . Предоставь оба разрешения при запросе. Без Bluetooth тебе придется использовать USB или TCP соединения. Разрешение на доступ к местоположению . ⚠️ Почему для Bluetooth требуется местоположение? Android требует разрешение на определение местоположения для обнаружения устройств Bluetooth Low Energy поблизости. Это требование системы Android, а не специфический выбор Meshtastic. Meshtastic также использует местоположение для: . | Показ вашего положения на карте | Вычисление расстояний до других нод | Обмен GPS-координатами с другими участниками сети (если включено) | . Предоставь доступ “При использовании приложения” или “Всегда” в зависимости от своих предпочтений: . | При использовании приложения — обновление местоположения происходит только когда приложение открыто | Всегда — включает обновления позиции в фоновом режиме для активного присутствия в сети | . Если доступ будет запрещен, сканирование Bluetooth не будет работать, и нода не будет сообщать о положении. Разрешение на уведомления . Уведомления оповещают тебя о: . | Входящие сообщения из каналов и личных сообщений | Новые ноды, присоединившиеся к сети | Низкий заряд на удаленной ноде | . 💡 Совет: Ты можешь тонко настроить уведомления позже в настройках системы — приложение создает отдельный канал уведомлений по категориям (плюс несколько внутренних, как фоновая служба), поэтому ты можешь включить или заглушить их по отдельности. Разрешение на критические уведомления . На поддерживаемых устройствах приложение может запрашивать разрешение на критические уведомления: . | Это уведомления высокого приоритета, которые могут прерывать режим “Не беспокоить” | Полезно для экстренных уведомлений в mesh-сети или срочных сообщений | Вы можете пропустить этот шаг, если не нужны уведомления о прорывах | Настроить или отменить можно позже в настройках уведомлений 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#разрешения" + },"4135": { + "doc": "Начало работы", + "title": "После настройки", + "content": "Как только разрешения предоставлены, приложение переходит к основному интерфейсу. Ваше первое действие должно заключаться в подключении к радиостанции Meshtastic — см. Подключения для подробных инструкций. 💡 Совет: Если ты пропустил какие-либо разрешения во время настройки, то можешь выдать их позже через Настройки Android → Приложения → Meshtastic → Разрешения. Приложение снова запросит у тебя разрешение, если отсутствующее разрешение блокирует функцию, которую ты пытаешься использовать. ", + "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#после-настройки" + },"4136": { + "doc": "Начало работы", + "title": "Что дальше?", + "content": "После подключения к радиостанции, исследуй: . | Подключения — соедини своё первое радиоустройство | Сообщения и каналы — отправь своё первое сообщение | Ноды — посмотри, кто есть в сети | Карта и контрольные точки — просмотр позиций нод | Настройки — настрой своё устройство и профиль пользователя | . Новичок в Meshtastic? Руководство по началу работы на meshtastic.org охватывает выбор оборудования, начальную настройку радиостанции и первую установку сети. ", + "url": "/Meshtastic-Android/main/ru-rRU/user/onboarding.html#%D1%87%D1%82%D0%BE-%D0%B4%D0%B0%D0%BB%D1%8C%D1%88%D0%B5", + + "relUrl": "/ru-rRU/user/onboarding.html#что-дальше" + },"4137": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html", + + "relUrl": "/ko-rKR/user/onboarding.html" + },"4138": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html#first-launch", + + "relUrl": "/ko-rKR/user/onboarding.html#first-launch" + },"4139": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html#permissions", + + "relUrl": "/ko-rKR/user/onboarding.html#permissions" + },"4140": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html#after-setup", + + "relUrl": "/ko-rKR/user/onboarding.html#after-setup" + },"4141": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/ko-rKR/user/onboarding.html#whats-next" + },"4142": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html", + + "relUrl": "/hr-rHR/user/onboarding.html" + },"4143": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html#first-launch", + + "relUrl": "/hr-rHR/user/onboarding.html#first-launch" + },"4144": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html#permissions", + + "relUrl": "/hr-rHR/user/onboarding.html#permissions" + },"4145": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html#after-setup", + + "relUrl": "/hr-rHR/user/onboarding.html#after-setup" + },"4146": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/hr-rHR/user/onboarding.html#whats-next" + },"4147": { "doc": "Getting Started", "title": "Getting Started", "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", "url": "/Meshtastic-Android/main/sq-rAL/user/onboarding.html", "relUrl": "/sq-rAL/user/onboarding.html" - },"4238": { + },"4148": { "doc": "Getting Started", "title": "First Launch", "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", "url": "/Meshtastic-Android/main/sq-rAL/user/onboarding.html#first-launch", "relUrl": "/sq-rAL/user/onboarding.html#first-launch" - },"4239": { + },"4149": { "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", "url": "/Meshtastic-Android/main/sq-rAL/user/onboarding.html#permissions", "relUrl": "/sq-rAL/user/onboarding.html#permissions" - },"4240": { + },"4150": { "doc": "Getting Started", "title": "After Setup", "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", "url": "/Meshtastic-Android/main/sq-rAL/user/onboarding.html#after-setup", "relUrl": "/sq-rAL/user/onboarding.html#after-setup" - },"4241": { + },"4151": { "doc": "Getting Started", "title": "What’s Next?", "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", "relUrl": "/sq-rAL/user/onboarding.html#whats-next" + },"4152": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html", + + "relUrl": "/no-rNO/user/onboarding.html" + },"4153": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html#first-launch", + + "relUrl": "/no-rNO/user/onboarding.html#first-launch" + },"4154": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html#permissions", + + "relUrl": "/no-rNO/user/onboarding.html#permissions" + },"4155": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html#after-setup", + + "relUrl": "/no-rNO/user/onboarding.html#after-setup" + },"4156": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/no-rNO/user/onboarding.html#whats-next" + },"4157": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html", + + "relUrl": "/lt-rLT/user/onboarding.html" + },"4158": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html#first-launch", + + "relUrl": "/lt-rLT/user/onboarding.html#first-launch" + },"4159": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html#permissions", + + "relUrl": "/lt-rLT/user/onboarding.html#permissions" + },"4160": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html#after-setup", + + "relUrl": "/lt-rLT/user/onboarding.html#after-setup" + },"4161": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/lt-rLT/user/onboarding.html#whats-next" + },"4162": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html", + + "relUrl": "/ar-rSA/user/onboarding.html" + },"4163": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html#first-launch", + + "relUrl": "/ar-rSA/user/onboarding.html#first-launch" + },"4164": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html#permissions", + + "relUrl": "/ar-rSA/user/onboarding.html#permissions" + },"4165": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html#after-setup", + + "relUrl": "/ar-rSA/user/onboarding.html#after-setup" + },"4166": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/ar-rSA/user/onboarding.html#whats-next" + },"4167": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html", + + "relUrl": "/pt-rPT/user/onboarding.html" + },"4168": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html#first-launch", + + "relUrl": "/pt-rPT/user/onboarding.html#first-launch" + },"4169": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html#permissions", + + "relUrl": "/pt-rPT/user/onboarding.html#permissions" + },"4170": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html#after-setup", + + "relUrl": "/pt-rPT/user/onboarding.html#after-setup" + },"4171": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/pt-rPT/user/onboarding.html#whats-next" + },"4172": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html", + + "relUrl": "/iw-rIL/user/onboarding.html" + },"4173": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html#first-launch", + + "relUrl": "/iw-rIL/user/onboarding.html#first-launch" + },"4174": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html#permissions", + + "relUrl": "/iw-rIL/user/onboarding.html#permissions" + },"4175": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html#after-setup", + + "relUrl": "/iw-rIL/user/onboarding.html#after-setup" + },"4176": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/iw-rIL/user/onboarding.html#whats-next" + },"4177": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html", + + "relUrl": "/el-rGR/user/onboarding.html" + },"4178": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html#first-launch", + + "relUrl": "/el-rGR/user/onboarding.html#first-launch" + },"4179": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html#permissions", + + "relUrl": "/el-rGR/user/onboarding.html#permissions" + },"4180": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html#after-setup", + + "relUrl": "/el-rGR/user/onboarding.html#after-setup" + },"4181": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/el-rGR/user/onboarding.html#whats-next" + },"4182": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html", + + "relUrl": "/ro-rRO/user/onboarding.html" + },"4183": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html#first-launch", + + "relUrl": "/ro-rRO/user/onboarding.html#first-launch" + },"4184": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html#permissions", + + "relUrl": "/ro-rRO/user/onboarding.html#permissions" + },"4185": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html#after-setup", + + "relUrl": "/ro-rRO/user/onboarding.html#after-setup" + },"4186": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/ro-rRO/user/onboarding.html#whats-next" + },"4187": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Tere tulemast Meshtasticusse! See juhend juhendab sind Meshtastic Androidi rakenduse esmasel seadistamisel. ", + "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html", + + "relUrl": "/et-rEE/user/onboarding.html" + },"4188": { + "doc": "Getting Started", + "title": "First Launch", + "content": "Rakenduse esmakordsel avamisel juhendatakse sind sissejuhatavas voos, mis aitab konfigureerida olulisi õigusi ja sätteid. Iga sammu saab läbida järjekorras või võid selle vahele jätta ja õigused hiljem Androidi seadetes konfigureerida. Tervituskuva . Tervituskuval tutvustatakse Meshtasticut ja selle põhifunktsioone: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Puuduta Alusta seadistusvoo jätkamiseks. ", + "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html#first-launch", + + "relUrl": "/et-rEE/user/onboarding.html#first-launch" + },"4189": { + "doc": "Getting Started", + "title": "Permissions", + "content": "Rakendus küsib seadistamise ajal mitmeid lube. Each one serves a specific purpose, and some are required for core functionality. Sinihamba load . Sinihammas on peamine ühendusmeetod sinu telefoni ja Meshtastic raadio vahel: . | Bluetoothi ​​skann – avasta lähedalasuvad Meshtastic raadiod | Sinihamba ühendus – loo ja halda seotud seadmete ühendusi | . Grant both permissions when prompted. Ilma sinihambata peate kasutama USB- või TCP-ühendusi. Asukoha luba . ⚠️ Miks on sinihamba ​​jaoks vaja asukohateavet? Android vajab lähedalasuvate sinihamba madala energia seadmete avastamiseks asukohale juurdepääsu luba. See on Androidi süsteeminõue, mitte Meshtastic põhine valik. Meshtastic kasutab sinu asukohta ka järgmiseks: . | Kuvatakse asukoht kärgvõrgu kaardil | Calculating distances to other nodes | GPS koordinaatide jagamine teiste võrgusilma liikmetega (kui lubatud) | . Grant “While using the app” or “Always” depending on your preference: . | Rakenduse kasutamise ajal – asukohta uuendatakse kui rakendus on avatud | Alati – lubab taustal asukoha värskendusi, et kärgvõrgu oleks alati sisse lülitatud | . Kui keelatud, siis sinihamba otsing ei toimi ja sõlm ei edasta asukohta. 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 . On supported devices, the app may request permission for critical alerts: . | Need on kõrge prioriteediga märguanded, mis võivad režiimist „Ära sega” läbi murda | Useful for emergency mesh alerts or urgent messages | Võid selle sammu vahele jätta, kui te kõrge prioriteediga märguandeid ei vaja | Seadistada või tühistada hiljem Androidi teavitusseadetes | . ", + "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html#permissions", + + "relUrl": "/et-rEE/user/onboarding.html#permissions" + },"4190": { + "doc": "Getting Started", + "title": "Peale seadistamist", + "content": "Kui load on antud, läheb rakendus üle põhiliidesele. Esimene samm peaks olema ühenduse loomine Meshtastic raadioga – üksikasjalike juhiste saamiseks vaata [Ühendused] (connections). 💡 Vihje: Kui jätsid seadistamise ajal mõne õiguse andmata, saad selle hiljem anda jaotises Androidi seaded → Rakendused → Meshtastic → Load. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html#peale-seadistamist", + + "relUrl": "/et-rEE/user/onboarding.html#peale-seadistamist" + },"4191": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Kui raadioga on ühendus loodud, uuri: . | [Ühendused(connections) — seo oma esimene raadioseade | Sõnumid ja kanalid — saada oma esimene sõnum | Seadmed — vaata, kes on sinu võrgus | Kaart ja teekonnapunktid — vaata sõlmede asukohti | Seaded — raadio ja kasutajaprofiili seadistamine | . 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#whats-next", + + "relUrl": "/et-rEE/user/onboarding.html#whats-next" + },"4192": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html", + + "relUrl": "/ga-rIE/user/onboarding.html" + },"4193": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html#first-launch", + + "relUrl": "/ga-rIE/user/onboarding.html#first-launch" + },"4194": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html#permissions", + + "relUrl": "/ga-rIE/user/onboarding.html#permissions" + },"4195": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html#after-setup", + + "relUrl": "/ga-rIE/user/onboarding.html#after-setup" + },"4196": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/ga-rIE/user/onboarding.html#whats-next" + },"4197": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html", + + "relUrl": "/pl-rPL/user/onboarding.html" + },"4198": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html#first-launch", + + "relUrl": "/pl-rPL/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html#permissions", + + "relUrl": "/pl-rPL/user/onboarding.html#permissions" + },"4200": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html#after-setup", + + "relUrl": "/pl-rPL/user/onboarding.html#after-setup" + },"4201": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/pl-rPL/user/onboarding.html#whats-next" + },"4202": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html", + + "relUrl": "/nl-rNL/user/onboarding.html" + },"4203": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html#first-launch", + + "relUrl": "/nl-rNL/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html#permissions", + + "relUrl": "/nl-rNL/user/onboarding.html#permissions" + },"4205": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html#after-setup", + + "relUrl": "/nl-rNL/user/onboarding.html#after-setup" + },"4206": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/nl-rNL/user/onboarding.html#whats-next" + },"4207": { + "doc": "Kom igång", + "title": "Kom igång", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html", + + "relUrl": "/sv-rSE/user/onboarding.html" + },"4208": { + "doc": "Kom igång", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html#first-launch", + + "relUrl": "/sv-rSE/user/onboarding.html#first-launch" + },"4209": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html#permissions", + + "relUrl": "/sv-rSE/user/onboarding.html#permissions" + },"4210": { + "doc": "Kom igång", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html#after-setup", + + "relUrl": "/sv-rSE/user/onboarding.html#after-setup" + },"4211": { + "doc": "Kom igång", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/sv-rSE/user/onboarding.html#whats-next" + },"4212": { + "doc": "はじめに", + "title": "はじめに", + "content": "Meshtastic へようこそ！ このガイドでは、Meshtastic Android アプリの初期設定を順を追って説明します。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html", + + "relUrl": "/ja-rJP/user/onboarding.html" + },"4213": { + "doc": "はじめに", + "title": "初回起動", + "content": "アプリを初めて開くと、必要な権限と設定を構成するための導入フローが案内されます。 各ステップは順番に完了することも、スキップして後で Android の設定で権限を構成することもできます。 . ようこそ画面 . ようこそ画面では、Meshtastic とその主な機能を紹介します： . | オフグリッドのメッシュ通信 | 携帯電話やインターネットは不要 | エンドツーエンドで暗号化されたメッセージング | . 開始するをタップして、セットアップフローを進めます。 . ", + "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#初回起動" + },"4214": { + "doc": "はじめに", + "title": "権限", + "content": "アプリはセットアップ中にいくつかの権限を要求します。 それぞれに特定の目的があり、一部は主要な機能に必要です。 . Bluetooth の権限 . Bluetooth は、スマートフォンと Meshtastic 無線機の主な接続方法です： . | Bluetooth スキャン：近くの Meshtastic 無線機を検出します | Bluetooth 接続：ペアリング済みの無線機との接続を確立して維持します | . プロンプトが表示されたら、両方の権限を許可してください。 Bluetooth がない場合は、代わりに USB または TCP 接続を使用する必要があります。 . 位置情報の権限 . ⚠️ なぜ Bluetooth に位置情報が必要なのですか？ Android では、近くの Bluetooth Low Energy デバイスを検出するために位置情報の権限が必要です。 これは Android システムの要件であり、Meshtastic 固有の仕様ではありません。 . Meshtastic は、次の目的でも位置情報を使用します： . | メッシュマップ上に自分の位置を表示する | 他のノードまでの距離を計算する | 他のメッシュメンバーと GPS 座標を共有する（有効な場合） | . お好みに応じて、**「アプリの使用中のみ」または「常に許可」**を選択してください： . | アプリの使用中のみ：アプリが開いているときだけ位置情報を更新します | 常に許可：常時メッシュに存在するために、バックグラウンドでの位置情報更新を有効にします | . 拒否すると、Bluetooth スキャンが機能せず、ノードは位置情報を報告しません。 . 通知の権限 . 通知は、次のことをお知らせします： . | チャンネルおよびダイレクトメッセージの受信 | メッシュに参加する新しいノード | リモートノードのバッテリー低下 | . 💡 ヒント： 通知の設定は、後で Android のシステム設定で細かく調整できます。アプリはカテゴリごとに個別の通知チャンネルを作成する（さらに、バックグラウンドサービスなどの内部用のものもいくつか作成する）ため、個別に有効化したり消音したりできます。 . 重要なアラートの権限 . 対応デバイスでは、アプリが重要なアラートの権限を要求することがあります： . | これらは、サイレントモードを突破できる高優先度の通知です | 緊急のメッシュアラートや至急のメッセージに役立ちます | 突破通知が不要な場合は、このステップをスキップできます | 後で Android の通知設定で構成または取り消しができます | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html#%E6%A8%A9%E9%99%90", + + "relUrl": "/ja-rJP/user/onboarding.html#権限" + },"4215": { + "doc": "はじめに", + "title": "セットアップ後", + "content": "権限を許可すると、アプリはメイン画面に移行します。 最初に行うべきことは、Meshtastic 無線機への接続です。詳しい手順は接続を参照してください。 . 💡 ヒント： セットアップ中に権限をスキップした場合は、後で**「Android 設定 → アプリ → Meshtastic → 権限」**から許可できます。 不足している権限が、使おうとする機能を妨げる場合は、アプリが再度確認を求めます。 . ", + "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#セットアップ後" + },"4216": { + "doc": "はじめに", + "title": "次のステップ", + "content": "無線機に接続したら、次を確認してみましょう： . | 接続：最初の無線機デバイスをペアリングする | メッセージとチャンネル：最初のメッセージを送信する | ノード：メッシュに参加しているノードを確認する | マップとウェイポイント：ノードの位置を表示する | 設定：無線機とユーザープロフィールを構成する | . Meshtastic は初めてですか？ meshtastic.org の入門ガイドでは、ハードウェアの選択、無線機の初期設定、最初のメッシュのセットアップについて説明しています。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html#%E6%AC%A1%E3%81%AE%E3%82%B9%E3%83%86%E3%83%83%E3%83%97", + + "relUrl": "/ja-rJP/user/onboarding.html#次のステップ" + },"4217": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html", + + "relUrl": "/hu-rHU/user/onboarding.html" + },"4218": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html#first-launch", + + "relUrl": "/hu-rHU/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html#permissions", + + "relUrl": "/hu-rHU/user/onboarding.html#permissions" + },"4220": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html#after-setup", + + "relUrl": "/hu-rHU/user/onboarding.html#after-setup" + },"4221": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/hu-rHU/user/onboarding.html#whats-next" + },"4222": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html", + + "relUrl": "/ht-rHT/user/onboarding.html" + },"4223": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html#first-launch", + + "relUrl": "/ht-rHT/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html#permissions", + + "relUrl": "/ht-rHT/user/onboarding.html#permissions" + },"4225": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html#after-setup", + + "relUrl": "/ht-rHT/user/onboarding.html#after-setup" + },"4226": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/ht-rHT/user/onboarding.html#whats-next" + },"4227": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html", + + "relUrl": "/gl-rES/user/onboarding.html" + },"4228": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html#first-launch", + + "relUrl": "/gl-rES/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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html#permissions", + + "relUrl": "/gl-rES/user/onboarding.html#permissions" + },"4230": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html#after-setup", + + "relUrl": "/gl-rES/user/onboarding.html#after-setup" + },"4231": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/gl-rES/user/onboarding.html#whats-next" + },"4232": { + "doc": "Getting Started", + "title": "Getting Started", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html", + + "relUrl": "/tr-rTR/user/onboarding.html" + },"4233": { + "doc": "Getting Started", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html#first-launch", + + "relUrl": "/tr-rTR/user/onboarding.html#first-launch" + },"4234": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html#permissions", + + "relUrl": "/tr-rTR/user/onboarding.html#permissions" + },"4235": { + "doc": "Getting Started", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html#after-setup", + + "relUrl": "/tr-rTR/user/onboarding.html#after-setup" + },"4236": { + "doc": "Getting Started", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/tr-rTR/user/onboarding.html#whats-next" + },"4237": { + "doc": "Primeros Pasos", + "title": "Primeros Pasos", + "content": "Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app. ", + "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html", + + "relUrl": "/es-rES/user/onboarding.html" + },"4238": { + "doc": "Primeros Pasos", + "title": "First Launch", + "content": "When you open the app for the first time, you’ll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings. Welcome Screen . The welcome screen introduces Meshtastic and its core capabilities: . | Off-grid mesh communication | No cellular or internet required | End-to-end encrypted messaging | . Tap Get Started to proceed through the setup flow. ", + "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html#first-launch", + + "relUrl": "/es-rES/user/onboarding.html#first-launch" + },"4239": { + "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: . | Bluetooth scanning — discover nearby Meshtastic radios | Bluetooth connect — establish and maintain connections with paired radios | . Grant both permissions when prompted. Without Bluetooth, you’ll need to use USB or TCP connections instead. Location Permission . ⚠️ Why is location required for Bluetooth? Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app” or “Always” depending on your preference: . | While using the app — position updates only when the app is open | Always — enables background position updates for always-on mesh presence | . If denied, Bluetooth scanning will not function and your node will not report a position. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | 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 . On supported devices, the app may request permission for critical alerts: . | These are high-priority notifications that can break through Do Not Disturb mode | Useful for emergency mesh alerts or urgent messages | You can skip this step if you don’t need breakthrough notifications | Configure or revoke later in Android notification settings | . ", + "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html#permissions", + + "relUrl": "/es-rES/user/onboarding.html#permissions" + },"4240": { + "doc": "Primeros Pasos", + "title": "After Setup", + "content": "Once permissions are granted, the app transitions to 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, you can grant them later through Android Settings → Apps → Meshtastic → Permissions. The app will prompt you again if a missing permission blocks a feature you try to use. ", + "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html#after-setup", + + "relUrl": "/es-rES/user/onboarding.html#after-setup" + },"4241": { + "doc": "Primeros Pasos", + "title": "What’s Next?", + "content": "Once connected to a radio, explore: . | Connections — pair your first radio device | Messages & Channels — send your first message | Nodes — see who’s on your mesh | Map & Waypoints — view node positions | Settings — configure your radio and user profile | . 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#whats-next", + + "relUrl": "/es-rES/user/onboarding.html#whats-next" },"4242": { "doc": "Persistence", "title": "Persistence", @@ -29735,4177 +29735,4177 @@ "relUrl": "/en/developer/persistence.html#best-practices" },"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. 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" - },"4249": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Lýsing | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Lýsing | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Lýsing | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Lýsing | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Lýsing | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Lýsing | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Lýsing | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Lýsing | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Lýsing | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/is-rIS/user/settings-module-admin.html#module-configuration", - - "relUrl": "/is-rIS/user/settings-module-admin.html#module-configuration" - },"4250": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Endurræsa . Remotely reboot a connected or administered node. Villuleitarborð . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4251": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4252": { - "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" - },"4253": { - "doc": "設定：モジュールと管理", - "title": "設定：モジュールと管理", - "content": "オプションの機能モジュールを設定し、デバイスの管理を行います。 モジュールは、専用の機能で Meshtastic を拡張します。それぞれ個別に有効・無効を切り替えられます。 . 💡 ヒント： 実際に使うモジュールだけを有効にすれば十分です。 使わないモジュールを無効にすると、電波利用時間が減り、バッテリーを節約でき、設定もシンプルになります。 . モジュールの設定は、トグルスイッチ、ドロップダウン、テキストフィールド、スライダーを備えたカード形式のレイアウトを使用します： . . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/settings-module-admin.html", - - "relUrl": "/ja-rJP/user/settings-module-admin.html" - },"4254": { - "doc": "設定：モジュールと管理", - "title": "モジュールの設定", - "content": "MQTT モジュール . インターネット接続のために、メッシュのメッセージを MQTT サーバーとの間で橋渡しします。 これにより、無線の到達範囲を超えてメッシュを拡張したり、ホームオートメーションシステムと連携したりできます。 . | 設定項目 | 説明 | . | 有効 | MQTT ブリッジを切り替え | . | サーバー | MQTT サーバーのアドレス | . | ユーザー名 | 認証用のユーザー名 | . | パスワード | 認証用のパスワード | . | 暗号化 | MQTT ペイロードを暗号化 | . | JSON 出力 | ⚠️ 非推奨：JSON のサポートはファームウェアから削除されました。このフィールドは無視されます | . | TLS | セキュアな接続を使用 | . | ルートトピック | MQTT のベーストピックパス | . | マップ報告 | 公開マップ用に位置を公開 | . 暗号化、プライバシー、サーバーの設定を含む詳しい使い方は、MQTT を参照してください。 . シリアルモジュール . 外部デバイスとの連携（GPS モジュール、センサー、カスタムハードウェア）のために、シリアルポート通信を有効にします。 有効にすると、ノードのシリアルポートで protobuf またはテキストデータを送受信でき、外部のマイコンやコンピューターがメッシュとやり取りできるようになります。 . | 設定項目 | 説明 | . | 有効 | シリアル通信を有効化 | . | エコー | 受信したシリアルデータをそのまま返す | . | モード | テキスト、Protobuf、または NMEA 出力 | . | RX/TX ピン | シリアル接続用の GPIO ピン | . | ボーレート | シリアル通信の速度 | . 外部通知モジュール . 無線機ハードウェアのブザー、LED、振動によるアラートを制御します。 メッセージ到着時に物理的に知らせる必要があるデバイスに便利です。特に無人設置や屋外設置で役立ちます。 . | 設定項目 | 説明 | . | 有効 | 通知を有効化 | . | メッセージ通知 | メッセージ受信時に通知 | . | メッセージのブザー通知 | メッセージにブザーを使用 | . | メッセージの振動通知 | メッセージに振動を使用 | . | ベル通知 | ベル文字の受信時に通知 | . | 出力（GPIO） | 通知出力用のピン | . | アクティブ | アクティブハイまたはアクティブロー | . | 継続時間（ミリ秒） | 通知の長さ | . | I2S をブザーとして使用 | I2S 音声出力を使用 | . Store & Forward モジュール . 一時的にオフラインだったノードのためにメッセージをバッファリングし、それらのノードが再接続したときに再送します。 ノードが頻繁に圏内・圏外を行き来するメッシュに不可欠です。短時間の切断中にメッセージが失われないようにします。 . | 設定項目 | 説明 | . | 有効 | ストア＆フォワードを有効化 | . | ハートビート | このノードのストア＆フォワード機能を定期的に告知する | . | レコード数 | 保存するメッセージの最大数 | . | 履歴の返送（最大） | 再送するメッセージの最大数 | . | 履歴の返送（期間） | 再送する時間の範囲 | . | サーバー | メッシュのストア＆フォワードサーバーとして動作する（十分なメモリが必要、例：PSRAM 搭載の ESP32） | . 💡 ヒント： ストア＆フォワードは、十分なメモリを持つノード（PSRAM 搭載の ESP32）で最も良く機能します。 ルーターノードは通常は常時起動しているため、理想的な候補です。 . レンジテストモジュール . ノード間のリンク品質を評価するための、自動レンジテストツールです。 有効にすると、ノードはカウンターを増やしながらテストメッセージを定期的に送信します。 受信側のノードがこれらのメッセージを記録するため、歩いたり車で移動したりして、後からどの距離でメッセージが届かなくなったかを分析できます。 . | 設定項目 | 説明 | . | 有効 | レンジテストを有効化 | . | 送信間隔（秒） | テスト送信の間隔 | . | CSV を保存 | 受信したテストデータを SD カードに記録 | . テレメトリモジュール . ノードがメッシュと共有するテレメトリデータを制御します。 テレメトリには、デバイスの状態（バッテリー、連続稼働時間）と環境センサーのデータ（温度、湿度、気圧）が含まれます。 . | 設定項目 | 説明 | . | デバイスメトリクスの間隔 | デバイスメトリクスを報告する頻度 | . | 環境メトリクスの間隔 | 環境センサーを報告する頻度 | . | 大気質を有効化 | 粒子状物質センサーのデータを報告 | . | 電力メトリクスを有効化 | 電力使用量を報告 | . 対応センサーと設定の推奨事項については、テレメトリとセンサー を参照してください。 . 定型メッセージモジュール . デバイスの物理ボタンからアクセスできる、あらかじめ設定されたメッセージです（ロータリーエンコーダー、キーパッド、または同様の入力ハードウェアを備えた無線機向け）。 スマートフォンを接続していなくても送信できる、クイック送信メッセージのリストを定義します。フィールドでの使用に最適です。 . | 設定項目 | 説明 | . | 有効 | ⚠️ 非推奨：現在のファームウェアはこのトグルを無視することがあります | . | メッセージ | 改行で区切ったメッセージのリスト | . | ベルを送信 | 送信時にベル音を鳴らす | . | ロータリーエンコーダー | ロータリーエンコーダー入力を有効化 | . | 上／下／押下ピン | 入力用の GPIO ピンの割り当て | . オーディオモジュール . メッシュ上での低帯域幅の音声通信のための、Codec2 音声サポートです。 これは、Codec2 コーデックを使って音声を非常に小さなデータパケットにエンコードする、実験的な機能です。 . | 設定項目 | 説明 | . | 有効 | オーディオモジュールを有効化 | . | Codec2 レート | 音質と帯域幅のトレードオフ | . | I2S ワードセレクト | I2S WS 用の GPIO ピン | . | I2S データ入力 | I2S DIN 用の GPIO ピン | . | I2S データ出力 | I2S DOUT 用の GPIO ピン | . ⚠️ 注意： オーディオには特定のハードウェア（I2S マイクとスピーカー）が必要です。 音質は非常に低帯域です。「聞き取れる無線の声」程度で、電話並みの品質ではないと考えてください。 . リモートハードウェアモジュール . メッシュネットワーク経由での GPIO 制御です。 リモートのノードが、別のノードの GPIO ピンを読み書きできるようにします。リレーの作動、スイッチの読み取り、離れた場所からの外部ハードウェア制御に便利です。 . | 設定項目 | 説明 | . | 有効 | リモート GPIO アクセスを有効化 | . | 未定義ピンを許可 | 任意の GPIO ピンへのアクセスを許可（セキュリティリスク） | . | 利用可能なピン | このノードがリモートの読み書き用に公開する GPIO ピン（最大 4 個） | . ⚠️ 警告： 「未定義ピンを許可」を有効にすると、リモートのノードがすべての GPIO ピンにアクセスでき、無線機自体のハードウェアに干渉するおそれがあります。 GPIO 専用のノードでのみ有効にしてください。 . 隣接ノード情報モジュール . 直接受信した隣接ノードの情報をブロードキャストし、メッシュのトポロジーマッピングを可能にします。 有効にした各ノードは、受信できる他のノードとその信号品質のリストを定期的に共有します。 . | 設定項目 | 説明 | . | 有効 | 隣接ノードのブロードキャストを有効化 | . | 更新間隔（秒） | 隣接ノードのリストをブロードキャストする頻度 | . | LoRa で送信 | MQTT／スマートフォンだけでなく、LoRa 経由でも隣接ノード情報をブロードキャストします。 デフォルトの鍵と名前を使用しているチャンネルでは利用できません | . 隣接ノードのデータをメッシュのトポロジー探索に使う方法については、探索 を参照してください。 . アンビエントライティングモジュール . 対応ハードウェア上の、オンボードの NeoPixel やその他のアドレサブル RGB LED を制御します。 視覚的なステータス表示、通知ライト、装飾的な演出に使用できます。 . | 設定項目 | 説明 | . | LED の状態 | LED のオン／オフを切り替え | . | 電流 | LED の電流制限（0〜31） | . | 赤／緑／青 | 各色チャンネルの値（0〜255） | . 検知センサーモジュール . ノードを、動きやドアを検知するセンサーアラートシステムに変えます。 GPIO ピンが状態の変化（動きの検知、ドアの開放）を検出すると、ノードはメッシュ経由でアラートメッセージをブロードキャストします。 . | 設定項目 | 説明 | . | 有効 | 検知センサーを有効化 | . | 監視ピン | センサーに接続された GPIO ピン | . | 検知トリガーの種類 | ピンの状態を検知イベントにどう対応させるか（例：アクティブハイ／ロー、エッジトリガー） | . | 入力プルアップモードを使用 | ピンの内蔵プルアップ抵抗を有効にする | . | 最小ブロードキャスト間隔（秒） | アラートのブロードキャスト間の最小時間 | . | 状態ブロードキャスト（秒） | 定期的な状態ブロードキャストの間隔 | . | ベルを送信 | アラートにベル文字を含める | . | 分かりやすい名前 | このセンサーのカスタム名 | . Paxcounter モジュール . WiFi と BLE のプローブ要求を使った人数カウンターです。 スマートフォンやノートパソコンがネットワークを探すときに発するプローブ要求を受動的に受信して、近くのデバイスを数えます。 ESP32 デバイスでのみ利用できます。 . | 設定項目 | 説明 | . | 有効 | 人数カウントを有効化 | . | 更新間隔（秒） | カウントを報告する頻度 | . 💡 ヒント： Paxcounter は、登山口やイベント会場などの人出を推定するのに便利です。 カウントはおおよその値です。1 人が複数のデバイスを持っていることがあります。 . TAK モジュール . ATAK および WinTAK と相互運用するための、Team Awareness Kit 連携です。 詳しい設定と使い方は、TAK 連携 を参照してください。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/settings-module-admin.html#%E3%83%A2%E3%82%B8%E3%83%A5%E3%83%BC%E3%83%AB%E3%81%AE%E8%A8%AD%E5%AE%9A", - - "relUrl": "/ja-rJP/user/settings-module-admin.html#モジュールの設定" - },"4255": { - "doc": "設定：モジュールと管理", - "title": "管理", - "content": "リモート管理 . 管理者鍵を共有しているノードをリモートで設定します： . | ノードリストで対象のノードを選択します。 | そのノードの「設定」に移動します。 | 設定を変更します。 | 「保存」をタップします。変更がメッシュ経由で送信されます。 | . ⚠️ 必要条件： 自分のノードと対象のノードの両方に管理者鍵が設定されていること。 . ノードデータベースの整理 . 設定可能な期間内に受信していない古いノードを、ローカルデータベースから削除します。 . 工場出荷時リセット . すべての設定を工場出荷時のデフォルトにリセットします。 この操作は取り消せません。 . 再起動 . 接続中または管理中のノードをリモートで再起動します。 . デバッグ . 診断出力の表示・絞り込み・エクスポートを行う「パケット」タブと「アプリログ」タブを開きます。 詳しい手順は、デバッグログ を参照してください。 . リモート管理のトラブルシューティング . | 「対象ノードから応答がありません」：対象が圏外、オフライン、または管理者鍵が一致していない可能性があります。 両方のノードで管理者鍵が一致しているか確認してください。 | 変更が適用されない：一部の設定は、反映に再起動が必要です。 保存後に「再起動」を実行してみてください。 | リモートの設定が表示されない：自分のノードに、対象ノードの管理者鍵があることを確認してください。 管理チャンネルは、管理者鍵を設定すると自動的に構成されます。 | . ", - "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#管理" - },"4256": { - "doc": "設定：モジュールと管理", - "title": "関連トピック", - "content": ". | 設定：無線機とユーザー：基本の無線機とユーザープロファイルの設定 | モジュール設定リファレンス：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#関連トピック" - },"4257": { - "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. 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" - },"4258": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descripció | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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ó | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descripció | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descripció | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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ó | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descripció | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descripció | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descripció | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descripció | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descripció | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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ó | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descripció | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html#module-configuration", - - "relUrl": "/ca-rES/user/settings-module-admin.html#module-configuration" - },"4259": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reiniciar . Remotely reboot a connected or administered node. Panell de depuració . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4260": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4261": { - "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" - },"4262": { - "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. 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" - },"4263": { - "doc": "Settings — Modules & Admin", - "title": "Конфигурација модула", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Опис | . | Омогућено | Toggle MQTT bridge | . | Сервер | MQTT broker address | . | Корисничко име | Authentication username | . | Лозинка | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Корен тема | Base MQTT topic path | . | Извештај мапе | Publish position for public map | . 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 | . | Мод | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Опис | . | Омогућено | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Активан | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Омогућено | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Омогућено | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Опис | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Поруке | Newline-separated list of messages | . | Пошаљи звоно | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | Омогућено | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Опис | . | Омогућено | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Омогућено | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Пошаљи звоно | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Омогућено | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration 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#конфигурација-модула" - },"4264": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Ресетовање на фабричка подешавања . Resets all settings to factory defaults. This cannot be undone. Поново покрени . Remotely reboot a connected or administered node. 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. 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" - },"4265": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4266": { - "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" - },"4267": { - "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. 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" - },"4268": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | 설명 | . | 활성화 | Toggle MQTT bridge | . | 서버 | MQTT broker address | . | 사용자명 | Authentication username | . | 비밀번호 | Authentication password | . | 암호화 | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial Module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | 설명 | . | 활성화 | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | 설명 | . | 활성화 | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | 설명 | . | 활성화 | Activate store and forward | . | Heartbeat | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | 설명 | . | 활성화 | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | 설명 | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | 설명 | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | 메시지기기 | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | 설명 | . | 활성화 | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | 설명 | . | 활성화 | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | 설명 | . | 활성화 | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | 설명 | . | 활성화 | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | 설명 | . | 활성화 | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/settings-module-admin.html#module-configuration", - - "relUrl": "/ko-rKR/user/settings-module-admin.html#module-configuration" - },"4269": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. 재부팅 . Remotely reboot a connected or administered node. 디버그 패널 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#관리" - },"4270": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4271": { - "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" - },"4272": { - "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. 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" - },"4273": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descriere | . | Activat | Toggle MQTT bridge | . | Server | MQTT broker address | . | Nume de utilizator | Authentication username | . | Parolă | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Activat | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descriere | . | Activat | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descriere | . | Activat | Activate store and forward | . | Puls | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Activat | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descriere | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descriere | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Mesaje | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descriere | . | Activat | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descriere | . | Activat | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descriere | . | Activat | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Activat | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descriere | . | Activat | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/settings-module-admin.html#module-configuration", - - "relUrl": "/ro-rRO/user/settings-module-admin.html#module-configuration" - },"4274": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Curăță baza de date a nodurilor . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Restartează . Remotely reboot a connected or administered node. Panou de depanare . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4275": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4276": { - "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" - },"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. 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" - },"4278": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Cur síos | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Cur síos | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Cur síos | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Cur síos | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Cur síos | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Cur síos | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Cur síos | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Cur síos | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Cur síos | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/settings-module-admin.html#module-configuration", - - "relUrl": "/ga-rIE/user/settings-module-admin.html#module-configuration" - },"4279": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Athmhaoinigh . Remotely reboot a connected or administered node. Painéal Laige . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4280": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4281": { - "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" - },"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. 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" - },"4283": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | תיאור | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial Module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | תיאור | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | תיאור | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | תיאור | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | תיאור | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | תיאור | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | תיאור | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | הודעות | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | תיאור | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | תיאור | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | תיאור | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | תיאור | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | תיאור | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/settings-module-admin.html#module-configuration", - - "relUrl": "/iw-rIL/user/settings-module-admin.html#module-configuration" - },"4284": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. אתחול מחדש . Remotely reboot a connected or administered node. פאנל דיבאג . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4285": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4286": { - "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" - },"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. 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" - },"4288": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Beskrivning | . | Aktiverad | Toggle MQTT bridge | . | Server | MQTT broker address | . | Användarnamn | Authentication username | . | Lösenord | Authentication password | . | Kryptering | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Aktiverad | Activate serial communication | . | Eko | Echo received serial data back | . | Typ | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Hastighet | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Beskrivning | . | Aktiverad | Activate notifications | . | Meddelande-utgång | Notify on incoming messages | . | Meddelande-summer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Klock-tecken-utgång | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Aktiv | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beskrivning | . | Aktiverad | Activate store and forward | . | Pulsera | Periodically announce this node’s store-and-forward capability | . | Post | 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 . 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 | . | Aktiverad | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Beskrivning | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Aktivera luftkvalitet | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beskrivning | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Meddelanden | Newline-separated list of messages | . | Skicka klocka | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beskrivning | . | Aktiverad | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Beskrivning | . | Aktiverad | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beskrivning | . | Aktiverad | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Aktiverad | Activate detection sensor | . | Stift 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) | . | Use Input Pullup Mode | Enable the pin’s internal pull-up resistor | . | Minimum Broadcast (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Skicka klocka | Include bell character in alerts | . | Visningsnamn | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beskrivning | . | Aktiverad | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/settings-module-admin.html#module-configuration", - - "relUrl": "/sv-rSE/user/settings-module-admin.html#module-configuration" - },"4289": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Rensa noddatabas . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Starta om . Remotely reboot a connected or administered node. Felsökningspanel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4290": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4291": { - "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" - },"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. 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" - },"4293": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Deskripsyon | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Deskripsyon | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Deskripsyon | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Deskripsyon | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Deskripsyon | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Deskripsyon | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Deskripsyon | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Deskripsyon | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Deskripsyon | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/settings-module-admin.html#module-configuration", - - "relUrl": "/ht-rHT/user/settings-module-admin.html#module-configuration" - },"4294": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Rekòmanse . Remotely reboot a connected or administered node. Panno Debug . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4295": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4296": { - "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" - },"4297": { - "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ä. 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" - },"4298": { - "doc": "Asetukset — Moduulit ja ylläpito", - "title": "Moduulin määritys", - "content": "MQTT-moduuli . Yhdistää verkon viestejä MQTT-välityspalvelimeen ja sieltä takaisin internet-yhteyksiä varten. Näin laajennat verkkoasi radiokantaman ulkopuolelle tai integroit sen kodin automaatiojärjestelmiin. | Asetus | Kuvaus | . | Käytössä | Ota MQTT-välityspalvelin käyttöön | . | Palvelin | MQTT-välityspalvelimen osoite | . | Käyttäjänimi | Todennuksen käyttäjätunnus | . | Salasana | Todennuksen salasana | . | Salaus | Salaa MQTT-viestisisällöt | . | JSON Output | ⚠️ Vanhentunut — JSON-tuki poistettu laiteohjelmistosta, kenttä ohitetaan | . | TLS | Käytä suojattua yhteyttä | . | Juuriaihe | MQTT:n perusaihepolku | . | Karttaraportointi | Julkaise sijainti julkiselle kartalle | . Katso MQTT saadaksesi yksityiskohtaisen käyttöoppaan, joka sisältää salauksen, tietosuojan ja välityspalvelimen määrityksen. Sarjaporttimoduuli . 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 | . | Käytössä | Ota sarjaporttiviestintä käyttöön | . | Toista | Toista vastaanotettu sarjaporttidata takaisin | . | Tila | Teksti-, Protobuf- tai NMEA-ulostulo | . | RX/TX pinnit | GPIO-pinnit sarjaporttiyhteyttä varten | . | Baud-siirtonopeus | Sarjaporttiyhteyden nopeus | . Ulkoisten ilmoitusten moduuli . Ohjaa radion laitteiston summeri-, LED- tai värinähälytyksiä. Hyödyllinen laitteille, joiden täytyy ilmoittaa fyysisesti viestin saapumisesta — erityisen hyödyllinen valvomattomissa tai ulkokäyttöön asennetuissa laitteissa. | Asetus | Kuvaus | . | Käytössä | Ota ilmoitukset käyttöön | . | Hälytysviesti | Ilmoita saapuvista viesteistä | . | Hälytysviestin summeri | Käytä summeria viesteille | . | Värinähälytys viesteille | Käytä värinää viesteille | . | Hälytysääni | Ilmoita soittomerkkimerkistä (bell character) | . | Ulostulo (GPIO) | Pinni ilmoitusulostuloa varten | . | Käytössä | Aktiivinen korkealla tai matalalla tasolla | . | Kesto (ms) | Ilmoituksen kesto | . | Käytä I2S:ää summerina | Käytä I2S-äänilähtöä | . Varastoi & välitä -moduuli . 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 | . | Käytössä | Ota Varastoi & välitä käyttöön | . | Valvontasignaali | Ilmoita tämän radion varastoi & välitä -ominaisuudesta säännöllisesti | . | Tiedot | Tallennettujen viestien enimmäismäärä | . | Historian palautus (enintään) | Toistettavien viestien enimmäismäärä | . | Historian palautus (aikaikkuna) | 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ä. Kuuluvuustesti-moduuli . 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 | . | Käytössä | Ota kuuluvuustesti käyttöön | . | Lähetysväli (s) | Aika testilähetysten välillä | . | Tallenna CSV-tiedosto | Kirjaa vastaanotetut testitiedot SD-kortille | . Telemetriamoduuli . 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). | Asetus | Kuvaus | . | Laitemittarien väli | Kuinka usein laitemittarit raportoidaan | . | Ympäristömittarien väli | Kuinka usein ympäristöanturit raportoidaan | . | Ilmanlaatu käytössä | Raportoi hiukkasanturin tiedot | . | Virtamittarit käytössä | Raportoi virrankulutus | . Katso Telemetria ja anturit saadaksesi tietoa tuetuista antureista ja määrityssuosituksista. Valmiiden viestien moduuli . Esimääritetyt viestit, joita voidaan käyttää laitteen fyysisillä painikkeilla (radioille, joissa on kiertokooderi, näppäimistö tai vastaava laitteisto). Määritä luettelo pikaviesteistä, jotka voidaan lähettää ilman yhdistettyä puhelinta — ihanteellinen kenttäkäyttöön. | Asetus | Kuvaus | . | Käytössä | ⚠️ Vanhentunut — nykyinen laiteohjelmisto saattaa ohittaa tämän asetuksen | . | Viestit | Rivinvaihdoilla eroteltu viestiluettelo | . | Lähetä äänimerkki | Toista merkkiääni lähetyksen yhteydessä | . | Kiertokooderi | Ota kiertokooderin syöte käyttöön | . | Ylös, alas ja painallus-pinnit | GPIO-pinnien määritykset syötteille | . Äänimoduuli . 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 | . | Käytössä | Ota äänimoduuli käyttöön | . | Codec2-nopeus | Äänenlaadun ja kaistanleveyden välinen kompromissi | . | I2S Word Select | GPIO-pinni I2S WS:lle | . | I2S-datasisääntulo | GPIO-nasta I2S DIN:lle | . | I2S-dataulostulo | GPIO-pinni I2S DOUT:lle | . ⚠️ Huomautus: Ääniominaisuudet edellyttävät yhteensopivaa laitteistoa (I2S-mikrofoni ja kaiutin). Äänenlaatu on hyvin matalakaistainen — ajattele “ymmärrettävää radiopuhetta”, ei puhelinlaatua. Etälaitteiston moduuli . 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ä. | Asetus | Kuvaus | . | Käytössä | Ota etä-GPIO-käyttö käyttöön | . | Salli määrittelemättömät pinnit | 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ä | . ⚠️ Varoitus: Määrittelemättömien pinnien salliminen antaa etäradioille pääsyn kaikkiin GPIO-pinneihin, mikä voi häiritä radion omaa laitteistoa. Ota käyttöön vain erillisissä GPIO-radioissa. Naapuritieto-moduuli . 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 | . | Käytössä | Ota naapuritiedon lähetys käyttöön | . | Päivitysväli (s) | Kuinka usein naapuriluettelo lähetetään | . | Lähetä LoRan 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 Haku saadaksesi lisätietoja naapuritietojen käyttämisestä verkon topologian tutkimiseen. Ympäristövalaistusmoduuli . Ohjaa tuetuissa laitteissa olevaa NeoPixeliä tai muita osoitteellisia RGB-LEDejä. Voidaan käyttää visuaalisina tilailmaisimina, ilmoitusvaloina tai koriste-efekteinä. | Asetus | Kuvaus | . | Ledin 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) | . Tunnistusanturimoduuli . 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 | . | Käytössä | Ota tunnistusanturi käyttöön | . | Valvonta pinni | Anturiin kytketty GPIO-pinni | . | Havaitsemisen laukaisutyyppi | Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu) | . | Käytä sisäistä ylösvetovastusta | Ota pinnin sisäinen ylösvetovastus käyttöön | . | Lähetyksen vähimmäisväli (s) | Hälytyslähetysten vähimmäisaika | . | Tilalähetys (s) | Tilatiedon lähetysväli | . | Lähetä äänimerkki | Sisällytä soittomerkkimerkki hälytyksiin | . | Käyttäjäystävälinen nimi | Tälle anturille määritetty nimi | . PAX-laskurimoduuli . Henkilölaskuri, joka hyödyntää Wi-Fi- ja BLE-koepyyntöjä. 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 | . | Käytössä | Ota henkilölaskenta käyttöön | . | Päivitysväli (s) | Kuinka usein laskentatiedot raportoidaan | . 💡 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. TAK-moduuli . Team Awareness Kit -integraatio yhteensopivuutta varten ATAK- ja WinTAK-järjestelmien kanssa. Katso TAK-integraatio saadaksesi tarkemmat määritys- ja käyttöohjeet. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/settings-module-admin.html#moduulin-m%C3%A4%C3%A4ritys", - - "relUrl": "/fi-rFI/user/settings-module-admin.html#moduulin-määritys" - },"4299": { - "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. | . ⚠️ Edellyttää: Ylläpitoavain on määritetty sekä omassa radiossasi että kohderadiossa. Tyhjennä NodeDB-tietokanta . Poistaa vanhentuneet radiot paikallisesta tietokannastasi, jos niistä ei ole kuultu määritettävän aikaikkunan aikana. Palauta tehdasasetukset . Palauttaa kaikki asetukset tehdasasetuksiin. Tätä toimintoa ei voi perua. Käynnistä uudelleen . Käynnistä yhdistetty tai ylläpidettävä radio etänä uudelleen. Vianetsintäpaneeli . Avaa Paketit- ja Sovelluslokit-välilehdet diagnostiikkatietojen tarkastelua, suodatusta ja vientiä varten. Katso Virheenjäljityslokit, jossa on täydellinen käyttöohje. Etähallinnan vianmääritys . | 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" - },"4300": { - "doc": "Asetukset — Moduulit ja ylläpito", - "title": "Aiheeseen liittyvät aiheet", - "content": ". | Asetukset — Radio ja käyttäjä — radion ja käyttäjäprofiilin keskeiset asetukset | 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" - },"4301": { - "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. 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" - },"4302": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descrición | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descrición | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrición | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descrición | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrición | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrición | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descrición | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrición | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrición | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/gl-rES/user/settings-module-admin.html#module-configuration", - - "relUrl": "/gl-rES/user/settings-module-admin.html#module-configuration" - },"4303": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reiniciar . Remotely reboot a connected or administered node. 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. 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" - },"4304": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4305": { - "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" - },"4306": { - "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. 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" - },"4307": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Опис | . | Увімкнено | Toggle MQTT bridge | . | Сервер | MQTT broker address | . | Ім’я користувача | Authentication username | . | Пароль | Authentication password | . | Шифрування | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Режим | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Опис | . | Увімкнено | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Увімкнено | Activate store and forward | . | Пульсація | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Увімкнено | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Опис | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Повідомлення | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | Увімкнено | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Опис | . | Увімкнено | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Увімкнено | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | Опис | . | Увімкнено | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Увімкнено | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html#module-configuration", - - "relUrl": "/uk-rUA/user/settings-module-admin.html#module-configuration" - },"4308": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Очистити базу даних вузлів . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Перевантажити . Remotely reboot a connected or administered node. Панель налагодження . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#адміністрування" - },"4309": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4310": { - "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" - },"4311": { "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. 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" - },"4312": { + },"4249": { "doc": "Settings — Modules & Admin", "title": "Moduleinstellungen", "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Einstellung | Beschreibung | . | Aktiviert | Toggle MQTT bridge | . | Server | MQTT broker address | . | Benutzername | Authentication username | . | Passwort | Authentication password | . | Verschlüsselung | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Hauptthema | Base MQTT topic path | . | Map Report | Publish position for public map | . 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 | . | Aktiviert | Activate serial communication | . | Echo | Echo received serial data back | . | Betriebsmodus | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baudrate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Einstellung | Beschreibung | . | Aktiviert | Activate notifications | . | Warnmeldung | Notify on incoming messages | . | Summer bei Warnmeldung | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Warnglocke | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Aktiv | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Einstellung | Beschreibung | . | Aktiviert | Activate store and forward | . | Puls | Periodically announce this node’s store-and-forward capability | . | Datensätze | 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 . 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 | . | Aktiviert | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Einstellung | Beschreibung | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Luftqualität aktiviert | Report particulate sensor data | . | Energiedaten aktiviert | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Einstellung | Beschreibung | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Nachrichten | Newline-separated list of messages | . | Sende Glocke | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Einstellung | Beschreibung | . | Aktiviert | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Wortauswahl | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Einstellung | Beschreibung | . | Aktiviert | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Einstellung | Beschreibung | . | Aktiviert | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 Status | 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 | . | Aktiviert | Activate detection sensor | . | GPIO Pin überwachen | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Sende Glocke | Include bell character in alerts | . | Anzeigename | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Einstellung | Beschreibung | . | Aktiviert | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/de-rDE/user/settings-module-admin.html#moduleinstellungen", "relUrl": "/de-rDE/user/settings-module-admin.html#moduleinstellungen" - },"4313": { + },"4250": { "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Knotendatenbank leeren . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Werkseinstellungen . Resets all settings to factory defaults. This cannot be undone. Neustart . Remotely reboot a connected or administered node. Debug-Ausgaben . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4314": { + },"4251": { "doc": "Settings — Modules & Admin", "title": "Related Topics", "content": ". | Settings — Radio & User — core radio 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" - },"4315": { + },"4252": { "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" - },"4316": { + },"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. 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", + "url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html#settings--modules--admin", - "relUrl": "/hr-rHR/user/settings-module-admin.html#settings--modules--admin" - },"4317": { + "relUrl": "/ca-rES/user/settings-module-admin.html#settings--modules--admin" + },"4254": { "doc": "Settings — Modules & Admin", "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Opis | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Opis | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Opis | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Opis | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/settings-module-admin.html#module-configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descripció | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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ó | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descripció | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descripció | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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ó | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descripció | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descripció | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descripció | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descripció | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descripció | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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ó | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descripció | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html#module-configuration", - "relUrl": "/hr-rHR/user/settings-module-admin.html#module-configuration" - },"4318": { + "relUrl": "/ca-rES/user/settings-module-admin.html#module-configuration" + },"4255": { "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Ponovno pokreni . Remotely reboot a connected or administered node. Otklanjanje pogrešaka . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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", + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reiniciar . Remotely reboot a connected or administered node. Panell de depuració . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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": "/hr-rHR/user/settings-module-admin.html#administration" - },"4319": { + "relUrl": "/ca-rES/user/settings-module-admin.html#administration" + },"4256": { "doc": "Settings — Modules & Admin", "title": "Related Topics", "content": ". | Settings — Radio & User — core radio 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", + "url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html#related-topics", - "relUrl": "/hr-rHR/user/settings-module-admin.html#related-topics" - },"4320": { + "relUrl": "/ca-rES/user/settings-module-admin.html#related-topics" + },"4257": { "doc": "Settings — Modules & Admin", "title": "Settings — Modules & Admin", "content": " ", - "url": "/Meshtastic-Android/main/hr-rHR/user/settings-module-admin.html", + "url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html", - "relUrl": "/hr-rHR/user/settings-module-admin.html" - },"4321": { - "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. 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" - },"4322": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Aprašymas | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Aprašymas | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Aprašymas | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Aprašymas | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Aprašymas | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Aprašymas | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Aprašymas | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Aprašymas | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Aprašymas | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/settings-module-admin.html#module-configuration", - - "relUrl": "/lt-rLT/user/settings-module-admin.html#module-configuration" - },"4323": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Perkrauti . Remotely reboot a connected or administered node. Derinimo skydelis . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4324": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4325": { - "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" - },"4326": { - "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. 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" - },"4327": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Description | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Description | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Description | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Description | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Description | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Description | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Description | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Description | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Description | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration 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" - },"4328": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reboot . Remotely reboot a connected or administered node. Debug Panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4329": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4330": { - "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" - },"4331": { - "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. 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" - },"4332": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Leírás | . | Engedélyezve | Toggle MQTT bridge | . | Szerver | MQTT broker address | . | Felhasználónév | Authentication username | . | Jelszó | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Engedélyezve | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Leírás | . | Engedélyezve | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Leírás | . | Engedélyezve | Activate store and forward | . | Heartbeat jel | Periodically announce this node’s store-and-forward capability | . | Bejegyzések | Maximum stored messages | . | History Return (max) | Max messages to replay | . | History Return (window) | 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 . 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 | . | Engedélyezve | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Leírás | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Leírás | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Üzenetek | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Leírás | . | Engedélyezve | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Leírás | . | Engedélyezve | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Leírás | . | Engedélyezve | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 State | 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 | . | Engedélyezve | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Leírás | . | Engedélyezve | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/settings-module-admin.html#module-configuration", - - "relUrl": "/hu-rHU/user/settings-module-admin.html#module-configuration" - },"4333": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Csomópont-adatbázis tisztítása . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Újraindítás . Remotely reboot a connected or administered node. Hibakereső panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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ó" - },"4334": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4335": { - "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" - },"4336": { - "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. 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" - },"4337": { - "doc": "Settings — Modules & Admin", - "title": "Конфигурация на модулите", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Настройка | Описание | . | Активиран | Toggle MQTT bridge | . | Сървър | MQTT broker address | . | Потребителско име | Authentication username | . | Парола | Authentication password | . | Криптиране | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial Module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Настройка | Описание | . | Активиран | Activate serial communication | . | Ехо | Echo received serial data back | . | Режим | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Настройка | Описание | . | Активиран | Activate notifications | . | Предупредително съобщение | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Активно | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Настройка | Описание | . | Активиран | Activate store and forward | . | Heartbeat | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Настройка | Описание | . | Активиран | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Настройка | Описание | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Качество на въздуха е активирано | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Настройка | Описание | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Съобщения | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Настройка | Описание | . | Активиран | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Настройка | Описание | . | Активиран | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Настройка | Описание | . | Активиран | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 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. | Настройка | Описание | . | Активиран | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Приятелско име | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Настройка | Описание | . | Активиран | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration 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%B0%D1%86%D0%B8%D1%8F-%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#конфигурация-на-модулите" - },"4338": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Почистване на базата данни с възлите . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Рестартиране . Remotely reboot a connected or administered node. Панел за отстраняване на грешки . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#администриране" - },"4339": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4340": { - "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" - },"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. 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" - },"4342": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Opis | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Opis | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Opis | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Opis | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/settings-module-admin.html#module-configuration", - - "relUrl": "/sl-rSI/user/settings-module-admin.html#module-configuration" - },"4343": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Ponovni zagon . Remotely reboot a connected or administered node. 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. 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" - },"4344": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4345": { - "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" - },"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. 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" - },"4347": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descrição | . | Enabled | Toggle MQTT bridge | . | Servidor | MQTT broker address | . | Utilizador | Authentication username | . | Palavra-passe | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descrição | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrição | . | Enabled | Activate store and forward | . | Batimento | Periodically announce this node’s store-and-forward capability | . | Records | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descrição | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrição | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Mensagens | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrição | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descrição | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrição | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrição | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/settings-module-admin.html#module-configuration", - - "relUrl": "/pt-rPT/user/settings-module-admin.html#module-configuration" - },"4348": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reiniciar . Remotely reboot a connected or administered node. 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. 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" - },"4349": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4350": { - "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" - },"4351": { + "relUrl": "/ca-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. 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" - },"4352": { + },"4259": { "doc": "Settings — Modules & Admin", "title": "Module Configuration", "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Апісанне | . | Уключана | Toggle MQTT bridge | . | Сервер | MQTT broker address | . | Імя карыстальніка | Authentication username | . | Пароль | Authentication password | . | Шифравание | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial Module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Апісанне | . | Уключана | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Апісанне | . | Уключана | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Апісанне | . | Уключана | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Апісанне | . | Уключана | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Апісанне | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Апісанне | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Паведамленні | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Апісанне | . | Уключана | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Апісанне | . | Уключана | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Апісанне | . | Уключана | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | Апісанне | . | Уключана | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Апісанне | . | Уключана | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration 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" - },"4353": { + },"4260": { "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Перазагрузіць . Remotely reboot a connected or administered node. Панэль адладкі . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4354": { + },"4261": { "doc": "Settings — Modules & Admin", "title": "Related Topics", "content": ". | Settings — Radio & User — core radio 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" - },"4355": { + },"4262": { "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" - },"4356": { + },"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. 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", + "url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html#settings--modules--admin", - "relUrl": "/pt-rBR/user/settings-module-admin.html#settings--modules--admin" - },"4357": { + "relUrl": "/uk-rUA/user/settings-module-admin.html#settings--modules--admin" + },"4264": { "doc": "Settings — Modules & Admin", "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descrição | . | Enabled | Toggle MQTT bridge | . | Servidor | MQTT broker address | . | Nome de usuário | Authentication username | . | Senha | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descrição | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrição | . | Enabled | Activate store and forward | . | Batimento | Periodically announce this node’s store-and-forward capability | . | Records | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descrição | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrição | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Mensagens | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrição | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descrição | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrição | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrição | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/settings-module-admin.html#module-configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Опис | . | Увімкнено | Toggle MQTT bridge | . | Сервер | MQTT broker address | . | Ім’я користувача | Authentication username | . | Пароль | Authentication password | . | Шифрування | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Режим | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Опис | . | Увімкнено | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Увімкнено | Activate store and forward | . | Пульсація | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Увімкнено | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Опис | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Повідомлення | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | Увімкнено | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Опис | . | Увімкнено | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Увімкнено | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | Опис | . | Увімкнено | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Увімкнено | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html#module-configuration", - "relUrl": "/pt-rBR/user/settings-module-admin.html#module-configuration" - },"4358": { + "relUrl": "/uk-rUA/user/settings-module-admin.html#module-configuration" + },"4265": { "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Limpar Banco de Dados de Nó . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reiniciar . Remotely reboot a connected or administered node. 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. 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", + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Очистити базу даних вузлів . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Перевантажити . Remotely reboot a connected or administered node. Панель налагодження . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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": "/pt-rBR/user/settings-module-admin.html#administração" - },"4359": { + "relUrl": "/uk-rUA/user/settings-module-admin.html#адміністрування" + },"4266": { "doc": "Settings — Modules & Admin", "title": "Related Topics", "content": ". | Settings — Radio & User — core radio 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", + "url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html#related-topics", - "relUrl": "/pt-rBR/user/settings-module-admin.html#related-topics" - },"4360": { + "relUrl": "/uk-rUA/user/settings-module-admin.html#related-topics" + },"4267": { "doc": "Settings — Modules & Admin", "title": "Settings — Modules & Admin", "content": " ", - "url": "/Meshtastic-Android/main/pt-rBR/user/settings-module-admin.html", + "url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html", - "relUrl": "/pt-rBR/user/settings-module-admin.html" - },"4361": { - "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. 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" - },"4362": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Περιγραφή | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Όνομα χρήστη | Authentication username | . | Κωδικός πρόσβασης | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial Module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Περιγραφή | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Περιγραφή | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Περιγραφή | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Περιγραφή | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Περιγραφή | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Περιγραφή | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Μηνύματα | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Περιγραφή | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Περιγραφή | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Περιγραφή | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | Περιγραφή | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Περιγραφή | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/el-rGR/user/settings-module-admin.html#module-configuration", - - "relUrl": "/el-rGR/user/settings-module-admin.html#module-configuration" - },"4363": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Επανεκκίνηση . Remotely reboot a connected or administered node. Πίνακας αποσφαλμάτωσης . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#διαχείριση" - },"4364": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4365": { - "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" - },"4366": { - "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. 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" - },"4367": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descripción | . | Habilitado | Toggle MQTT bridge | . | Servidor | MQTT broker address | . | Usuario | Authentication username | . | Contraseña | Authentication password | . | Cifrado | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Habilitado | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descripción | . | Habilitado | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descripción | . | Habilitado | Activate store and forward | . | Pulso de vida | Periodically announce this node’s store-and-forward capability | . | Registros | 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 . 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 | . | Habilitado | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descripción | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descripción | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Mensajes | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descripción | . | Habilitado | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descripción | . | Habilitado | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descripción | . | Habilitado | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Habilitado | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descripción | . | Habilitado | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/es-rES/user/settings-module-admin.html#module-configuration", - - "relUrl": "/es-rES/user/settings-module-admin.html#module-configuration" - },"4368": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Limpiar nodos de la base de datos . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reiniciar . Remotely reboot a connected or administered node. 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. 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" - },"4369": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4370": { - "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" - },"4371": { - "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. 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" - },"4372": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Açıklaması | . | Açık | Toggle MQTT bridge | . | Sunucu | MQTT broker address | . | Kullanıcı adı | Authentication username | . | Şifre | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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ı | . | Açık | Activate serial communication | . | Echo | Echo received serial data back | . | Mod | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Açıklaması | . | Açık | Activate notifications | . | Uyarı Mesajı | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Aktif | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Açıklaması | . | Açık | Activate store and forward | . | Kalp atışı | Periodically announce this node’s store-and-forward capability | . | Records | Maximum stored messages | . | History Return (max) | Max messages to replay | . | History Return (window) | 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 . 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ı | . | Açık | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Açıklaması | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Açıklaması | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Mesajlar | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Açıklaması | . | Açık | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Açıklaması | . | Açık | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Açıklaması | . | Açık | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 State | 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ı | . | Açık | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Açıklaması | . | Açık | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/settings-module-admin.html#module-configuration", - - "relUrl": "/tr-rTR/user/settings-module-admin.html#module-configuration" - },"4373": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Yeniden başlat . Remotely reboot a connected or administered node. 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. 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" - },"4374": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4375": { - "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" - },"4376": { - "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. 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" - },"4377": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Beskrivelse | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Beskrivelse | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beskrivelse | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Beskrivelse | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beskrivelse | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beskrivelse | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Beskrivelse | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beskrivelse | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beskrivelse | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/no-rNO/user/settings-module-admin.html#module-configuration", - - "relUrl": "/no-rNO/user/settings-module-admin.html#module-configuration" - },"4378": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Omstart . Remotely reboot a connected or administered node. Feilsøkningspanel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4379": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4380": { - "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" - },"4381": { - "doc": "Настройки — Модули и администрирование", - "title": "Настройки — Модули и администрирование", - "content": "Настрой дополнительные функциональные модули и выполняй управление устройством. Модули расширяют Meshtastic с помощью специализированных возможностей — каждый из них можно включать или отключать отдельно. 💡 Совет: Тебе нужно включать только те модули, которые действительно используешь. Отключение неиспользуемых модулей снижает время передачи, экономит батарею и упрощает конфигурацию. Настройки модулей используют макет на основе карточек с переключателями, выпадающими списками, текстовыми полями и ползунками: . . ", - "url": "/Meshtastic-Android/main/ru-rRU/user/settings-module-admin.html", - - "relUrl": "/ru-rRU/user/settings-module-admin.html" - },"4382": { - "doc": "Настройки — Модули и администрирование", - "title": "Конфигурация модуля", - "content": "Модуль MQTT . Мосты передают сообщения туда и обратно от брокера MQTT для подключения к интернету. Ты так расширишь сеть за пределы радиуса действия или интегрируешь её с системами домашней автоматизации. | Настройка | Описание | . | Включено | Переключить MQTT мост | . | Сервер | Адрес MQTT брокера | . | Имя пользователя | Имя пользователя для аутентификации | . | Пароль | Пароль аутентификации | . | Шифрование | Зашифровать MQTT-пейлоады | . | Вывод JSON | ⚠️ Устарело — поддержка JSON удалена из прошивки; поле игнорируется | . | TLS | Использовать защищённое соединение | . | Корневая тема | Базовый путь темы MQTT | . | Отчет карты | Опубликовать позицию на публичной карте | . См. MQTT для подробного руководства по использованию, включая шифрование, конфиденциальность и настройку брокера. Последовательный модуль . Позволяет общаться через последовательный порт с внешними устройствами (GPS-модулями, датчиками или собственной техникой). Когда включено, последовательный порт ноды может отправлять и получать данные в формате protobuf или текст, что позволяет внешним микроконтроллерам или компьютерам взаимодействовать с сетью. | Настройка | Описание | . | Включено | Включить последовательное соединение | . | Эхо | Echo получил обратно последовательные данные | . | Режим обмена | Вывод в формате текста, Protobuf или NMEA | . | Пины RX/TX | GPIO-пины для последовательного соединения | . | Скорость передачи (бод) | Скорость последовательного соединения | . Модуль внешних уведомлений . Управляет зуммером, светодиодом или вибрацией на вашем радиооборудовании. Полезно для устройств, которым нужно физически сигнализировать о приходе сообщения — особенно удобно для неоснащенных персоналом или уличных установок. | Настройка | Описание | . | Включено | Включить уведомления | . | Включить уведомление о входящем сообщении | Уведомлять о входящих сообщениях | . | Зуммер при уведомлении | Использовать буззер для сообщений | . | Вибрация при уведомлении | Использовать вибрацию для сообщений | . | Уведомлять при 🔔 | Уведомлять о символе колокола | . | Вывод (GPIO) | Пин для вывода уведомления | . | Активный выход | Высокая или низкая активность | . | Длительность (мс) | Длительность уведомления | . | Использовать I2S как буззер | Использовать аудиовывод I2S | . Модуль Store & Forward . Буферизирует сообщения для узлов, которые временно были недоступны, а затем ретранслирует их, когда эти узлы переподключаются. Важное значение для сеток, где узлы входят и выходят вне диапазона регулярно - обеспечивает отсутствие потери сообщений при коротких разъединениях. | Настройка | Описание | . | Включено | Активировать режим хранения и пересылки | . | Heartbeat | Периодически объявлять о наличии функции хранения и пересылки у этого узла | . | Записи | Максимальное количество сохраненных сообщений | . | История возврата (макс) | Максимум сообщений для повтора | . | Возврат истории (окно) | Окно времени для повтора | . | Сервер | Действовать как сервер хранения и пересылки для mesh-сети (требуется большой объем памяти, например, ESP32 с PSRAM) | . 💡 Совет: Хранение и пересылка лучше всего работает на узлах с достаточной памятью (ESP32 с PSRAM). Узлы маршрутизатора являются идеальными кандидатами, так как они обычно всегда включены. Модуль проверки дальности . Автоматизированный инструмент для проверки дальности и оценки качества связи между нодами. Когда включено, нода периодически отправляет сообщения с увеличивающимся счетчиком. Приёмная нода записывает эти сообщения, что позволяет тебе уйти пешком или уехать на машине, а потом проанализировать, на каком расстоянии сообщения перестали приходить. | Настройка | Описание | . | Включено | Активировать проверку дальности | . | Интервал отправки (с) | Время между передачами проверок | . | Сохранить в CSV | Журнал полученных тестовых данных на SD-карту | . Модуль телеметрии . Контролирует какими телеметрическими данными ваш узел делится с сеткой. Телеметрия включает данные о состоянии устройства (заряд батареи, время работы) и данные с датчиков окружающей среды (температура, влажность, давление). | Настройка | Описание | . | Интервал обновления метрик устройства | Как часто сообщать о показателях устройства | . | Интервал обновления метрик среды | Как часто сообщать о датчиках окружающей среды | . | Телеметрия воздуха | Сообщить данные датчика частиц | . | Включены метрики энергии | Сообщать об энергопотреблении | . Посмотрите Телеметрия и датчики — для получения информации о поддерживаемых датчиках и рекомендациях по настройке. Модуль шаблонных сообщений . Предварительно настроенные сообщения, доступные через физические кнопки устройства (для радиостанций с поворотными энкодерами, кнопочными панелями или аналогичным оборудованием ввода). Определите список быстрых сообщений, которые могут быть переданы без подключённого телефона — идеально подходит для использования в поле. | Настройка | Описание | . | Включено | ⚠️ Устарело — текущая прошивка может игнорировать этот переключатель | . | Сообщения | Список сообщений, разделённых новой строкой | . | Отправлять 🔔 | Воспроизвести звук колокола при отправке | . | Поворотный энкодер | Включить ввод поворотного энкодера | . | Пины поворота и нажатия | Задания GPIO PIN-кода для ввода | . Звуковой модуль . Поддержка аудио Codec2 для низкополосной голосовой связи через сетку. Это экспериментальная функция, которая кодирует голос в очень маленькие пакеты данных с помощью кодека Codec2. | Настройка | Описание | . | Включено | Активировать модуль аудио | . | Частота кодирования | Компромисс между качеством звука и полосой пропускания | . | Выбор слов I2S | GPIO контакт для I2S WS | . | I2S Вход данных | Пин GPIO для I2S DIN | . | I2S Выход данных | Пин GPIO для I2S DOUT | . ⚠️ Примечание: Для работы аудио требуется специальное аппаратное обеспечение (I2S-микрофон и динамик). Качество голоса очень низкополосное — представьте себе «разборчивую радиосвязь», а не качество телефонного звонка. Удаленный аппаратный модуль . Управление GPIO через mesh-сеть. Позволяет удалённому узлу читать и записывать состояния выводов GPIO на другом узле — полезно для активации реле, опроса переключателей или удалённого управления внешним оборудованием. | Настройка | Описание | . | Включено | Активировать удаленный GPIO доступ | . | Разрешить неопределенные пины | Разрешить доступ к любому GPIO-пину (риск для безопасности) | . | Доступные пины | До 4 пинов GPIO, которые этот узел предоставляет для удалённого чтения и записи | . ⚠️ Предупреждение: Включение опции «Разрешить неопределённые пины» даёт удалённым узлам доступ ко всем выводам GPIO, что может нарушить работу собственного аппаратного обеспечения радио. Включать только на выделенных GPIO-нодах. Модуль информации о соседях . Транслирует информацию о доступных услышанных соседей, включив ячейку сеточной топологии. Каждый включенный узел периодически делится списком других узлов которые он может слышать и их качество сигнала. | Настройка | Описание | . | Включено | Включить трансляцию соседей | . | Интервал обновления (с) | Как часто транслировать список соседей | . | Передача через LoRa | Также транслировать информацию соседей по LoRa, а не только MQTT/телефон. Недоступно на канале используя ключ по умолчанию и имя | . Смотрите Discovery за тем как использовать соседние данные для сеточно топологического исследования. Модуль окружающего освещения . Управляет встроенными светодиодами NeoPixel или другими адресуемыми RGB-светодиодами на поддерживаемом оборудовании. Может использоваться для визуальных статусовых индикаторов, световых уведомлений, или декоративных эффектов. | Настройка | Описание | . | Состояние светодиода | Включить или выключить светодиод | . | Ток | Текущий лимит светодиодов (0–31) | . | Красный / Зеленый / Синий | Индивидуальные значения цветов канала (0–255) | . Модуль определения датчика . Превращает ваш узел в систему сигнализации на основе датчика движения или открытия двери. При обнаружении изменения состояния на выводе GPIO (например, сработал датчик движения или открылась дверь) узел отправляет по меш-сети оповещение. | Настройка | Описание | . | Включено | Активировать датчик обнаружения | . | Пин датчика | Пин GPIO, подключенный к датчику | . | Триггер срабатывания | Как состояние пина интерпретируется как событие обнаружения (например, активный высокий/низкий уровень, срабатывание по фронту) | . | Использовать режим подтяжки входа | Включить внутренний подтягивающий резистор пина | . | Минимальное количество трансляций (с) | Минимальный интервал между оповещениями | . | Трансляция состояния (с) | Интервал периодической отправки состояния | . | Отправлять 🔔 | Включать символ колокола в оповещения | . | Имя датчика | Пользовательское имя для этого датчика | . Paxcounter Модуль . Подсчёт количества людей по Wi-Fi и BLE-запросам от устройств. Засчитывает ближайшие устройства, пассивно прослушивая зондирующие запросы, чтобы телефоны и ноутбуки излучали при сканировании сетей. Доступно только на устройствах ESP32. | Настройка | Описание | . | Включено | Активировать подсчет людей | . | Интервал обновления (с) | Как часто сообщать подсчитывания | . 💡 Совет: Paxcounter полезен для приблизительной оценки пешеходного потока в местах начала маршрутов, на мероприятийных площадках или в других локациях. Счетчики приблизительны — один человек может иметь несколько устройств. Модуль TAK . Интеграция Team Awareness Kit для совместимости с ATAK и WinTAK. См. TAK Integration для детальной настройки и использования. ", - "url": "/Meshtastic-Android/main/ru-rRU/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%8F-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D1%8F", - - "relUrl": "/ru-rRU/user/settings-module-admin.html#конфигурация-модуля" - },"4383": { - "doc": "Настройки — Модули и администрирование", - "title": "Администрирование", - "content": "Удаленное администрирование . Удалённо настраивай ноды, которые используют твой ключ администрирования: . | Выбери целевую ноду в списке нод. | Перейди в Настройки этой ноды. | Измени конфигурацию. | Нажми Сохранить — изменения отправляются через сеть. | . ⚠️ Требуется: Ключ администратора настроенный как на вашем узле, так и на целевом узле. Очистить базу данных нод . Удаляет устаревшие узлы из локальной базы данных, которые не были услышаны в настраиваемом окне времени. Сброс к заводским настройкам . Сбрасывает все настройки к заводским. Это действие нельзя отменить. Перезагрузка . Удаленно перезагрузить подключенный или управляемый узел. Панель отладки . Открывает вкладки Пакет и Журналы приложений для просмотра, фильтрации и экспорта диагностических выходов. См. Отладочные журналы для полного прохождения. Устранение неполадок удалённого администрирования . | “Нет ответа от целевого узла” — цель может находиться вне диапазона, в автономном режиме или иметь несоответствующий ключ администратора. Проверьте соответствие ключа администратора на обоих узлах. | Изменения не применены — чтобы некоторые настройки вступили в силу, нужно перезагрузить устройство. Попробуй перезагрузить после сохранения. | Не видны настройки удалённой ноды — убедись, что твоя нода имеет админ-ключ для целевой ноды. Админ-канал настраивается автоматически, когда задан ключ администратора. | . ", - "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#администрирование" - },"4384": { - "doc": "Настройки — Модули и администрирование", - "title": "Связанные темы", - "content": ". | Настройки — Радио и Пользователь — основные настройки радио и профиля пользователя | Ссылка на конфигурацию модуля — подробная документация по модулям на 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#связанные-темы" - },"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. 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" - },"4386": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Beschrijving | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Gebruikersnaam | Authentication username | . | Wachtwoord | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Beschrijving | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beschrijving | . | Enabled | Activate store and forward | . | Hartslag | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Beschrijving | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beschrijving | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Berichten | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beschrijving | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Beschrijving | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beschrijving | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 State | 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beschrijving | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/settings-module-admin.html#module-configuration", - - "relUrl": "/nl-rNL/user/settings-module-admin.html#module-configuration" - },"4387": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Herstart . Remotely reboot a connected or administered node. Debug-paneel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4388": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4389": { - "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" - },"4390": { - "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. 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" - },"4391": { - "doc": "Sätted - moodulid & admin", - "title": "Mooduli konf", - "content": "MQTT moodul . Sildab võrgusõnumeid MQTT vahendajasse ja sealt internetiühenduse loomiseks. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Sätted | Kirjeldus | . | Lubatud | Lükka MQTT sild sisse | . | Server | MQTT vahendaja aadress | . | Kasutajatunnus | Authentication username | . | Parool | Authentication password | . | Encryption | Krüpteeri MQTT kasutus | . | JSON Output | ⚠️ Vananenud — JSON tugi püsivarast eemaldatud; välja ignoreeritakse | . | TLS | Use secure connection | . | Root Topic | Baas MQTT teema teekond | . | Kaardiaruanne | Avalda asukoht avalikul kaardil | . Vaata MQTT üksikasjalikumat kasutusjuhendit, mis sisaldab teavet krüpteerimise, privaatsuse ja vahendaja seadistamise kohta,. Jadapordi moodul . 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 | . | Lubatud | Aktiveeri jadapordi ühendus | . | Echo | Kaja sai jadaandmed tagasi | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX kontaktid | GPIO sisend jagaühenduseks | . | Baud Rate | Jadaühenduse kiirus | . Välise teavitusmoodul . Juhib raadio riistvara summeri-, LED- või vibratsioonihoiatusi. Kasulik seadmetele, mis peavad sõnumi saabumisest füüsiliselt märku andma – eriti kasulik järelevalveta või välistingimustes paigaldamise korral. | Sätted | Kirjeldus | . | Lubatud | Aktiveeri märguanded | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Hoiatuskell | Teavita hoiatuskella märgist | . | Väljund (GPIO) | Sisend teavitusväljundi jaoks | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Salvesta & edasta moodul . 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. | Sätted | Kirjeldus | . | Lubatud | Aktiveeri salvesta ja saada | . | Südamelöögid | Periodically announce this node’s store-and-forward capability | . | 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) | . 💡 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. Kaugustesti moodul . 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 | . | Lubatud | Aktiveeri levi test | . | Sender Interval (s) | Time between test transmissions | . | Salvesta CSV | Log received test data to SD card | . Telemeetria moodul . Controls what telemetry data your node shares with the mesh. Telemeetria sisaldab seadme tervist (aku, tööaeg) ja keskkonnaandurite andmeid (temperatuur, niiskus, rõhk). | Sätted | Kirjeldus | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . Vaata Telemeetria & Sensorid toetatud andurite ja sätete soovituste kohta. Eelsalvestatud sõnumi moodul . Seadme füüsiliste nuppude kaudu ligipääsetavad eelseadistatud sõnumid (pöördnuppude, klaviatuuride või sarnase sisendriistvaraga raadiote puhul). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Sätted | Kirjeldus | . | Lubatud | ⚠️ Vananenud — praegune püsivara võib seda lülitit ignoreerida | . | Sõnumid | Newline-separated list of messages | . | Saada kelluke | Esita saatmisel kellukese heli | . | Rotary Encoder | Enable rotary encoder input | . | Üles/alla/vajuta sisend | GPIO sisendi kontaktide määramine | . Audio moodul . 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 | . | Lubatud | Aktiveeri audio moodul | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO sisend I2S WS jaoks | . | I2S Data In | GPIO sisend I2S DIN jaoks | . | I2S Data Out | GPIO sisend I2S DOUT jaoks | . ⚠️ Märkus: Heli jaoks on vaja spetsiaalset riistvara (I2S mikrofon ja kõlar). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Kaugriistvara moodul . 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. | Sätted | Kirjeldus | . | Lubatud | Aktiveeri kaugjuurdepääs GPIO-le | . | Luba määratlemata sisendid | Luba juurdepääs mis tahes GPIO sisendile (turvarisk) | . | Available Pins | Kuni 4 GPIO sisendit, mida see sõlm kauglugemiseks/-kirjutamiseks avab | . ⚠️ Hoiatus: Funktsiooni „Luba määratlemata sisendkontaktid” lubamine annab kaugsõlmedele juurdepääsu kõigile GPIO sisendile, mis võib häirida raadio enda riistvara. Luba ainult spetsiaalsetel GPIO sõlmedel. Naabriinfo moodul . 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 | . | Lubatud | Aktiveeri naabrite leviring | . | Värskendusintervall(id) | Kui tihti naabrite nimekirja levitada | . | Transmit Over LoRa | Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval | . Vaata Avasta kuidas kasutada naabri-andmeid kärgvõrgu topoloogia uurimiseks. Ambientvalguse moodul . Juhib toetatud riistvaral NeoPixeli või muid adresseeritavaid RGB LEDe. Can be used for visual status indicators, notification lights, or decorative effects. | Sätted | Kirjeldus | . | LED olek | Turn the LED on or off | . | Pinge | LED current limit (0–31) | . | Red / Green / Blue | Individuaalsete värvikanalite väärtused (0–255) | . Tuvastusanduri moodul . Turns your node into a motion or door sensor alert system. Kui GPIO sisend tuvastab oleku muutuse (liikumine tuvastatud, uks avatud), levitab sõlm kärgvõrgu kaudu hoiatusteate. | Sätted | Kirjeldus | . | Lubatud | Aktiveeri tuvastusandur | . | Ekraani sisend | GPIO sisend on anduriga ühendatud | . | Detection Trigger Type | Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav) | . | Use Input Pullup Mode | Enable the pin’s internal pull-up resistor | . | Minimaalne leviring(id) | Minimaalne aeg hoiatusteadete levitamisel | . | Riiklik ringhääling(ud) | Perioodilise oleku levitamise intervall | . | Saada hoiatuskell | Lisa märguannetesse hoiatuskella sümbol | . | Friendly Name | Selle anduri kohandatud nimi | . Paxloenduri moodul . Inimeste loendur WiFi ja BLE päringute abil. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Sätted | Kirjeldus | . | Lubatud | Aktiveeri inimeste loendamine | . | Värskendusintervall(id) | How often to report counts | . 💡 Vihje: Paxloendur on kasulik jalakäijate liikluse hindamiseks matkaradade alguses, ürituste toimumiskohtades või muudes kohtades. Counts are approximate — one person may carry multiple devices. TAK moodul . Meeskonna teadlikkuse komplekti integratsioon ATAKi ja WinTAKi koostalitlusvõime tagamiseks. Vaata TAK Integration täpsema seadistamise ja kasutamise kohta. ", - "url": "/Meshtastic-Android/main/et-rEE/user/settings-module-admin.html#mooduli-konf", - - "relUrl": "/et-rEE/user/settings-module-admin.html#mooduli-konf" - },"4392": { - "doc": "Sätted - moodulid & admin", - "title": "Haldus", - "content": "Kaughaldus . Administraatori võtit jagavate sõlmede kaugkonfigureerimine: . | Select the target node in the node list. | Mine selle sõlme Seadetesse. | Muuda seadistust. | Puuduta Salvesta – muudatused saadetakse kärgvõrgu kaudu. | . ⚠️ Nõutud: Administraatori võtit, mis on seadistatud nii sinu kui ka sihtsõlmes. Tühjenda sõlmede andmebaas . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Taastab kõik seaded tehase vaikeväärtustele. Seda ei saa tagasi võtta. Taaskäivita . Ühendatud või hallatava sõlme kaugkäivitamine. Arendaja paneel . Avab vahekaardid Paketid ja Rakenduse logid diagnostilise väljundi vaatamiseks, filtreerimiseks ja eksportimiseks. See Debug Logs for the full walkthrough. Kaug-admin tõrkeotsing . | “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" - },"4393": { - "doc": "Sätted - moodulid & admin", - "title": "Related Topics", - "content": ". | Seaded — Raadio ja kasutaja — raadio ja kasutajaprofiili põhiseaded | 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#related-topics", - - "relUrl": "/et-rEE/user/settings-module-admin.html#related-topics" - },"4394": { - "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" - },"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. 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" - },"4396": { - "doc": "Settings — Modules & Admin", - "title": "Configurazione modulo", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Impostazione | Descrizione | . | Abilitato | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Cifratura | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Abilitato | Activate serial communication | . | Echo | Echo received serial data back | . | Modalità | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Impostazione | Descrizione | . | Abilitato | Activate notifications | . | Messaggio di allerta | Notify on incoming messages | . | Buzzer Messaggio Di Allerta | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Campanella Di Allarme | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Attivo | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Impostazione | Descrizione | . | Abilitato | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Record | 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 . 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 | . | Abilitato | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Impostazione | Descrizione | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Qualità Dell’Aria Abilitata | Report particulate sensor data | . | Metriche Di Alimentazione Abilitate | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Impostazione | Descrizione | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messaggi | Newline-separated list of messages | . | Invia Campanella | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Impostazione | Descrizione | . | Abilitato | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | Selezione Parola I2S | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Impostazione | Descrizione | . | Abilitato | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Impostazione | Descrizione | . | Abilitato | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Stato LED | 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 | . | Abilitato | Activate detection sensor | . | Pin 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Invia Campanella | Include bell character in alerts | . | Nome Descrittivo | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Impostazione | Descrizione | . | Abilitato | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/it-rIT/user/settings-module-admin.html#configurazione-modulo", - - "relUrl": "/it-rIT/user/settings-module-admin.html#configurazione-modulo" - },"4397": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Azzera il database dei nodi . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Riavvia . Remotely reboot a connected or administered node. Pannello Di Debug . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4398": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4399": { - "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" - },"4400": { - "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. 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" - },"4401": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | الوصف | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial Module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | الوصف | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | الوصف | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | الوصف | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | الوصف | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | الوصف | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | الوصف | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | الرسائل | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | الوصف | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | الوصف | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | الوصف | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | الوصف | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | الوصف | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/settings-module-admin.html#module-configuration", - - "relUrl": "/ar-rSA/user/settings-module-admin.html#module-configuration" - },"4402": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. إعادة التشغيل . Remotely reboot a connected or administered node. Debug Panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#الإدارة" - },"4403": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4404": { - "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" - },"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. 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" - },"4406": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Popis | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Používateľské meno | Authentication username | . | Heslo | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Popis | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Popis | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Popis | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Popis | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Správy | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Popis | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Popis | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Popis | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Popis | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/settings-module-admin.html#module-configuration", - - "relUrl": "/sk-rSK/user/settings-module-admin.html#module-configuration" - },"4407": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reštartovať . Remotely reboot a connected or administered node. Debug okno . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4408": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4409": { - "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" - },"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. 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" - },"4411": { - "doc": "Settings — Modules & Admin", - "title": "Konfiguracja modułu", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Opis | . | Włączony | Toggle MQTT bridge | . | Serwer | MQTT broker address | . | Nazwa użytkownika | Authentication username | . | Hasło | Authentication password | . | Szyfrowanie | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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łączony | Activate serial communication | . | Echo | Echo received serial data back | . | Tryb | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Opis | . | Włączony | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Włączony | Activate store and forward | . | Bicie serca | Periodically announce this node’s store-and-forward capability | . | Wpisów | Maximum stored messages | . | History Return (max) | Max messages to replay | . | History Return (window) | 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 . 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 | . | Włączony | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Opis | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Wiadomości | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | Włączony | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Opis | . | Włączony | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Włączony | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Włączony | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Włączony | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/settings-module-admin.html#konfiguracja-modu%C5%82u", - - "relUrl": "/pl-rPL/user/settings-module-admin.html#konfiguracja-modułu" - },"4412": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Wyczyść bazę węzłów . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Uruchom ponownie . Remotely reboot a connected or administered node. Panel debugowania . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" - },"4413": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4414": { - "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" - },"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. 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" - },"4416": { - "doc": "Settings — Modules & Admin", - "title": "模組設定", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | 設定 | 描述說明 | . | 已啟用 | Toggle MQTT bridge | . | 伺服器 | MQTT broker address | . | 使用者名稱 | Authentication username | . | 密碼 | Authentication password | . | 加密 | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | 根主題 | Base MQTT topic path | . | Map Report | Publish position for public map | . 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 | . | 模式 | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | 鮑率 | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | 設定 | 描述說明 | . | 已啟用 | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | 設定 | 描述說明 | . | 已啟用 | Activate store and forward | . | 心跳 | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | 設定 | 描述說明 | . | 已啟用 | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | 設定 | 描述說明 | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | 空氣品質已啟用 | Report particulate sensor data | . | 已啟用電源量測指標 | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | 設定 | 描述說明 | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | 訊息 | Newline-separated list of messages | . | 傳送 Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | 設定 | 描述說明 | . | 已啟用 | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S 字元選擇 | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | 設定 | 描述說明 | . | 已啟用 | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | 設定 | 描述說明 | . | 已啟用 | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | 透過 LoRa 傳輸 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | 傳送 Bell | Include bell character in alerts | . | 友善名稱 | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | 設定 | 描述說明 | . | 已啟用 | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration 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#模組設定" - },"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. | . ⚠️ Requires: Admin key configured on both your node and the target node. 清除節點資料庫 . Removes stale nodes from your local database that haven’t been heard in a configurable time window. 恢復原廠設定 . Resets all settings to factory defaults. This cannot be undone. 重新開機 . Remotely reboot a connected or administered node. 偵錯面板 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#管理" - },"4418": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4419": { - "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" - },"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. 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" - },"4421": { - "doc": "Settings — Modules & Admin", - "title": "Module Configuration", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Nastavení | Popis | . | Povoleno | Toggle MQTT bridge | . | Server | MQTT broker address | . | Uživatelské jméno | Authentication username | . | Heslo | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Kořenové téma | Base MQTT topic path | . | Map Report | Publish position for public map | . 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 | . | Povoleno | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Nastavení | Popis | . | Povoleno | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Nastavení | Popis | . | Povoleno | Activate store and forward | . | Pulzující LED | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Povoleno | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Nastavení | Popis | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Nastavení | Popis | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Zprávy | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Nastavení | Popis | . | Povoleno | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Nastavení | Popis | . | Povoleno | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Nastavení | Popis | . | Povoleno | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Povoleno | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Nastavení | Popis | . | Povoleno | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-module-admin.html#module-configuration", - - "relUrl": "/cs-rCZ/user/settings-module-admin.html#module-configuration" - },"4422": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Vyčistit databázi uzlů . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Restartovat . Remotely reboot a connected or administered node. 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. 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" - },"4423": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4424": { - "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" - },"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. 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" - },"4426": { - "doc": "Settings — Modules & Admin", - "title": "Configuration du module", - "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Description | . | Activé | Toggle MQTT bridge | . | Serveur | MQTT broker address | . | Nom d’utilisateur | Authentication username | . | Mot de passe | Authentication password | . | Chiffrement | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Activé | Activate serial communication | . | Écho | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Vitesse en bauds | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Description | . | Activé | Activate notifications | . | Message d’alerte | Notify on incoming messages | . | Message d’alerte buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Bip d’alerte | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Actif | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Description | . | Activé | Activate store and forward | . | Battement de cœur (heartbeat) | Periodically announce this node’s store-and-forward capability | . | Enregistrements | Maximum stored messages | . | History Return (max) | Max messages to replay | . | History Return (window) | 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 . 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 | . | Activé | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Description | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Qualité de l’air activée | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Description | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Envoyer un bip | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Description | . | Activé | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Description | . | Activé | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Description | . | Activé | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 des 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 | . | Activé | Activate detection sensor | . | Broche de monitoring | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Envoyer un bip | Include bell character in alerts | . | Nom convivial | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Description | . | Activé | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/settings-module-admin.html#configuration-du-module", - - "relUrl": "/fr-rFR/user/settings-module-admin.html#configuration-du-module" - },"4427": { - "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Nettoyer la base de données des nœuds . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Redémarrer . Remotely reboot a connected or administered node. 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. 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" - },"4428": { - "doc": "Settings — Modules & Admin", - "title": "Related Topics", - "content": ". | Settings — Radio & User — core radio 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" - },"4429": { - "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" - },"4430": { + "relUrl": "/uk-rUA/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. 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" - },"4431": { + },"4269": { "doc": "Settings — Modules & Admin", "title": "模块配置", "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | 说明 | . | Enabled | Toggle MQTT bridge | . | 服务器 | MQTT broker address | . | 用户名称 | Authentication username | . | 密码 | Authentication password | . | 加密 | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | 地图报告 | Publish position for public map | . 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 | 说明 | . | Enabled | Activate serial communication | . | 回声 | Echo received serial data back | . | 模式 | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | 波特率 | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | 说明 | . | Enabled | Activate notifications | . | 提醒消息 | Notify on incoming messages | . | 警告消息蜂鸣 | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | 提醒铃声 | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | 启用 | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | 说明 | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | 说明 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | 说明 | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | 启用空气质量检测 | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | 说明 | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | 消息 | Newline-separated list of messages | . | 发送铃声 | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | 说明 | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | 说明 | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | 说明 | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | 说明 | . | Enabled | Activate detection sensor | . | 监视器 | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | 发送铃声 | Include bell character in alerts | . | 友好名称 | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | 说明 | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/zh-rCN/user/settings-module-admin.html#%E6%A8%A1%E5%9D%97%E9%85%8D%E7%BD%AE", "relUrl": "/zh-rCN/user/settings-module-admin.html#模块配置" - },"4432": { + },"4270": { "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. 清理节点数据库 . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. 重启 . Remotely reboot a connected or administered node. 调试面板 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#管理员" - },"4433": { + },"4271": { "doc": "Settings — Modules & Admin", "title": "Related Topics", "content": ". | Settings — Radio & User — core radio 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" - },"4434": { + },"4272": { "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" - },"4435": { + },"4273": { + "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. 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" + },"4274": { + "doc": "Settings — Modules & Admin", + "title": "Конфигурация на модулите", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Настройка | Описание | . | Активиран | Toggle MQTT bridge | . | Сървър | MQTT broker address | . | Потребителско име | Authentication username | . | Парола | Authentication password | . | Криптиране | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial Module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Настройка | Описание | . | Активиран | Activate serial communication | . | Ехо | Echo received serial data back | . | Режим | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Настройка | Описание | . | Активиран | Activate notifications | . | Предупредително съобщение | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Активно | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Настройка | Описание | . | Активиран | Activate store and forward | . | Heartbeat | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Настройка | Описание | . | Активиран | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Настройка | Описание | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Качество на въздуха е активирано | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Настройка | Описание | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Съобщения | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Настройка | Описание | . | Активиран | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Настройка | Описание | . | Активиран | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Настройка | Описание | . | Активиран | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 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. | Настройка | Описание | . | Активиран | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Приятелско име | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Настройка | Описание | . | Активиран | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration 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%B0%D1%86%D0%B8%D1%8F-%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#конфигурация-на-модулите" + },"4275": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Почистване на базата данни с възлите . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Рестартиране . Remotely reboot a connected or administered node. Панел за отстраняване на грешки . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#администриране" + },"4276": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4277": { + "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" + },"4278": { + "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. 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" + },"4279": { + "doc": "Settings — Modules & Admin", + "title": "模組設定", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | 設定 | 描述說明 | . | 已啟用 | Toggle MQTT bridge | . | 伺服器 | MQTT broker address | . | 使用者名稱 | Authentication username | . | 密碼 | Authentication password | . | 加密 | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | 根主題 | Base MQTT topic path | . | Map Report | Publish position for public map | . 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 | . | 模式 | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | 鮑率 | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | 設定 | 描述說明 | . | 已啟用 | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | 設定 | 描述說明 | . | 已啟用 | Activate store and forward | . | 心跳 | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | 設定 | 描述說明 | . | 已啟用 | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | 設定 | 描述說明 | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | 空氣品質已啟用 | Report particulate sensor data | . | 已啟用電源量測指標 | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | 設定 | 描述說明 | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | 訊息 | Newline-separated list of messages | . | 傳送 Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | 設定 | 描述說明 | . | 已啟用 | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S 字元選擇 | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | 設定 | 描述說明 | . | 已啟用 | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | 設定 | 描述說明 | . | 已啟用 | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | 透過 LoRa 傳輸 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | 傳送 Bell | Include bell character in alerts | . | 友善名稱 | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | 設定 | 描述說明 | . | 已啟用 | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration 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#模組設定" + },"4280": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. 清除節點資料庫 . Removes stale nodes from your local database that haven’t been heard in a configurable time window. 恢復原廠設定 . Resets all settings to factory defaults. This cannot be undone. 重新開機 . Remotely reboot a connected or administered node. 偵錯面板 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#管理" + },"4281": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4282": { + "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" + },"4283": { + "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. 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" + },"4284": { + "doc": "Settings — Modules & Admin", + "title": "Конфигурација модула", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Опис | . | Омогућено | Toggle MQTT bridge | . | Сервер | MQTT broker address | . | Корисничко име | Authentication username | . | Лозинка | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Корен тема | Base MQTT topic path | . | Извештај мапе | Publish position for public map | . 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 | . | Мод | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Опис | . | Омогућено | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Активан | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Омогућено | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Омогућено | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Опис | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Поруке | Newline-separated list of messages | . | Пошаљи звоно | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | Омогућено | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Опис | . | Омогућено | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Омогућено | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Пошаљи звоно | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Омогућено | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration 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#конфигурација-модула" + },"4285": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Ресетовање на фабричка подешавања . Resets all settings to factory defaults. This cannot be undone. Поново покрени . Remotely reboot a connected or administered node. 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. 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" + },"4286": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4287": { + "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" + },"4288": { + "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. 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" + },"4289": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Nastavení | Popis | . | Povoleno | Toggle MQTT bridge | . | Server | MQTT broker address | . | Uživatelské jméno | Authentication username | . | Heslo | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Kořenové téma | Base MQTT topic path | . | Map Report | Publish position for public map | . 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 | . | Povoleno | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Nastavení | Popis | . | Povoleno | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Nastavení | Popis | . | Povoleno | Activate store and forward | . | Pulzující LED | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Povoleno | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Nastavení | Popis | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Nastavení | Popis | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Zprávy | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Nastavení | Popis | . | Povoleno | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Nastavení | Popis | . | Povoleno | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Nastavení | Popis | . | Povoleno | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Povoleno | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Nastavení | Popis | . | Povoleno | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-module-admin.html#module-configuration", + + "relUrl": "/cs-rCZ/user/settings-module-admin.html#module-configuration" + },"4290": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Vyčistit databázi uzlů . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Restartovat . Remotely reboot a connected or administered node. 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. 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" + },"4291": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4292": { + "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" + },"4293": { + "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. 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" + },"4294": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Description | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Description | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Description | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Description | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Description | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Description | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Description | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Description | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Description | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration 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" + },"4295": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reboot . Remotely reboot a connected or administered node. Debug Panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" + },"4296": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4297": { + "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" + },"4298": { + "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. 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" + },"4299": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Opis | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Opis | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Opis | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Opis | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/settings-module-admin.html#module-configuration", + + "relUrl": "/sl-rSI/user/settings-module-admin.html#module-configuration" + },"4300": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Ponovni zagon . Remotely reboot a connected or administered node. 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. 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" + },"4301": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4302": { + "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" + },"4303": { + "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. 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" + },"4304": { + "doc": "Settings — Modules & Admin", + "title": "Configurazione modulo", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Impostazione | Descrizione | . | Abilitato | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Cifratura | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Abilitato | Activate serial communication | . | Echo | Echo received serial data back | . | Modalità | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Impostazione | Descrizione | . | Abilitato | Activate notifications | . | Messaggio di allerta | Notify on incoming messages | . | Buzzer Messaggio Di Allerta | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Campanella Di Allarme | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Attivo | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Impostazione | Descrizione | . | Abilitato | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Record | 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 . 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 | . | Abilitato | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Impostazione | Descrizione | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Qualità Dell’Aria Abilitata | Report particulate sensor data | . | Metriche Di Alimentazione Abilitate | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Impostazione | Descrizione | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messaggi | Newline-separated list of messages | . | Invia Campanella | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Impostazione | Descrizione | . | Abilitato | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | Selezione Parola I2S | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Impostazione | Descrizione | . | Abilitato | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Impostazione | Descrizione | . | Abilitato | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Stato LED | 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 | . | Abilitato | Activate detection sensor | . | Pin 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Invia Campanella | Include bell character in alerts | . | Nome Descrittivo | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Impostazione | Descrizione | . | Abilitato | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/it-rIT/user/settings-module-admin.html#configurazione-modulo", + + "relUrl": "/it-rIT/user/settings-module-admin.html#configurazione-modulo" + },"4305": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Azzera il database dei nodi . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Riavvia . Remotely reboot a connected or administered node. Pannello Di Debug . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" + },"4306": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4307": { + "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" + },"4308": { + "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. 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" + },"4309": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descrição | . | Enabled | Toggle MQTT bridge | . | Servidor | MQTT broker address | . | Nome de usuário | Authentication username | . | Senha | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descrição | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrição | . | Enabled | Activate store and forward | . | Batimento | Periodically announce this node’s store-and-forward capability | . | Records | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descrição | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrição | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Mensagens | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrição | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descrição | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrição | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrição | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/settings-module-admin.html#module-configuration", + + "relUrl": "/pt-rBR/user/settings-module-admin.html#module-configuration" + },"4310": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Limpar Banco de Dados de Nó . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reiniciar . Remotely reboot a connected or administered node. 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. 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" + },"4311": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4312": { + "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" + },"4313": { + "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. 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" + },"4314": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Lýsing | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Lýsing | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Lýsing | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Lýsing | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Lýsing | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Lýsing | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Lýsing | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Lýsing | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Lýsing | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/is-rIS/user/settings-module-admin.html#module-configuration", + + "relUrl": "/is-rIS/user/settings-module-admin.html#module-configuration" + },"4315": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Endurræsa . Remotely reboot a connected or administered node. Villuleitarborð . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" + },"4316": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4317": { + "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" + },"4318": { + "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. 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" + },"4319": { + "doc": "Settings — Modules & Admin", + "title": "Configuration du module", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Description | . | Activé | Toggle MQTT bridge | . | Serveur | MQTT broker address | . | Nom d’utilisateur | Authentication username | . | Mot de passe | Authentication password | . | Chiffrement | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Activé | Activate serial communication | . | Écho | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Vitesse en bauds | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Description | . | Activé | Activate notifications | . | Message d’alerte | Notify on incoming messages | . | Message d’alerte buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Bip d’alerte | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Actif | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Description | . | Activé | Activate store and forward | . | Battement de cœur (heartbeat) | Periodically announce this node’s store-and-forward capability | . | Enregistrements | Maximum stored messages | . | History Return (max) | Max messages to replay | . | History Return (window) | 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 . 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 | . | Activé | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Description | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Qualité de l’air activée | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Description | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Envoyer un bip | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Description | . | Activé | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Description | . | Activé | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Description | . | Activé | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 des 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 | . | Activé | Activate detection sensor | . | Broche de monitoring | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Envoyer un bip | Include bell character in alerts | . | Nom convivial | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Description | . | Activé | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/settings-module-admin.html#configuration-du-module", + + "relUrl": "/fr-rFR/user/settings-module-admin.html#configuration-du-module" + },"4320": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Nettoyer la base de données des nœuds . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Redémarrer . Remotely reboot a connected or administered node. 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. 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" + },"4321": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4322": { + "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" + },"4323": { "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. 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" - },"4436": { + },"4324": { "doc": "Settings — Modules & Admin", "title": "Конфигурација модула", "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Опис | . | Омогућено | Toggle MQTT bridge | . | Сервер | MQTT broker address | . | Корисничко име | Authentication username | . | Лозинка | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Корен тема | Base MQTT topic path | . | Извештај мапе | Publish position for public map | . 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 | . | Мод | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Опис | . | Омогућено | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Активан | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Омогућено | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Омогућено | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Опис | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Поруке | Newline-separated list of messages | . | Пошаљи звоно | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | Омогућено | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Опис | . | Омогућено | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Омогућено | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Пошаљи звоно | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Омогућено | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration 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#конфигурација-модула" - },"4437": { + },"4325": { "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Ресетовање на фабричка подешавања . Resets all settings to factory defaults. This cannot be undone. Поновно покретање . Remotely reboot a connected or administered node. Панел за отклањање грешака . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#администрација" - },"4438": { + },"4326": { "doc": "Settings — Modules & Admin", "title": "Related Topics", "content": ". | Settings — Radio & User — core radio 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" - },"4439": { + },"4327": { "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" - },"4440": { + },"4328": { + "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. 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" + },"4329": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Popis | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Používateľské meno | Authentication username | . | Heslo | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Popis | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Popis | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Popis | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Popis | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Správy | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Popis | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Popis | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Popis | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Popis | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/settings-module-admin.html#module-configuration", + + "relUrl": "/sk-rSK/user/settings-module-admin.html#module-configuration" + },"4330": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reštartovať . Remotely reboot a connected or administered node. Debug okno . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" + },"4331": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4332": { + "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" + },"4333": { + "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ä. 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" + },"4334": { + "doc": "Asetukset — Moduulit ja ylläpito", + "title": "Moduulin määritys", + "content": "MQTT-moduuli . Yhdistää verkon viestejä MQTT-välityspalvelimeen ja sieltä takaisin internet-yhteyksiä varten. Näin laajennat verkkoasi radiokantaman ulkopuolelle tai integroit sen kodin automaatiojärjestelmiin. | Asetus | Kuvaus | . | Käytössä | Ota MQTT-välityspalvelin käyttöön | . | Palvelin | MQTT-välityspalvelimen osoite | . | Käyttäjänimi | Todennuksen käyttäjätunnus | . | Salasana | Todennuksen salasana | . | Salaus | Salaa MQTT-viestisisällöt | . | JSON Output | ⚠️ Vanhentunut — JSON-tuki poistettu laiteohjelmistosta, kenttä ohitetaan | . | TLS | Käytä suojattua yhteyttä | . | Juuriaihe | MQTT:n perusaihepolku | . | Karttaraportointi | Julkaise sijainti julkiselle kartalle | . Katso MQTT saadaksesi yksityiskohtaisen käyttöoppaan, joka sisältää salauksen, tietosuojan ja välityspalvelimen määrityksen. Sarjaporttimoduuli . 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 | . | Käytössä | Ota sarjaporttiviestintä käyttöön | . | Toista | Toista vastaanotettu sarjaporttidata takaisin | . | Tila | Teksti-, Protobuf- tai NMEA-ulostulo | . | RX/TX pinnit | GPIO-pinnit sarjaporttiyhteyttä varten | . | Baud-siirtonopeus | Sarjaporttiyhteyden nopeus | . Ulkoisten ilmoitusten moduuli . Ohjaa radion laitteiston summeri-, LED- tai värinähälytyksiä. Hyödyllinen laitteille, joiden täytyy ilmoittaa fyysisesti viestin saapumisesta — erityisen hyödyllinen valvomattomissa tai ulkokäyttöön asennetuissa laitteissa. | Asetus | Kuvaus | . | Käytössä | Ota ilmoitukset käyttöön | . | Hälytysviesti | Ilmoita saapuvista viesteistä | . | Hälytysviestin summeri | Käytä summeria viesteille | . | Värinähälytys viesteille | Käytä värinää viesteille | . | Hälytysääni | Ilmoita soittomerkkimerkistä (bell character) | . | Ulostulo (GPIO) | Pinni ilmoitusulostuloa varten | . | Käytössä | Aktiivinen korkealla tai matalalla tasolla | . | Kesto (ms) | Ilmoituksen kesto | . | Käytä I2S:ää summerina | Käytä I2S-äänilähtöä | . Varastoi & välitä -moduuli . 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 | . | Käytössä | Ota Varastoi & välitä käyttöön | . | Valvontasignaali | Ilmoita tämän radion varastoi & välitä -ominaisuudesta säännöllisesti | . | Tiedot | Tallennettujen viestien enimmäismäärä | . | Historian palautus (enintään) | Toistettavien viestien enimmäismäärä | . | Historian palautus (aikaikkuna) | 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ä. Kuuluvuustesti-moduuli . 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 | . | Käytössä | Ota kuuluvuustesti käyttöön | . | Lähetysväli (s) | Aika testilähetysten välillä | . | Tallenna CSV-tiedosto | Kirjaa vastaanotetut testitiedot SD-kortille | . Telemetriamoduuli . 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). | Asetus | Kuvaus | . | Laitemittarien väli | Kuinka usein laitemittarit raportoidaan | . | Ympäristömittarien väli | Kuinka usein ympäristöanturit raportoidaan | . | Ilmanlaatu käytössä | Raportoi hiukkasanturin tiedot | . | Virtamittarit käytössä | Raportoi virrankulutus | . Katso Telemetria ja anturit saadaksesi tietoa tuetuista antureista ja määrityssuosituksista. Valmiiden viestien moduuli . Esimääritetyt viestit, joita voidaan käyttää laitteen fyysisillä painikkeilla (radioille, joissa on kiertokooderi, näppäimistö tai vastaava laitteisto). Määritä luettelo pikaviesteistä, jotka voidaan lähettää ilman yhdistettyä puhelinta — ihanteellinen kenttäkäyttöön. | Asetus | Kuvaus | . | Käytössä | ⚠️ Vanhentunut — nykyinen laiteohjelmisto saattaa ohittaa tämän asetuksen | . | Viestit | Rivinvaihdoilla eroteltu viestiluettelo | . | Lähetä äänimerkki | Toista merkkiääni lähetyksen yhteydessä | . | Kiertokooderi | Ota kiertokooderin syöte käyttöön | . | Ylös, alas ja painallus-pinnit | GPIO-pinnien määritykset syötteille | . Äänimoduuli . 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 | . | Käytössä | Ota äänimoduuli käyttöön | . | Codec2-nopeus | Äänenlaadun ja kaistanleveyden välinen kompromissi | . | I2S Word Select | GPIO-pinni I2S WS:lle | . | I2S-datasisääntulo | GPIO-nasta I2S DIN:lle | . | I2S-dataulostulo | GPIO-pinni I2S DOUT:lle | . ⚠️ Huomautus: Ääniominaisuudet edellyttävät yhteensopivaa laitteistoa (I2S-mikrofoni ja kaiutin). Äänenlaatu on hyvin matalakaistainen — ajattele “ymmärrettävää radiopuhetta”, ei puhelinlaatua. Etälaitteiston moduuli . 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ä. | Asetus | Kuvaus | . | Käytössä | Ota etä-GPIO-käyttö käyttöön | . | Salli määrittelemättömät pinnit | 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ä | . ⚠️ Varoitus: Määrittelemättömien pinnien salliminen antaa etäradioille pääsyn kaikkiin GPIO-pinneihin, mikä voi häiritä radion omaa laitteistoa. Ota käyttöön vain erillisissä GPIO-radioissa. Naapuritieto-moduuli . 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 | . | Käytössä | Ota naapuritiedon lähetys käyttöön | . | Päivitysväli (s) | Kuinka usein naapuriluettelo lähetetään | . | Lähetä LoRan 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 Haku saadaksesi lisätietoja naapuritietojen käyttämisestä verkon topologian tutkimiseen. Ympäristövalaistusmoduuli . Ohjaa tuetuissa laitteissa olevaa NeoPixeliä tai muita osoitteellisia RGB-LEDejä. Voidaan käyttää visuaalisina tilailmaisimina, ilmoitusvaloina tai koriste-efekteinä. | Asetus | Kuvaus | . | Ledin 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) | . Tunnistusanturimoduuli . 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 | . | Käytössä | Ota tunnistusanturi käyttöön | . | Valvonta pinni | Anturiin kytketty GPIO-pinni | . | Havaitsemisen laukaisutyyppi | Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu) | . | Käytä sisäistä ylösvetovastusta | Ota pinnin sisäinen ylösvetovastus käyttöön | . | Lähetyksen vähimmäisväli (s) | Hälytyslähetysten vähimmäisaika | . | Tilalähetys (s) | Tilatiedon lähetysväli | . | Lähetä äänimerkki | Sisällytä soittomerkkimerkki hälytyksiin | . | Käyttäjäystävälinen nimi | Tälle anturille määritetty nimi | . PAX-laskurimoduuli . Henkilölaskuri, joka hyödyntää Wi-Fi- ja BLE-koepyyntöjä. 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 | . | Käytössä | Ota henkilölaskenta käyttöön | . | Päivitysväli (s) | Kuinka usein laskentatiedot raportoidaan | . 💡 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. TAK-moduuli . Team Awareness Kit -integraatio yhteensopivuutta varten ATAK- ja WinTAK-järjestelmien kanssa. Katso TAK-integraatio saadaksesi tarkemmat määritys- ja käyttöohjeet. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/settings-module-admin.html#moduulin-m%C3%A4%C3%A4ritys", + + "relUrl": "/fi-rFI/user/settings-module-admin.html#moduulin-määritys" + },"4335": { + "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. | . ⚠️ Edellyttää: Ylläpitoavain on määritetty sekä omassa radiossasi että kohderadiossa. Tyhjennä NodeDB-tietokanta . Poistaa vanhentuneet radiot paikallisesta tietokannastasi, jos niistä ei ole kuultu määritettävän aikaikkunan aikana. Palauta tehdasasetukset . Palauttaa kaikki asetukset tehdasasetuksiin. Tätä toimintoa ei voi perua. Käynnistä uudelleen . Käynnistä yhdistetty tai ylläpidettävä radio etänä uudelleen. Vianetsintäpaneeli . Avaa Paketit- ja Sovelluslokit-välilehdet diagnostiikkatietojen tarkastelua, suodatusta ja vientiä varten. Katso Virheenjäljityslokit, jossa on täydellinen käyttöohje. Etähallinnan vianmääritys . | 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" + },"4336": { + "doc": "Asetukset — Moduulit ja ylläpito", + "title": "Aiheeseen liittyvät aiheet", + "content": ". | Asetukset — Radio ja käyttäjä — radion ja käyttäjäprofiilin keskeiset asetukset | 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" + },"4337": { + "doc": "Настройки — Модули и администрирование", + "title": "Настройки — Модули и администрирование", + "content": "Настрой дополнительные функциональные модули и выполняй управление устройством. Модули расширяют Meshtastic с помощью специализированных возможностей — каждый из них можно включать или отключать отдельно. 💡 Совет: Тебе нужно включать только те модули, которые действительно используешь. Отключение неиспользуемых модулей снижает время передачи, экономит батарею и упрощает конфигурацию. Настройки модулей используют макет на основе карточек с переключателями, выпадающими списками, текстовыми полями и ползунками: . . ", + "url": "/Meshtastic-Android/main/ru-rRU/user/settings-module-admin.html", + + "relUrl": "/ru-rRU/user/settings-module-admin.html" + },"4338": { + "doc": "Настройки — Модули и администрирование", + "title": "Конфигурация модуля", + "content": "Модуль MQTT . Мосты передают сообщения туда и обратно от брокера MQTT для подключения к интернету. Ты так расширишь сеть за пределы радиуса действия или интегрируешь её с системами домашней автоматизации. | Настройка | Описание | . | Включено | Переключить MQTT мост | . | Сервер | Адрес MQTT брокера | . | Имя пользователя | Имя пользователя для аутентификации | . | Пароль | Пароль аутентификации | . | Шифрование | Зашифровать MQTT-пейлоады | . | Вывод JSON | ⚠️ Устарело — поддержка JSON удалена из прошивки; поле игнорируется | . | TLS | Использовать защищённое соединение | . | Корневая тема | Базовый путь темы MQTT | . | Отчет карты | Опубликовать позицию на публичной карте | . См. MQTT для подробного руководства по использованию, включая шифрование, конфиденциальность и настройку брокера. Последовательный модуль . Позволяет общаться через последовательный порт с внешними устройствами (GPS-модулями, датчиками или собственной техникой). Когда включено, последовательный порт ноды может отправлять и получать данные в формате protobuf или текст, что позволяет внешним микроконтроллерам или компьютерам взаимодействовать с сетью. | Настройка | Описание | . | Включено | Включить последовательное соединение | . | Эхо | Echo получил обратно последовательные данные | . | Режим обмена | Вывод в формате текста, Protobuf или NMEA | . | Пины RX/TX | GPIO-пины для последовательного соединения | . | Скорость передачи (бод) | Скорость последовательного соединения | . Модуль внешних уведомлений . Управляет зуммером, светодиодом или вибрацией на вашем радиооборудовании. Полезно для устройств, которым нужно физически сигнализировать о приходе сообщения — особенно удобно для неоснащенных персоналом или уличных установок. | Настройка | Описание | . | Включено | Включить уведомления | . | Включить уведомление о входящем сообщении | Уведомлять о входящих сообщениях | . | Зуммер при уведомлении | Использовать буззер для сообщений | . | Вибрация при уведомлении | Использовать вибрацию для сообщений | . | Уведомлять при 🔔 | Уведомлять о символе колокола | . | Вывод (GPIO) | Пин для вывода уведомления | . | Активный выход | Высокая или низкая активность | . | Длительность (мс) | Длительность уведомления | . | Использовать I2S как буззер | Использовать аудиовывод I2S | . Модуль Store & Forward . Буферизирует сообщения для узлов, которые временно были недоступны, а затем ретранслирует их, когда эти узлы переподключаются. Важное значение для сеток, где узлы входят и выходят вне диапазона регулярно - обеспечивает отсутствие потери сообщений при коротких разъединениях. | Настройка | Описание | . | Включено | Активировать режим хранения и пересылки | . | Heartbeat | Периодически объявлять о наличии функции хранения и пересылки у этого узла | . | Записи | Максимальное количество сохраненных сообщений | . | История возврата (макс) | Максимум сообщений для повтора | . | Возврат истории (окно) | Окно времени для повтора | . | Сервер | Действовать как сервер хранения и пересылки для mesh-сети (требуется большой объем памяти, например, ESP32 с PSRAM) | . 💡 Совет: Хранение и пересылка лучше всего работает на узлах с достаточной памятью (ESP32 с PSRAM). Узлы маршрутизатора являются идеальными кандидатами, так как они обычно всегда включены. Модуль проверки дальности . Автоматизированный инструмент для проверки дальности и оценки качества связи между нодами. Когда включено, нода периодически отправляет сообщения с увеличивающимся счетчиком. Приёмная нода записывает эти сообщения, что позволяет тебе уйти пешком или уехать на машине, а потом проанализировать, на каком расстоянии сообщения перестали приходить. | Настройка | Описание | . | Включено | Активировать проверку дальности | . | Интервал отправки (с) | Время между передачами проверок | . | Сохранить в CSV | Журнал полученных тестовых данных на SD-карту | . Модуль телеметрии . Контролирует какими телеметрическими данными ваш узел делится с сеткой. Телеметрия включает данные о состоянии устройства (заряд батареи, время работы) и данные с датчиков окружающей среды (температура, влажность, давление). | Настройка | Описание | . | Интервал обновления метрик устройства | Как часто сообщать о показателях устройства | . | Интервал обновления метрик среды | Как часто сообщать о датчиках окружающей среды | . | Телеметрия воздуха | Сообщить данные датчика частиц | . | Включены метрики энергии | Сообщать об энергопотреблении | . Посмотрите Телеметрия и датчики — для получения информации о поддерживаемых датчиках и рекомендациях по настройке. Модуль шаблонных сообщений . Предварительно настроенные сообщения, доступные через физические кнопки устройства (для радиостанций с поворотными энкодерами, кнопочными панелями или аналогичным оборудованием ввода). Определите список быстрых сообщений, которые могут быть переданы без подключённого телефона — идеально подходит для использования в поле. | Настройка | Описание | . | Включено | ⚠️ Устарело — текущая прошивка может игнорировать этот переключатель | . | Сообщения | Список сообщений, разделённых новой строкой | . | Отправлять 🔔 | Воспроизвести звук колокола при отправке | . | Поворотный энкодер | Включить ввод поворотного энкодера | . | Пины поворота и нажатия | Задания GPIO PIN-кода для ввода | . Звуковой модуль . Поддержка аудио Codec2 для низкополосной голосовой связи через сетку. Это экспериментальная функция, которая кодирует голос в очень маленькие пакеты данных с помощью кодека Codec2. | Настройка | Описание | . | Включено | Активировать модуль аудио | . | Частота кодирования | Компромисс между качеством звука и полосой пропускания | . | Выбор слов I2S | GPIO контакт для I2S WS | . | I2S Вход данных | Пин GPIO для I2S DIN | . | I2S Выход данных | Пин GPIO для I2S DOUT | . ⚠️ Примечание: Для работы аудио требуется специальное аппаратное обеспечение (I2S-микрофон и динамик). Качество голоса очень низкополосное — представьте себе «разборчивую радиосвязь», а не качество телефонного звонка. Удаленный аппаратный модуль . Управление GPIO через mesh-сеть. Позволяет удалённому узлу читать и записывать состояния выводов GPIO на другом узле — полезно для активации реле, опроса переключателей или удалённого управления внешним оборудованием. | Настройка | Описание | . | Включено | Активировать удаленный GPIO доступ | . | Разрешить неопределенные пины | Разрешить доступ к любому GPIO-пину (риск для безопасности) | . | Доступные пины | До 4 пинов GPIO, которые этот узел предоставляет для удалённого чтения и записи | . ⚠️ Предупреждение: Включение опции «Разрешить неопределённые пины» даёт удалённым узлам доступ ко всем выводам GPIO, что может нарушить работу собственного аппаратного обеспечения радио. Включать только на выделенных GPIO-нодах. Модуль информации о соседях . Транслирует информацию о доступных услышанных соседей, включив ячейку сеточной топологии. Каждый включенный узел периодически делится списком других узлов которые он может слышать и их качество сигнала. | Настройка | Описание | . | Включено | Включить трансляцию соседей | . | Интервал обновления (с) | Как часто транслировать список соседей | . | Передача через LoRa | Также транслировать информацию соседей по LoRa, а не только MQTT/телефон. Недоступно на канале используя ключ по умолчанию и имя | . Смотрите Discovery за тем как использовать соседние данные для сеточно топологического исследования. Модуль окружающего освещения . Управляет встроенными светодиодами NeoPixel или другими адресуемыми RGB-светодиодами на поддерживаемом оборудовании. Может использоваться для визуальных статусовых индикаторов, световых уведомлений, или декоративных эффектов. | Настройка | Описание | . | Состояние светодиода | Включить или выключить светодиод | . | Ток | Текущий лимит светодиодов (0–31) | . | Красный / Зеленый / Синий | Индивидуальные значения цветов канала (0–255) | . Модуль определения датчика . Превращает ваш узел в систему сигнализации на основе датчика движения или открытия двери. При обнаружении изменения состояния на выводе GPIO (например, сработал датчик движения или открылась дверь) узел отправляет по меш-сети оповещение. | Настройка | Описание | . | Включено | Активировать датчик обнаружения | . | Пин датчика | Пин GPIO, подключенный к датчику | . | Триггер срабатывания | Как состояние пина интерпретируется как событие обнаружения (например, активный высокий/низкий уровень, срабатывание по фронту) | . | Использовать режим подтяжки входа | Включить внутренний подтягивающий резистор пина | . | Минимальное количество трансляций (с) | Минимальный интервал между оповещениями | . | Трансляция состояния (с) | Интервал периодической отправки состояния | . | Отправлять 🔔 | Включать символ колокола в оповещения | . | Имя датчика | Пользовательское имя для этого датчика | . Paxcounter Модуль . Подсчёт количества людей по Wi-Fi и BLE-запросам от устройств. Засчитывает ближайшие устройства, пассивно прослушивая зондирующие запросы, чтобы телефоны и ноутбуки излучали при сканировании сетей. Доступно только на устройствах ESP32. | Настройка | Описание | . | Включено | Активировать подсчет людей | . | Интервал обновления (с) | Как часто сообщать подсчитывания | . 💡 Совет: Paxcounter полезен для приблизительной оценки пешеходного потока в местах начала маршрутов, на мероприятийных площадках или в других локациях. Счетчики приблизительны — один человек может иметь несколько устройств. Модуль TAK . Интеграция Team Awareness Kit для совместимости с ATAK и WinTAK. См. TAK Integration для детальной настройки и использования. ", + "url": "/Meshtastic-Android/main/ru-rRU/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%8F-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D1%8F", + + "relUrl": "/ru-rRU/user/settings-module-admin.html#конфигурация-модуля" + },"4339": { + "doc": "Настройки — Модули и администрирование", + "title": "Администрирование", + "content": "Удаленное администрирование . Удалённо настраивай ноды, которые используют твой ключ администрирования: . | Выбери целевую ноду в списке нод. | Перейди в Настройки этой ноды. | Измени конфигурацию. | Нажми Сохранить — изменения отправляются через сеть. | . ⚠️ Требуется: Ключ администратора настроенный как на вашем узле, так и на целевом узле. Очистить базу данных нод . Удаляет устаревшие узлы из локальной базы данных, которые не были услышаны в настраиваемом окне времени. Сброс к заводским настройкам . Сбрасывает все настройки к заводским. Это действие нельзя отменить. Перезагрузка . Удаленно перезагрузить подключенный или управляемый узел. Панель отладки . Открывает вкладки Пакет и Журналы приложений для просмотра, фильтрации и экспорта диагностических выходов. См. Отладочные журналы для полного прохождения. Устранение неполадок удалённого администрирования . | “Нет ответа от целевого узла” — цель может находиться вне диапазона, в автономном режиме или иметь несоответствующий ключ администратора. Проверьте соответствие ключа администратора на обоих узлах. | Изменения не применены — чтобы некоторые настройки вступили в силу, нужно перезагрузить устройство. Попробуй перезагрузить после сохранения. | Не видны настройки удалённой ноды — убедись, что твоя нода имеет админ-ключ для целевой ноды. Админ-канал настраивается автоматически, когда задан ключ администратора. | . ", + "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#администрирование" + },"4340": { + "doc": "Настройки — Модули и администрирование", + "title": "Связанные темы", + "content": ". | Настройки — Радио и Пользователь — основные настройки радио и профиля пользователя | Ссылка на конфигурацию модуля — подробная документация по модулям на 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#связанные-темы" + },"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. 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" + },"4342": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | 설명 | . | 활성화 | Toggle MQTT bridge | . | 서버 | MQTT broker address | . | 사용자명 | Authentication username | . | 비밀번호 | Authentication password | . | 암호화 | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial Module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | 설명 | . | 활성화 | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | 설명 | . | 활성화 | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | 설명 | . | 활성화 | Activate store and forward | . | Heartbeat | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | 설명 | . | 활성화 | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | 설명 | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | 설명 | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | 메시지기기 | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | 설명 | . | 활성화 | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | 설명 | . | 활성화 | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | 설명 | . | 활성화 | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | 설명 | . | 활성화 | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | 설명 | . | 활성화 | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/settings-module-admin.html#module-configuration", + + "relUrl": "/ko-rKR/user/settings-module-admin.html#module-configuration" + },"4343": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. 재부팅 . Remotely reboot a connected or administered node. 디버그 패널 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#관리" + },"4344": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4345": { + "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" + },"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. 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" + },"4347": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Opis | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Opis | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Opis | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Opis | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/settings-module-admin.html#module-configuration", + + "relUrl": "/hr-rHR/user/settings-module-admin.html#module-configuration" + },"4348": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Ponovno pokreni . Remotely reboot a connected or administered node. Otklanjanje pogrešaka . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" + },"4349": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4350": { + "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" + },"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. 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" - },"4441": { + },"4352": { "doc": "Settings — Modules & Admin", "title": "Module Configuration", "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Përshkrimi | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Përshkrimi | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Përshkrimi | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Përshkrimi | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Përshkrimi | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | 訊息 | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Përshkrimi | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Përshkrimi | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Përshkrimi | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Përshkrimi | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/sq-rAL/user/settings-module-admin.html#module-configuration", "relUrl": "/sq-rAL/user/settings-module-admin.html#module-configuration" - },"4442": { + },"4353": { "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Rindiz . Remotely reboot a connected or administered node. 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. 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ë" - },"4443": { + },"4354": { "doc": "Settings — Modules & Admin", "title": "Related Topics", "content": ". | Settings — Radio & User — core radio 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" - },"4444": { + },"4355": { "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" - },"4445": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "url": "/Meshtastic-Android/main/is-rIS/user/settings-radio-user.html#settings--radio--user", + },"4356": { + "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. 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": "/is-rIS/user/settings-radio-user.html#settings--radio--user" - },"4446": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Lýsing | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/is-rIS/user/settings-radio-user.html#user-settings", + "relUrl": "/no-rNO/user/settings-module-admin.html#settings--modules--admin" + },"4357": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Beskrivelse | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Beskrivelse | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beskrivelse | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Beskrivelse | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beskrivelse | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beskrivelse | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Beskrivelse | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beskrivelse | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beskrivelse | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/no-rNO/user/settings-module-admin.html#module-configuration", - "relUrl": "/is-rIS/user/settings-radio-user.html#user-settings" - },"4447": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | Lýsing | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Lýsing | Default | . | Svæði | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Lýsing | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Lýsing | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Lýsing | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Lýsing | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Lýsing | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Lýsing | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + "relUrl": "/no-rNO/user/settings-module-admin.html#module-configuration" + },"4358": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Omstart . Remotely reboot a connected or administered node. Feilsøkningspanel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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": "/is-rIS/user/settings-radio-user.html#configuration" - },"4448": { - "doc": "Settings — Radio & User", + "relUrl": "/no-rNO/user/settings-module-admin.html#administrasjon" + },"4359": { + "doc": "Settings — Modules & Admin", "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", + "content": ". | Settings — Radio & User — core radio 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": "/is-rIS/user/settings-radio-user.html#related-topics" - },"4449": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", + "relUrl": "/no-rNO/user/settings-module-admin.html#related-topics" + },"4360": { + "doc": "Settings — Modules & Admin", + "title": "Settings — Modules & Admin", "content": " ", - "url": "/Meshtastic-Android/main/is-rIS/user/settings-radio-user.html", + "url": "/Meshtastic-Android/main/no-rNO/user/settings-module-admin.html", - "relUrl": "/is-rIS/user/settings-radio-user.html" - },"4450": { - "doc": "設定：無線機とユーザー", - "title": "設定：無線機とユーザー", - "content": "無線機のハードウェアと、ユーザーの識別情報のパラメーターを設定します。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/settings-radio-user.html", + "relUrl": "/no-rNO/user/settings-module-admin.html" + },"4361": { + "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. 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": "/ja-rJP/user/settings-radio-user.html" - },"4451": { - "doc": "設定：無線機とユーザー", - "title": "ユーザー設定", - "content": "ユーザープロファイル . | 設定項目 | 説明 | . | 正式名称 | 表示名（最大 39 文字） | . | 短縮名 | 4 文字の短縮名 | . | 免許を持つ運用者 | アマチュア無線の免許を持っている場合に有効にします（より高い出力が可能になります） | . 変更を適用する . 設定を変更したら、「保存」をタップして構成を無線機に書き込みます。 変更を適用するために、デバイスが再起動することがあります。 . ", - "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": "/lt-rLT/user/settings-module-admin.html#settings--modules--admin" + },"4362": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Aprašymas | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Aprašymas | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Aprašymas | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Aprašymas | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Aprašymas | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Aprašymas | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Aprašymas | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Aprašymas | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Aprašymas | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/settings-module-admin.html#module-configuration", - "relUrl": "/ja-rJP/user/settings-radio-user.html#ユーザー設定" - },"4452": { - "doc": "設定：無線機とユーザー", - "title": "設定", - "content": "デバイスの設定 . | 設定項目 | 説明 | デフォルト | . | 役割 | ノードの動作（クライアント、ルーターなど） | クライアント | . | 再ブロードキャストモード | ノードがメッセージを再送信する方法 | すべて | . | ノード情報のブロードキャスト（秒） | ノード情報をブロードキャストする間隔 | 10800 | . | ダブルタップボタン | ボタンをダブルタップしたときの動作 | 無効 | . LoRa設定 . | 設定項目 | 説明 | デフォルト | . | リージョン | 周波数帯の規制リージョン | 未設定（要設定） | . | モデムプリセット | 速度と距離のトレードオフ | LongFast | . | ホップ数上限 | 再送信の最大ホップ数 | 3 | . | 送信出力 | 送信出力（dBm）。0 = リージョンで許可された最大値 | 0（リージョン最大） | . | 周波数オフセット | 周波数の微調整（MHz） | 0 | . | チャンネル帯域幅 | 帯域幅の設定 | プリセットのデフォルト | . ⚠️ 重要： 送信する前に、必ずリージョンを設定する必要があります。 正しいリージョンを設定せずに運用すると、現地の無線規制に違反するおそれがあります。 詳しくは、meshtastic.org の リージョン設定ガイド を参照してください。 . モデムプリセット . 💡 ヒント： 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 | 5.5 kbps | −10 dB | 郊外の短距離。中程度の建物密度 | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | 郊外エリア。中程度の建物密度 | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | 郊外・地方。中程度の距離で低速 | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Long Fast と同程度の距離だが 500 kHz 帯域幅。スループットが速い | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | 一般用途（デフォルト）：距離と速度のバランスが良い | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | 起伏のある地方。ときどき使う用途 | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD 帯（125 kHz 帯域幅）。Medium Fast に相当 | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD 帯（125 kHz 帯域幅）。Long Fast に相当 | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz 帯（62.5 kHz 帯域幅）。他のデバイスとの干渉を避ける | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz 帯（62.5 kHz 帯域幅）。Long Fast に相当 | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります | . ℹ️ 注意： この表では、一般的な短い名前を使用しています。 アプリのプリセットのドロップダウンでは、Short Range - Fast、Long Range - Fast、Lite - Fast、Narrow - Fast のように表示されます。 . モデムプリセットを選ぶ . モデムプリセットは、距離とデータ速度の基本的なトレードオフを制御します： . | 遅いプリセットは拡散をより多く使い、より弱い信号レベルでも復調できるようにします（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 のままにします。これはコミュニティのデフォルトで、地域内の他のユーザーとの互換性を確保します。 | . ⚠️ 重要： 同じチャンネル上のすべてのノードは、同じモデムプリセットを使用する必要があります。 プリセットが一致しないノードは、同じ周波数と暗号化鍵を共有していても通信できません。 . 💡 ヒント： 上記の距離の目安は、平坦な地形と一般的なアンテナを前提としています。 高所（丘の上、屋上）にあると、実効的な距離が大幅に伸びます。 適切に設置された Long Fast のルーターは、地上に置かれた Long Slow のノードを上回ることがよくあります。 . 表示設定 . | 設定項目 | 説明 | . | 画面のタイムアウト | ディスプレイがスリープするまでの時間 | . | 表示単位 | メートル法またはヤード・ポンド法 | . | OLED の種類 | 自動、SSD1306、SH1106、SH1107 | . | コンパスの向き | コンパス表示の回転オフセット（0°、90°、180°、270°） | . | コンパスの北 | ⚠️ 非推奨：コンパスの向きに置き換えられました。古いファームウェアではまだ表示されます | . 位置情報設定 . | 設定項目 | 説明 | . | GPS を有効化 | GPS の有効／無効 | . | GPS の更新間隔 | GPS 測位を取得する頻度 | . | 位置のブロードキャスト（秒） | 位置を共有する頻度 | . | スマート位置 | 移動に基づくブロードキャストを有効化 | . | 固定位置 | 手動で設定した位置を使用 | . 電源設定 . | 設定項目 | 説明 | . | 省電力 | 低電力のスリープモードを有効化 | . | シャットダウンまでの時間（秒） | アイドル時の自動シャットダウンタイマー | . | ADC 倍率 | バッテリー電圧の校正係数 | . | Bluetooth 待機時間（秒） | 起動時に BLE 接続を待つ時間 | . | メッシュ SDS タイムアウト（秒） | スーパーディープスリープのタイムアウト | . ネットワーク設定 . | 設定項目 | 説明 | . | WiFi を有効化 | WiFi 無線を有効化（ESP32 デバイス） | . | WiFi SSID | 接続先のネットワーク名 | . | WiFi PSK | ネットワークのパスワード | . | NTP サーバー | 時刻同期サーバー | . | Syslog サーバー | リモートログサーバー | . Bluetooth 設定 . | 設定項目 | 説明 | . | Bluetooth を有効化 | BLE 無線の有効／無効 | . | ペアリングモード | 固定 PIN、ランダム PIN、または PIN なし | . | 固定 PIN | ペアリング用の PIN コード（デフォルト：123456） | . セキュリティ設定 . | 設定項目 | 説明 | . | 公開鍵 | ノードの公開鍵（読み取り専用） | . | 管理者鍵 | リモート管理用の鍵 | . | 秘密鍵 | ノードの秘密鍵（安全に取り扱ってください） | . | 管理チャンネルを有効化 | ⚠️ 削除されました：管理者キーを設定すると自動的に構成されるようになりました | . | デバッグログ | シリアル／Bluetooth 経由でライブのデバッグログを出力 | . | シリアルを有効化 | シリアルコンソールへのアクセスを有効化（デバイスの設定から移動） | . | 管理モード | 管理者以外によるチャンネル変更を制限 | . | 鍵をバックアップ | ノードの鍵の暗号化されたバックアップを、このデバイスに保存します（Android のみ） | . | 鍵を復元 | バックアップした鍵をノードに書き戻します（バックアップがある場合に利用可能） | . | 鍵のバックアップを削除 | このデバイスに保存されている鍵のバックアップを削除します | . | 保護レベル | パケットの真正性。署名のないパケットや中継されたパケットをどう扱うか：厳格、バランス、互換（対応するファームウェアが必要。厳格は確認を求めます） | . 設定には、標準的な設定コントロール（ドロップダウン、トグル、スライダー）を使用します： . | コントロール | スクリーンショット | . | ドロップダウン | | . | トグル | | . | スライダー | | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/settings-radio-user.html#%E8%A8%AD%E5%AE%9A", + "relUrl": "/lt-rLT/user/settings-module-admin.html#module-configuration" + },"4363": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Perkrauti . Remotely reboot a connected or administered node. Derinimo skydelis . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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": "/ja-rJP/user/settings-radio-user.html#設定" - },"4453": { - "doc": "設定：無線機とユーザー", + "relUrl": "/lt-rLT/user/settings-module-admin.html#administravimas" + },"4364": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4365": { + "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" + },"4366": { + "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. 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" + },"4367": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | الوصف | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial Module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | الوصف | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | الوصف | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | الوصف | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | الوصف | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | الوصف | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | الوصف | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | الرسائل | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | الوصف | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | الوصف | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | الوصف | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | الوصف | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | الوصف | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/settings-module-admin.html#module-configuration", + + "relUrl": "/ar-rSA/user/settings-module-admin.html#module-configuration" + },"4368": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. إعادة التشغيل . Remotely reboot a connected or administered node. Debug Panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#الإدارة" + },"4369": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4370": { + "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" + },"4371": { + "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. 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" + },"4372": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descrição | . | Enabled | Toggle MQTT bridge | . | Servidor | MQTT broker address | . | Utilizador | Authentication username | . | Palavra-passe | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descrição | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrição | . | Enabled | Activate store and forward | . | Batimento | Periodically announce this node’s store-and-forward capability | . | Records | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descrição | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrição | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Mensagens | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrição | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descrição | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrição | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrição | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/settings-module-admin.html#module-configuration", + + "relUrl": "/pt-rPT/user/settings-module-admin.html#module-configuration" + },"4373": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reiniciar . Remotely reboot a connected or administered node. 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. 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" + },"4374": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4375": { + "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" + },"4376": { + "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. 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" + },"4377": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | תיאור | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial Module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | תיאור | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | תיאור | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | תיאור | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | תיאור | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | תיאור | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | תיאור | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | הודעות | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | תיאור | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | תיאור | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | תיאור | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | תיאור | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | תיאור | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/settings-module-admin.html#module-configuration", + + "relUrl": "/iw-rIL/user/settings-module-admin.html#module-configuration" + },"4378": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. אתחול מחדש . Remotely reboot a connected or administered node. פאנל דיבאג . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" + },"4379": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4380": { + "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" + },"4381": { + "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. 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" + },"4382": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Περιγραφή | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Όνομα χρήστη | Authentication username | . | Κωδικός πρόσβασης | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial Module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Περιγραφή | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Περιγραφή | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Περιγραφή | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Περιγραφή | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Περιγραφή | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Περιγραφή | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Μηνύματα | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Περιγραφή | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Περιγραφή | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Περιγραφή | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | How often to broadcast neighbor list | . | Transmit Over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See 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 | Περιγραφή | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Περιγραφή | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/el-rGR/user/settings-module-admin.html#module-configuration", + + "relUrl": "/el-rGR/user/settings-module-admin.html#module-configuration" + },"4383": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Επανεκκίνηση . Remotely reboot a connected or administered node. Πίνακας αποσφαλμάτωσης . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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#διαχείριση" + },"4384": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4385": { + "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" + },"4386": { + "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. 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" + },"4387": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descriere | . | Activat | Toggle MQTT bridge | . | Server | MQTT broker address | . | Nume de utilizator | Authentication username | . | Parolă | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Activat | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descriere | . | Activat | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descriere | . | Activat | Activate store and forward | . | Puls | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Activat | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descriere | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descriere | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Mesaje | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descriere | . | Activat | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descriere | . | Activat | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descriere | . | Activat | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Activat | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descriere | . | Activat | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/settings-module-admin.html#module-configuration", + + "relUrl": "/ro-rRO/user/settings-module-admin.html#module-configuration" + },"4388": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Curăță baza de date a nodurilor . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Restartează . Remotely reboot a connected or administered node. Panou de depanare . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" + },"4389": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4390": { + "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" + },"4391": { + "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. 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" + },"4392": { + "doc": "Sätted - moodulid & admin", + "title": "Mooduli konf", + "content": "MQTT moodul . Sildab võrgusõnumeid MQTT vahendajasse ja sealt internetiühenduse loomiseks. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Sätted | Kirjeldus | . | Lubatud | Lükka MQTT sild sisse | . | Server | MQTT vahendaja aadress | . | Kasutajatunnus | Authentication username | . | Parool | Authentication password | . | Encryption | Krüpteeri MQTT kasutus | . | JSON Output | ⚠️ Vananenud — JSON tugi püsivarast eemaldatud; välja ignoreeritakse | . | TLS | Use secure connection | . | Root Topic | Baas MQTT teema teekond | . | Kaardiaruanne | Avalda asukoht avalikul kaardil | . Vaata MQTT üksikasjalikumat kasutusjuhendit, mis sisaldab teavet krüpteerimise, privaatsuse ja vahendaja seadistamise kohta,. Jadapordi moodul . 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 | . | Lubatud | Aktiveeri jadapordi ühendus | . | Echo | Kaja sai jadaandmed tagasi | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX kontaktid | GPIO sisend jagaühenduseks | . | Baud Rate | Jadaühenduse kiirus | . Välise teavitusmoodul . Juhib raadio riistvara summeri-, LED- või vibratsioonihoiatusi. Kasulik seadmetele, mis peavad sõnumi saabumisest füüsiliselt märku andma – eriti kasulik järelevalveta või välistingimustes paigaldamise korral. | Sätted | Kirjeldus | . | Lubatud | Aktiveeri märguanded | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Hoiatuskell | Teavita hoiatuskella märgist | . | Väljund (GPIO) | Sisend teavitusväljundi jaoks | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Salvesta & edasta moodul . 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. | Sätted | Kirjeldus | . | Lubatud | Aktiveeri salvesta ja saada | . | Südamelöögid | Periodically announce this node’s store-and-forward capability | . | 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) | . 💡 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. Kaugustesti moodul . 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 | . | Lubatud | Aktiveeri levi test | . | Sender Interval (s) | Time between test transmissions | . | Salvesta CSV | Log received test data to SD card | . Telemeetria moodul . Controls what telemetry data your node shares with the mesh. Telemeetria sisaldab seadme tervist (aku, tööaeg) ja keskkonnaandurite andmeid (temperatuur, niiskus, rõhk). | Sätted | Kirjeldus | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . Vaata Telemeetria & Sensorid toetatud andurite ja sätete soovituste kohta. Eelsalvestatud sõnumi moodul . Seadme füüsiliste nuppude kaudu ligipääsetavad eelseadistatud sõnumid (pöördnuppude, klaviatuuride või sarnase sisendriistvaraga raadiote puhul). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Sätted | Kirjeldus | . | Lubatud | ⚠️ Vananenud — praegune püsivara võib seda lülitit ignoreerida | . | Sõnumid | Newline-separated list of messages | . | Saada kelluke | Esita saatmisel kellukese heli | . | Rotary Encoder | Enable rotary encoder input | . | Üles/alla/vajuta sisend | GPIO sisendi kontaktide määramine | . Audio moodul . 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 | . | Lubatud | Aktiveeri audio moodul | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO sisend I2S WS jaoks | . | I2S Data In | GPIO sisend I2S DIN jaoks | . | I2S Data Out | GPIO sisend I2S DOUT jaoks | . ⚠️ Märkus: Heli jaoks on vaja spetsiaalset riistvara (I2S mikrofon ja kõlar). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Kaugriistvara moodul . 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. | Sätted | Kirjeldus | . | Lubatud | Aktiveeri kaugjuurdepääs GPIO-le | . | Luba määratlemata sisendid | Luba juurdepääs mis tahes GPIO sisendile (turvarisk) | . | Available Pins | Kuni 4 GPIO sisendit, mida see sõlm kauglugemiseks/-kirjutamiseks avab | . ⚠️ Hoiatus: Funktsiooni „Luba määratlemata sisendkontaktid” lubamine annab kaugsõlmedele juurdepääsu kõigile GPIO sisendile, mis võib häirida raadio enda riistvara. Luba ainult spetsiaalsetel GPIO sõlmedel. Naabriinfo moodul . 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 | . | Lubatud | Aktiveeri naabrite leviring | . | Värskendusintervall(id) | Kui tihti naabrite nimekirja levitada | . | Transmit Over LoRa | Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval | . Vaata Avasta kuidas kasutada naabri-andmeid kärgvõrgu topoloogia uurimiseks. Ambientvalguse moodul . Juhib toetatud riistvaral NeoPixeli või muid adresseeritavaid RGB LEDe. Can be used for visual status indicators, notification lights, or decorative effects. | Sätted | Kirjeldus | . | LED olek | Turn the LED on or off | . | Pinge | LED current limit (0–31) | . | Red / Green / Blue | Individuaalsete värvikanalite väärtused (0–255) | . Tuvastusanduri moodul . Turns your node into a motion or door sensor alert system. Kui GPIO sisend tuvastab oleku muutuse (liikumine tuvastatud, uks avatud), levitab sõlm kärgvõrgu kaudu hoiatusteate. | Sätted | Kirjeldus | . | Lubatud | Aktiveeri tuvastusandur | . | Ekraani sisend | GPIO sisend on anduriga ühendatud | . | Detection Trigger Type | Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav) | . | Use Input Pullup Mode | Enable the pin’s internal pull-up resistor | . | Minimaalne leviring(id) | Minimaalne aeg hoiatusteadete levitamisel | . | Riiklik ringhääling(ud) | Perioodilise oleku levitamise intervall | . | Saada hoiatuskell | Lisa märguannetesse hoiatuskella sümbol | . | Friendly Name | Selle anduri kohandatud nimi | . Paxloenduri moodul . Inimeste loendur WiFi ja BLE päringute abil. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Sätted | Kirjeldus | . | Lubatud | Aktiveeri inimeste loendamine | . | Värskendusintervall(id) | How often to report counts | . 💡 Vihje: Paxloendur on kasulik jalakäijate liikluse hindamiseks matkaradade alguses, ürituste toimumiskohtades või muudes kohtades. Counts are approximate — one person may carry multiple devices. TAK moodul . Meeskonna teadlikkuse komplekti integratsioon ATAKi ja WinTAKi koostalitlusvõime tagamiseks. Vaata TAK Integration täpsema seadistamise ja kasutamise kohta. ", + "url": "/Meshtastic-Android/main/et-rEE/user/settings-module-admin.html#mooduli-konf", + + "relUrl": "/et-rEE/user/settings-module-admin.html#mooduli-konf" + },"4393": { + "doc": "Sätted - moodulid & admin", + "title": "Haldus", + "content": "Kaughaldus . Administraatori võtit jagavate sõlmede kaugkonfigureerimine: . | Select the target node in the node list. | Mine selle sõlme Seadetesse. | Muuda seadistust. | Puuduta Salvesta – muudatused saadetakse kärgvõrgu kaudu. | . ⚠️ Nõutud: Administraatori võtit, mis on seadistatud nii sinu kui ka sihtsõlmes. Tühjenda sõlmede andmebaas . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Taastab kõik seaded tehase vaikeväärtustele. Seda ei saa tagasi võtta. Taaskäivita . Ühendatud või hallatava sõlme kaugkäivitamine. Arendaja paneel . Avab vahekaardid Paketid ja Rakenduse logid diagnostilise väljundi vaatamiseks, filtreerimiseks ja eksportimiseks. See Debug Logs for the full walkthrough. Kaug-admin tõrkeotsing . | “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" + },"4394": { + "doc": "Sätted - moodulid & admin", + "title": "Related Topics", + "content": ". | Seaded — Raadio ja kasutaja — raadio ja kasutajaprofiili põhiseaded | 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#related-topics", + + "relUrl": "/et-rEE/user/settings-module-admin.html#related-topics" + },"4395": { + "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" + },"4396": { + "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. 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" + },"4397": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Cur síos | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Cur síos | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Cur síos | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Cur síos | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Cur síos | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Cur síos | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Cur síos | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Cur síos | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Cur síos | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/settings-module-admin.html#module-configuration", + + "relUrl": "/ga-rIE/user/settings-module-admin.html#module-configuration" + },"4398": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Athmhaoinigh . Remotely reboot a connected or administered node. Painéal Laige . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" + },"4399": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4400": { + "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" + },"4401": { + "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. 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" + },"4402": { + "doc": "Settings — Modules & Admin", + "title": "Konfiguracja modułu", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Opis | . | Włączony | Toggle MQTT bridge | . | Serwer | MQTT broker address | . | Nazwa użytkownika | Authentication username | . | Hasło | Authentication password | . | Szyfrowanie | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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łączony | Activate serial communication | . | Echo | Echo received serial data back | . | Tryb | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Opis | . | Włączony | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Włączony | Activate store and forward | . | Bicie serca | Periodically announce this node’s store-and-forward capability | . | Wpisów | Maximum stored messages | . | History Return (max) | Max messages to replay | . | History Return (window) | 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 . 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 | . | Włączony | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Opis | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Wiadomości | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | Włączony | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Opis | . | Włączony | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Włączony | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Włączony | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Włączony | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/settings-module-admin.html#konfiguracja-modu%C5%82u", + + "relUrl": "/pl-rPL/user/settings-module-admin.html#konfiguracja-modułu" + },"4403": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Wyczyść bazę węzłów . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Uruchom ponownie . Remotely reboot a connected or administered node. Panel debugowania . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" + },"4404": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4405": { + "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" + },"4406": { + "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. 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" + },"4407": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Beschrijving | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Gebruikersnaam | Authentication username | . | Wachtwoord | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Beschrijving | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beschrijving | . | Enabled | Activate store and forward | . | Hartslag | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Beschrijving | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beschrijving | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Berichten | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beschrijving | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Beschrijving | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beschrijving | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 State | 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beschrijving | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/settings-module-admin.html#module-configuration", + + "relUrl": "/nl-rNL/user/settings-module-admin.html#module-configuration" + },"4408": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Herstart . Remotely reboot a connected or administered node. Debug-paneel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" + },"4409": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4410": { + "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" + },"4411": { + "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. 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" + },"4412": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Beskrivning | . | Aktiverad | Toggle MQTT bridge | . | Server | MQTT broker address | . | Användarnamn | Authentication username | . | Lösenord | Authentication password | . | Kryptering | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Aktiverad | Activate serial communication | . | Eko | Echo received serial data back | . | Typ | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Hastighet | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Beskrivning | . | Aktiverad | Activate notifications | . | Meddelande-utgång | Notify on incoming messages | . | Meddelande-summer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Klock-tecken-utgång | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Aktiv | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beskrivning | . | Aktiverad | Activate store and forward | . | Pulsera | Periodically announce this node’s store-and-forward capability | . | Post | 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 . 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 | . | Aktiverad | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Beskrivning | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Aktivera luftkvalitet | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beskrivning | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Meddelanden | Newline-separated list of messages | . | Skicka klocka | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beskrivning | . | Aktiverad | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Beskrivning | . | Aktiverad | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beskrivning | . | Aktiverad | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Aktiverad | Activate detection sensor | . | Stift 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) | . | Use Input Pullup Mode | Enable the pin’s internal pull-up resistor | . | Minimum Broadcast (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Skicka klocka | Include bell character in alerts | . | Visningsnamn | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beskrivning | . | Aktiverad | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/settings-module-admin.html#module-configuration", + + "relUrl": "/sv-rSE/user/settings-module-admin.html#module-configuration" + },"4413": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Rensa noddatabas . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Starta om . Remotely reboot a connected or administered node. Felsökningspanel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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" + },"4414": { + "doc": "Settings — Modules & Admin", + "title": "Related Topics", + "content": ". | Settings — Radio & User — core radio 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" + },"4415": { + "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" + },"4416": { + "doc": "設定：モジュールと管理", + "title": "設定：モジュールと管理", + "content": "オプションの機能モジュールを設定し、デバイスの管理を行います。 モジュールは、専用の機能で Meshtastic を拡張します。それぞれ個別に有効・無効を切り替えられます。 . 💡 ヒント： 実際に使うモジュールだけを有効にすれば十分です。 使わないモジュールを無効にすると、電波利用時間が減り、バッテリーを節約でき、設定もシンプルになります。 . モジュールの設定は、トグルスイッチ、ドロップダウン、テキストフィールド、スライダーを備えたカード形式のレイアウトを使用します： . . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/settings-module-admin.html", + + "relUrl": "/ja-rJP/user/settings-module-admin.html" + },"4417": { + "doc": "設定：モジュールと管理", + "title": "モジュールの設定", + "content": "MQTT モジュール . インターネット接続のために、メッシュのメッセージを MQTT サーバーとの間で橋渡しします。 これにより、無線の到達範囲を超えてメッシュを拡張したり、ホームオートメーションシステムと連携したりできます。 . | 設定項目 | 説明 | . | 有効 | MQTT ブリッジを切り替え | . | サーバー | MQTT サーバーのアドレス | . | ユーザー名 | 認証用のユーザー名 | . | パスワード | 認証用のパスワード | . | 暗号化 | MQTT ペイロードを暗号化 | . | JSON 出力 | ⚠️ 非推奨：JSON のサポートはファームウェアから削除されました。このフィールドは無視されます | . | TLS | セキュアな接続を使用 | . | ルートトピック | MQTT のベーストピックパス | . | マップ報告 | 公開マップ用に位置を公開 | . 暗号化、プライバシー、サーバーの設定を含む詳しい使い方は、MQTT を参照してください。 . シリアルモジュール . 外部デバイスとの連携（GPS モジュール、センサー、カスタムハードウェア）のために、シリアルポート通信を有効にします。 有効にすると、ノードのシリアルポートで protobuf またはテキストデータを送受信でき、外部のマイコンやコンピューターがメッシュとやり取りできるようになります。 . | 設定項目 | 説明 | . | 有効 | シリアル通信を有効化 | . | エコー | 受信したシリアルデータをそのまま返す | . | モード | テキスト、Protobuf、または NMEA 出力 | . | RX/TX ピン | シリアル接続用の GPIO ピン | . | ボーレート | シリアル通信の速度 | . 外部通知モジュール . 無線機ハードウェアのブザー、LED、振動によるアラートを制御します。 メッセージ到着時に物理的に知らせる必要があるデバイスに便利です。特に無人設置や屋外設置で役立ちます。 . | 設定項目 | 説明 | . | 有効 | 通知を有効化 | . | メッセージ通知 | メッセージ受信時に通知 | . | メッセージのブザー通知 | メッセージにブザーを使用 | . | メッセージの振動通知 | メッセージに振動を使用 | . | ベル通知 | ベル文字の受信時に通知 | . | 出力（GPIO） | 通知出力用のピン | . | アクティブ | アクティブハイまたはアクティブロー | . | 継続時間（ミリ秒） | 通知の長さ | . | I2S をブザーとして使用 | I2S 音声出力を使用 | . Store & Forward モジュール . 一時的にオフラインだったノードのためにメッセージをバッファリングし、それらのノードが再接続したときに再送します。 ノードが頻繁に圏内・圏外を行き来するメッシュに不可欠です。短時間の切断中にメッセージが失われないようにします。 . | 設定項目 | 説明 | . | 有効 | ストア＆フォワードを有効化 | . | ハートビート | このノードのストア＆フォワード機能を定期的に告知する | . | レコード数 | 保存するメッセージの最大数 | . | 履歴の返送（最大） | 再送するメッセージの最大数 | . | 履歴の返送（期間） | 再送する時間の範囲 | . | サーバー | メッシュのストア＆フォワードサーバーとして動作する（十分なメモリが必要、例：PSRAM 搭載の ESP32） | . 💡 ヒント： ストア＆フォワードは、十分なメモリを持つノード（PSRAM 搭載の ESP32）で最も良く機能します。 ルーターノードは通常は常時起動しているため、理想的な候補です。 . レンジテストモジュール . ノード間のリンク品質を評価するための、自動レンジテストツールです。 有効にすると、ノードはカウンターを増やしながらテストメッセージを定期的に送信します。 受信側のノードがこれらのメッセージを記録するため、歩いたり車で移動したりして、後からどの距離でメッセージが届かなくなったかを分析できます。 . | 設定項目 | 説明 | . | 有効 | レンジテストを有効化 | . | 送信間隔（秒） | テスト送信の間隔 | . | CSV を保存 | 受信したテストデータを SD カードに記録 | . テレメトリモジュール . ノードがメッシュと共有するテレメトリデータを制御します。 テレメトリには、デバイスの状態（バッテリー、連続稼働時間）と環境センサーのデータ（温度、湿度、気圧）が含まれます。 . | 設定項目 | 説明 | . | デバイスメトリクスの間隔 | デバイスメトリクスを報告する頻度 | . | 環境メトリクスの間隔 | 環境センサーを報告する頻度 | . | 大気質を有効化 | 粒子状物質センサーのデータを報告 | . | 電力メトリクスを有効化 | 電力使用量を報告 | . 対応センサーと設定の推奨事項については、テレメトリとセンサー を参照してください。 . 定型メッセージモジュール . デバイスの物理ボタンからアクセスできる、あらかじめ設定されたメッセージです（ロータリーエンコーダー、キーパッド、または同様の入力ハードウェアを備えた無線機向け）。 スマートフォンを接続していなくても送信できる、クイック送信メッセージのリストを定義します。フィールドでの使用に最適です。 . | 設定項目 | 説明 | . | 有効 | ⚠️ 非推奨：現在のファームウェアはこのトグルを無視することがあります | . | メッセージ | 改行で区切ったメッセージのリスト | . | ベルを送信 | 送信時にベル音を鳴らす | . | ロータリーエンコーダー | ロータリーエンコーダー入力を有効化 | . | 上／下／押下ピン | 入力用の GPIO ピンの割り当て | . オーディオモジュール . メッシュ上での低帯域幅の音声通信のための、Codec2 音声サポートです。 これは、Codec2 コーデックを使って音声を非常に小さなデータパケットにエンコードする、実験的な機能です。 . | 設定項目 | 説明 | . | 有効 | オーディオモジュールを有効化 | . | Codec2 レート | 音質と帯域幅のトレードオフ | . | I2S ワードセレクト | I2S WS 用の GPIO ピン | . | I2S データ入力 | I2S DIN 用の GPIO ピン | . | I2S データ出力 | I2S DOUT 用の GPIO ピン | . ⚠️ 注意： オーディオには特定のハードウェア（I2S マイクとスピーカー）が必要です。 音質は非常に低帯域です。「聞き取れる無線の声」程度で、電話並みの品質ではないと考えてください。 . リモートハードウェアモジュール . メッシュネットワーク経由での GPIO 制御です。 リモートのノードが、別のノードの GPIO ピンを読み書きできるようにします。リレーの作動、スイッチの読み取り、離れた場所からの外部ハードウェア制御に便利です。 . | 設定項目 | 説明 | . | 有効 | リモート GPIO アクセスを有効化 | . | 未定義ピンを許可 | 任意の GPIO ピンへのアクセスを許可（セキュリティリスク） | . | 利用可能なピン | このノードがリモートの読み書き用に公開する GPIO ピン（最大 4 個） | . ⚠️ 警告： 「未定義ピンを許可」を有効にすると、リモートのノードがすべての GPIO ピンにアクセスでき、無線機自体のハードウェアに干渉するおそれがあります。 GPIO 専用のノードでのみ有効にしてください。 . 隣接ノード情報モジュール . 直接受信した隣接ノードの情報をブロードキャストし、メッシュのトポロジーマッピングを可能にします。 有効にした各ノードは、受信できる他のノードとその信号品質のリストを定期的に共有します。 . | 設定項目 | 説明 | . | 有効 | 隣接ノードのブロードキャストを有効化 | . | 更新間隔（秒） | 隣接ノードのリストをブロードキャストする頻度 | . | LoRa で送信 | MQTT／スマートフォンだけでなく、LoRa 経由でも隣接ノード情報をブロードキャストします。 デフォルトの鍵と名前を使用しているチャンネルでは利用できません | . 隣接ノードのデータをメッシュのトポロジー探索に使う方法については、探索 を参照してください。 . アンビエントライティングモジュール . 対応ハードウェア上の、オンボードの NeoPixel やその他のアドレサブル RGB LED を制御します。 視覚的なステータス表示、通知ライト、装飾的な演出に使用できます。 . | 設定項目 | 説明 | . | LED の状態 | LED のオン／オフを切り替え | . | 電流 | LED の電流制限（0〜31） | . | 赤／緑／青 | 各色チャンネルの値（0〜255） | . 検知センサーモジュール . ノードを、動きやドアを検知するセンサーアラートシステムに変えます。 GPIO ピンが状態の変化（動きの検知、ドアの開放）を検出すると、ノードはメッシュ経由でアラートメッセージをブロードキャストします。 . | 設定項目 | 説明 | . | 有効 | 検知センサーを有効化 | . | 監視ピン | センサーに接続された GPIO ピン | . | 検知トリガーの種類 | ピンの状態を検知イベントにどう対応させるか（例：アクティブハイ／ロー、エッジトリガー） | . | 入力プルアップモードを使用 | ピンの内蔵プルアップ抵抗を有効にする | . | 最小ブロードキャスト間隔（秒） | アラートのブロードキャスト間の最小時間 | . | 状態ブロードキャスト（秒） | 定期的な状態ブロードキャストの間隔 | . | ベルを送信 | アラートにベル文字を含める | . | 分かりやすい名前 | このセンサーのカスタム名 | . Paxcounter モジュール . WiFi と BLE のプローブ要求を使った人数カウンターです。 スマートフォンやノートパソコンがネットワークを探すときに発するプローブ要求を受動的に受信して、近くのデバイスを数えます。 ESP32 デバイスでのみ利用できます。 . | 設定項目 | 説明 | . | 有効 | 人数カウントを有効化 | . | 更新間隔（秒） | カウントを報告する頻度 | . 💡 ヒント： Paxcounter は、登山口やイベント会場などの人出を推定するのに便利です。 カウントはおおよその値です。1 人が複数のデバイスを持っていることがあります。 . TAK モジュール . ATAK および WinTAK と相互運用するための、Team Awareness Kit 連携です。 詳しい設定と使い方は、TAK 連携 を参照してください。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/settings-module-admin.html#%E3%83%A2%E3%82%B8%E3%83%A5%E3%83%BC%E3%83%AB%E3%81%AE%E8%A8%AD%E5%AE%9A", + + "relUrl": "/ja-rJP/user/settings-module-admin.html#モジュールの設定" + },"4418": { + "doc": "設定：モジュールと管理", + "title": "管理", + "content": "リモート管理 . 管理者鍵を共有しているノードをリモートで設定します： . | ノードリストで対象のノードを選択します。 | そのノードの「設定」に移動します。 | 設定を変更します。 | 「保存」をタップします。変更がメッシュ経由で送信されます。 | . ⚠️ 必要条件： 自分のノードと対象のノードの両方に管理者鍵が設定されていること。 . ノードデータベースの整理 . 設定可能な期間内に受信していない古いノードを、ローカルデータベースから削除します。 . 工場出荷時リセット . すべての設定を工場出荷時のデフォルトにリセットします。 この操作は取り消せません。 . 再起動 . 接続中または管理中のノードをリモートで再起動します。 . デバッグ . 診断出力の表示・絞り込み・エクスポートを行う「パケット」タブと「アプリログ」タブを開きます。 詳しい手順は、デバッグログ を参照してください。 . リモート管理のトラブルシューティング . | 「対象ノードから応答がありません」：対象が圏外、オフライン、または管理者鍵が一致していない可能性があります。 両方のノードで管理者鍵が一致しているか確認してください。 | 変更が適用されない：一部の設定は、反映に再起動が必要です。 保存後に「再起動」を実行してみてください。 | リモートの設定が表示されない：自分のノードに、対象ノードの管理者鍵があることを確認してください。 管理チャンネルは、管理者鍵を設定すると自動的に構成されます。 | . ", + "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#管理" + },"4419": { + "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", + "content": ". | 設定：無線機とユーザー：基本の無線機とユーザープロファイルの設定 | モジュール設定リファレンス：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-radio-user.html#関連トピック" - },"4454": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html#settings--radio--user", + "relUrl": "/ja-rJP/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. 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": "/ca-rES/user/settings-radio-user.html#settings--radio--user" - },"4455": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Descripció | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html#user-settings", + "relUrl": "/hu-rHU/user/settings-module-admin.html#settings--modules--admin" + },"4421": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Leírás | . | Engedélyezve | Toggle MQTT bridge | . | Szerver | MQTT broker address | . | Felhasználónév | Authentication username | . | Jelszó | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Engedélyezve | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Leírás | . | Engedélyezve | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Leírás | . | Engedélyezve | Activate store and forward | . | Heartbeat jel | Periodically announce this node’s store-and-forward capability | . | Bejegyzések | Maximum stored messages | . | History Return (max) | Max messages to replay | . | History Return (window) | 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 . 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 | . | Engedélyezve | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Leírás | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Leírás | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Üzenetek | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Leírás | . | Engedélyezve | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Leírás | . | Engedélyezve | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Leírás | . | Engedélyezve | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 State | 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 | . | Engedélyezve | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Leírás | . | Engedélyezve | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/settings-module-admin.html#module-configuration", - "relUrl": "/ca-rES/user/settings-radio-user.html#user-settings" - },"4456": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | Descripció | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Descripció | Default | . | Regió | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Descripció | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Descripció | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Descripció | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Descripció | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Descripció | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Descripció | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + "relUrl": "/hu-rHU/user/settings-module-admin.html#module-configuration" + },"4422": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Csomópont-adatbázis tisztítása . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Újraindítás . Remotely reboot a connected or administered node. Hibakereső panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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": "/ca-rES/user/settings-radio-user.html#configuration" - },"4457": { - "doc": "Settings — Radio & User", + "relUrl": "/hu-rHU/user/settings-module-admin.html#adminisztráció" + },"4423": { + "doc": "Settings — Modules & Admin", "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", + "content": ". | Settings — Radio & User — core radio 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": "/ca-rES/user/settings-radio-user.html#related-topics" - },"4458": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", + "relUrl": "/hu-rHU/user/settings-module-admin.html#related-topics" + },"4424": { + "doc": "Settings — Modules & Admin", + "title": "Settings — Modules & Admin", "content": " ", - "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html", + "url": "/Meshtastic-Android/main/hu-rHU/user/settings-module-admin.html", - "relUrl": "/ca-rES/user/settings-radio-user.html" - },"4459": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-radio-user.html#settings--radio--user", + "relUrl": "/hu-rHU/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. 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": "/sr-rLatn/user/settings-radio-user.html#settings--radio--user" - },"4460": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Опис | . | Дуго име | Your display name (up to 39 characters) | . | Кратко име | 4-character abbreviated name | . | Лиценцирани оператор | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-radio-user.html#user-settings", + "relUrl": "/ht-rHT/user/settings-module-admin.html#settings--modules--admin" + },"4426": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Deskripsyon | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Deskripsyon | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Deskripsyon | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Deskripsyon | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Deskripsyon | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Deskripsyon | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Deskripsyon | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Deskripsyon | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Deskripsyon | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/settings-module-admin.html#module-configuration", - "relUrl": "/sr-rLatn/user/settings-radio-user.html#user-settings" - },"4461": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Подешавања уређаја . | Setting | Опис | Подразумевано | . | Улога | Node behavior (Client, Router, etc.) | Клијент | . | Режим реемитовања | How the node retransmits messages | Сви | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Онемогућено | . LoRA подешавања . | Setting | Опис | Подразумевано | . | Регион | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Подешавања приказа . | Setting | Опис | . | Screen Timeout | Time before display sleeps | . | Јединице приказа | Metric or Imperial | . | Тип OLED-а | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Подешавања позиције . | Setting | Опис | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Паметно позиционирање | Enable movement-based broadcasting | . | Фиксна локација | Use a manually set position | . Подешавања напајња . | Setting | Опис | . | Уштеда енергије | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Конфигурација мреже . | Setting | Опис | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Блутут подешавања . | Setting | Опис | . | Bluetooth Enabled | Enable/disable BLE radio | . | Мод упаривања | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Сигурносна подешавања . | Setting | Опис | . | Javni ključ | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Privatni ključ | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + "relUrl": "/ht-rHT/user/settings-module-admin.html#module-configuration" + },"4427": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Rekòmanse . Remotely reboot a connected or administered node. Panno Debug . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. 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": "/sr-rLatn/user/settings-radio-user.html#configuration" - },"4462": { - "doc": "Settings — Radio & User", + "relUrl": "/ht-rHT/user/settings-module-admin.html#administrasyon" + },"4428": { + "doc": "Settings — Modules & Admin", "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", + "content": ". | Settings — Radio & User — core radio 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": "/sr-rLatn/user/settings-radio-user.html#related-topics" - },"4463": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", + "relUrl": "/ht-rHT/user/settings-module-admin.html#related-topics" + },"4429": { + "doc": "Settings — Modules & Admin", + "title": "Settings — Modules & Admin", "content": " ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-radio-user.html", + "url": "/Meshtastic-Android/main/ht-rHT/user/settings-module-admin.html", - "relUrl": "/sr-rLatn/user/settings-radio-user.html" - },"4464": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/settings-radio-user.html#settings--radio--user", + "relUrl": "/ht-rHT/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. 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": "/ko-rKR/user/settings-radio-user.html#settings--radio--user" - },"4465": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | 설명 | . | 긴 이름 | Your display name (up to 39 characters) | . | 짧은 이름 | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/settings-radio-user.html#user-settings", + "relUrl": "/gl-rES/user/settings-module-admin.html#settings--modules--admin" + },"4431": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descrición | . | Enabled | Toggle MQTT bridge | . | Server | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Enabled | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descrición | . | Enabled | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrición | . | Enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 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 . 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 | . | Enabled | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descrición | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrición | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Messages | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrición | . | Enabled | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descrición | . | Enabled | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrición | . | Enabled | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | Enabled | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrición | . | Enabled | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/gl-rES/user/settings-module-admin.html#module-configuration", - "relUrl": "/ko-rKR/user/settings-radio-user.html#user-settings" - },"4466": { - "doc": "Settings — Radio & User", - "title": "설정", - "content": "장치 설정 . | Setting | 설명 | 기본값 | . | 역할 | Node behavior (Client, Router, etc.) | Client | . | 중계 모드 | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa 설정 . | Setting | 설명 | 기본값 | . | 지역 | Regulatory region for frequency bands | Unset (must configure) | . | 모뎀 프리셋 | Speed/range tradeoff | LongFast | . | Hop 제한 | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | 주파수 오프셋 | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 화면 설정 . | Setting | 설명 | . | 화면 끄기 시간 | Time before display sleeps | . | 단위 표시 | Metric or Imperial | . | OLED 타입 | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . 위치 설정 . | Setting | 설명 | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . 전원 설정 . | Setting | 설명 | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . 네트워크 설정 . | Setting | 설명 | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | 네트워크 암호 | . | NTP 서버 | Time synchronization server | . | Syslog Server | Remote logging server | . 블루투스 설정 . | Setting | 설명 | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | 고정 PIN | PIN code for pairing (default: 123456) | . 보안 설정 . | Setting | 설명 | . | 공개 키 | Your node’s public key (read-only) | . | Admin 키 | Key for remote administration | . | 개인 키 | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | 관리 모드 | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#%EC%84%A4%EC%A0%95", + "relUrl": "/gl-rES/user/settings-module-admin.html#module-configuration" + },"4432": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reiniciar . Remotely reboot a connected or administered node. 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. 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": "/ko-rKR/user/settings-radio-user.html#설정" - },"4467": { - "doc": "Settings — Radio & User", + "relUrl": "/gl-rES/user/settings-module-admin.html#administration" + },"4433": { + "doc": "Settings — Modules & Admin", "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", + "content": ". | Settings — Radio & User — core radio 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": "/ko-rKR/user/settings-radio-user.html#related-topics" - },"4468": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", + "relUrl": "/gl-rES/user/settings-module-admin.html#related-topics" + },"4434": { + "doc": "Settings — Modules & Admin", + "title": "Settings — Modules & Admin", "content": " ", - "url": "/Meshtastic-Android/main/ko-rKR/user/settings-radio-user.html", + "url": "/Meshtastic-Android/main/gl-rES/user/settings-module-admin.html", - "relUrl": "/ko-rKR/user/settings-radio-user.html" - },"4469": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/settings-radio-user.html#settings--radio--user", + "relUrl": "/gl-rES/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. 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": "/ro-rRO/user/settings-radio-user.html#settings--radio--user" - },"4470": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Descriere | . | Nume lung | Your display name (up to 39 characters) | . | Nume scurt | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/settings-radio-user.html#user-settings", + "relUrl": "/tr-rTR/user/settings-module-admin.html#settings--modules--admin" + },"4436": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Açıklaması | . | Açık | Toggle MQTT bridge | . | Sunucu | MQTT broker address | . | Kullanıcı adı | Authentication username | . | Şifre | Authentication password | . | Encryption | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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ı | . | Açık | Activate serial communication | . | Echo | Echo received serial data back | . | Mod | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Açıklaması | . | Açık | Activate notifications | . | Uyarı Mesajı | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Aktif | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Açıklaması | . | Açık | Activate store and forward | . | Kalp atışı | Periodically announce this node’s store-and-forward capability | . | Records | Maximum stored messages | . | History Return (max) | Max messages to replay | . | History Return (window) | 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 . 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ı | . | Açık | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Açıklaması | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Açıklaması | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Mesajlar | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Açıklaması | . | Açık | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Açıklaması | . | Açık | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Açıklaması | . | Açık | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 State | 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ı | . | Açık | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Açıklaması | . | Açık | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/settings-module-admin.html#module-configuration", - "relUrl": "/ro-rRO/user/settings-radio-user.html#user-settings" - },"4471": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | Descriere | Prestabilit | . | Role | Node behavior (Client, Router, etc.) | Client | . | Mod de redifuzare | How the node retransmits messages | Toate | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Descriere | Prestabilit | . | Regiune | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Descriere | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Descriere | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Poziție inteligentă | Enable movement-based broadcasting | . | Poziție fixă | Use a manually set position | . Configurare Putere . | Setting | Descriere | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Descriere | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Configurare Bluetooth . | Setting | Descriere | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | PIN fix | PIN code for pairing (default: 123456) | . Security Config . | Setting | Descriere | . | Chei publice | Your node’s public key (read-only) | . | Cheie Administrator | Key for remote administration | . | Cheia privată | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Mod Gestionat | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + "relUrl": "/tr-rTR/user/settings-module-admin.html#module-configuration" + },"4437": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Clean Node Database . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Yeniden başlat . Remotely reboot a connected or administered node. 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. 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": "/ro-rRO/user/settings-radio-user.html#configuration" - },"4472": { - "doc": "Settings — Radio & User", + "relUrl": "/tr-rTR/user/settings-module-admin.html#yönetim" + },"4438": { + "doc": "Settings — Modules & Admin", "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", + "content": ". | Settings — Radio & User — core radio 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": "/ro-rRO/user/settings-radio-user.html#related-topics" - },"4473": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", + "relUrl": "/tr-rTR/user/settings-module-admin.html#related-topics" + },"4439": { + "doc": "Settings — Modules & Admin", + "title": "Settings — Modules & Admin", "content": " ", - "url": "/Meshtastic-Android/main/ro-rRO/user/settings-radio-user.html", + "url": "/Meshtastic-Android/main/tr-rTR/user/settings-module-admin.html", - "relUrl": "/ro-rRO/user/settings-radio-user.html" - },"4474": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/settings-radio-user.html#settings--radio--user", + "relUrl": "/tr-rTR/user/settings-module-admin.html" + },"4440": { + "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. 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": "/ga-rIE/user/settings-radio-user.html#settings--radio--user" - },"4475": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Cur síos | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/settings-radio-user.html#user-settings", + "relUrl": "/es-rES/user/settings-module-admin.html#settings--modules--admin" + },"4441": { + "doc": "Settings — Modules & Admin", + "title": "Module Configuration", + "content": "MQTT Module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems. | Setting | Descripción | . | Habilitado | Toggle MQTT bridge | . | Servidor | MQTT broker address | . | Usuario | Authentication username | . | Contraseña | Authentication password | . | Cifrado | Encrypt MQTT payloads | . | JSON Output | ⚠️ Deprecated — JSON support removed from firmware; field is ignored | . | TLS | Use secure connection | . | Root Topic | Base MQTT topic path | . | Map Report | Publish position for public map | . See MQTT 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 | . | Habilitado | Activate serial communication | . | Echo | Echo received serial data back | . | Mode | Text, Protobuf, or NMEA output | . | RX/TX Pins | GPIO pins for serial connection | . | Baud Rate | Serial communication speed | . External Notification Module . Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. | Setting | Descripción | . | Habilitado | Activate notifications | . | Alert Message | Notify on incoming messages | . | Alert Message Buzzer | Use buzzer for messages | . | Alert Message Vibra | Use vibration for messages | . | Alert Bell | Notify on bell character | . | Output (GPIO) | Pin for notification output | . | Active | High or Low active | . | Duration (ms) | Notification length | . | Use I2S as Buzzer | Use I2S audio output | . Store & Forward Module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descripción | . | Habilitado | Activate store and forward | . | Pulso de vida | Periodically announce this node’s store-and-forward capability | . | Registros | 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 . 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 | . | Habilitado | Activate range testing | . | Sender Interval (s) | Time between test transmissions | . | Save CSV | Log received test data to SD card | . Telemetry Module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). | Setting | Descripción | . | Device Metrics Interval | How often to report device metrics | . | Environment Metrics Interval | How often to report environment sensors | . | Air Quality Enabled | Report particulate sensor data | . | Power Metrics Enabled | Report power usage | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message Module . Pre-configured messages accessible from the device’s physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descripción | . | Enabled | ⚠️ Deprecated — current firmware may ignore this toggle | . | Mensajes | Newline-separated list of messages | . | Send Bell | Play bell sound on send | . | Rotary Encoder | Enable rotary encoder input | . | Up/Down/Press Pins | GPIO pin assignments for input | . Audio Module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descripción | . | Habilitado | Activate audio module | . | Codec2 Rate | Audio quality/bandwidth tradeoff | . | I2S Word Select | GPIO pin for I2S WS | . | I2S Data In | GPIO pin for I2S DIN | . | I2S Data Out | GPIO pin for I2S DOUT | . ⚠️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware Module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. | Setting | Descripción | . | Habilitado | Activate remote GPIO access | . | Allow Undefined Pins | Allow access to any GPIO pin (security risk) | . | Available Pins | Up to 4 GPIO pins this node exposes for remote read/write | . ⚠️ Warning: Enabling “Allow Undefined Pins” gives remote nodes access to all GPIO pins, which could interfere with the radio’s own hardware. Only enable on dedicated GPIO nodes. Neighbor Info Module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descripción | . | Habilitado | Activate neighbor broadcasting | . | Update Interval (s) | 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 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 | . | LED State | 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 | . | Habilitado | Activate detection sensor | . | Monitor Pin | 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 (s) | Minimum time between alert broadcasts | . | State Broadcast (s) | Periodic state broadcast interval | . | Send Bell | Include bell character in alerts | . | Friendly Name | Custom name for this sensor | . Paxcounter Module . People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descripción | . | Habilitado | Activate people counting | . | Update Interval (s) | How often to report counts | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. TAK Module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. See TAK Integration for detailed setup and usage. ", + "url": "/Meshtastic-Android/main/es-rES/user/settings-module-admin.html#module-configuration", - "relUrl": "/ga-rIE/user/settings-radio-user.html#user-settings" - },"4476": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | Cur síos | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Cur síos | Default | . | Réigiún | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Cur síos | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Cur síos | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Cur síos | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Cur síos | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | 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 (default: 123456) | . Security Config . | Setting | Cur síos | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + "relUrl": "/es-rES/user/settings-module-admin.html#module-configuration" + },"4442": { + "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. | . ⚠️ Requires: Admin key configured on both your node and the target node. Limpiar nodos de la base de datos . Removes stale nodes from your local database that haven’t been heard in a configurable time window. Factory Reset . Resets all settings to factory defaults. This cannot be undone. Reiniciar . Remotely reboot a connected or administered node. 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. 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": "/ga-rIE/user/settings-radio-user.html#configuration" - },"4477": { - "doc": "Settings — Radio & User", + "relUrl": "/es-rES/user/settings-module-admin.html#administración" + },"4443": { + "doc": "Settings — Modules & Admin", "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", + "content": ". | Settings — Radio & User — core radio 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": "/ga-rIE/user/settings-radio-user.html#related-topics" - },"4478": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", + "relUrl": "/es-rES/user/settings-module-admin.html#related-topics" + },"4444": { + "doc": "Settings — Modules & Admin", + "title": "Settings — Modules & Admin", "content": " ", - "url": "/Meshtastic-Android/main/ga-rIE/user/settings-radio-user.html", + "url": "/Meshtastic-Android/main/es-rES/user/settings-module-admin.html", - "relUrl": "/ga-rIE/user/settings-radio-user.html" - },"4479": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4480": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | תיאור | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/settings-radio-user.html#user-settings", - - "relUrl": "/iw-rIL/user/settings-radio-user.html#user-settings" - },"4481": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | תיאור | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | תיאור | Default | . | אזור | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | תיאור | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | תיאור | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | תיאור | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | תיאור | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | תיאור | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | תיאור | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/iw-rIL/user/settings-radio-user.html#configuration" - },"4482": { - "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" - },"4483": { - "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" - },"4484": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4485": { - "doc": "Settings — Radio & User", - "title": "Användarinställningar", - "content": "User Profile . | Setting | Beskrivning | . | Långt namn | Your display name (up to 39 characters) | . | Kort namn | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "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" - },"4486": { - "doc": "Settings — Radio & User", - "title": "Konfiguration", - "content": "Enhetskonfiguration . | Setting | Beskrivning | Förvald | . | Roll | Node behavior (Client, Router, etc.) | Client | . | Återutsändningsläge | How the node retransmits messages | Alla | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Beskrivning | Förvald | . | Region | Regulatory region for frequency bands | Unset (must configure) | . | Modem-förinställningar | Speed/range tradeoff | LongFast | . | Hoppgräns | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frekvensförskjutning | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Beskrivning | . | Tidsgräns för display | Time before display sleeps | . | Enheter | Metric or Imperial | . | OLED-typ | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Beskrivning | . | GPS Enabled | Enable/disable GPS | . | Intervall för GPS-uppdatering | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart position | Enable movement-based broadcasting | . | Fast plats | Use a manually set position | . Ströminställningar . | Setting | Beskrivning | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Beskrivning | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Nätverkslösenord | . | NTP-server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth-inställningar . | Setting | Beskrivning | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fast PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Beskrivning | . | Publik nyckel | Your node’s public key (read-only) | . | Admin-nyckel | Key for remote administration | . | Privat nyckel | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Hanterat läge | Restrict non-admin channel changes | . | Säkerhetskopiera nycklar | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#konfiguration", - - "relUrl": "/sv-rSE/user/settings-radio-user.html#konfiguration" - },"4487": { - "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" - },"4488": { - "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" - },"4489": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4490": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Deskripsyon | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/settings-radio-user.html#user-settings", - - "relUrl": "/ht-rHT/user/settings-radio-user.html#user-settings" - },"4491": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | Deskripsyon | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Deskripsyon | Default | . | Rejyon | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Deskripsyon | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Deskripsyon | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Deskripsyon | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Deskripsyon | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Deskripsyon | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Deskripsyon | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/ht-rHT/user/settings-radio-user.html#configuration" - },"4492": { - "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" - },"4493": { - "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" - },"4494": { - "doc": "Asetukset — Radio ja käyttäjä", - "title": "Asetukset — Radio ja käyttäjä", - "content": "Määritä radion laitteisto ja käyttäjätunnistetiedot. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/settings-radio-user.html", - - "relUrl": "/fi-rFI/user/settings-radio-user.html" - },"4495": { - "doc": "Asetukset — Radio ja käyttäjä", - "title": "Käyttäjäasetukset", - "content": "Käyttäjäprofiili . | Asetus | Kuvaus | . | Pitkä nimi | Näyttönimesi (enintään 39 merkkiä) | . | Lyhytnimi | 4-merkkinen lyhytnimi | . | Lisensoitu radioamatööri | Ota käyttöön, jos sinulla on radioamatöörilupa (mahdollistaa suuremman lähetystehon) | . Muutosten käyttöönotto . Asetusten muuttamisen jälkeen napauta Tallenna kirjoittaaksesi määritykset radioon. Laite voidaan käynnistää uudelleen muutosten käyttöönottoa varten. ", - "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" - },"4496": { - "doc": "Asetukset — Radio ja käyttäjä", - "title": "Asetukset", - "content": "Laitteen asetukset . | Asetus | Kuvaus | Oletus | . | Rooli | Radion rooli (Client, Router jne.) | Client | . | Uudelleenlähetyksen tila | Miten radio välittää viestejä eteenpäin | Kaikki | . | Radiotiedon lähetys (s) | Radion tietojen lähetysväli | 10800 | . | Kaksoisnapautuspainike | Toiminto painikkeen kaksoisnapautukselle | Ei käytössä | . LoRa:n asetukset . | Asetus | Kuvaus | Oletus | . | Alue | Taajuusalueiden sääntelyalue | Ei asetettu (on määritettävä) | . | Modeemin esiasetus | Nopeuden ja kantaman välinen kompromissi | LongFast | . | Hyppyraja | Suurin hyppyjen määrä | 3 | . | Lähetysteho | Lähetysteho (dBm): 0 = alueen sallima enimmäisteho | 0 (alueen enimmäisteho) | . | Taajuuspoikkeama | Taajuuden hienosäätö (MHz) | 0 | . | Kanavan kaistanleveys | Kaistanleveysasetus | Esiasetuksen oletusarvo | . ⚠️ Tärkeää: Sinun täytyy määrittää alueesi ennen lähettämistä. Lähettäminen väärällä alueasetuksella voi rikkoa paikallisia radiomääräyksiä. Katso alueasetusten määritysopas meshtastic.org-sivustolta saadaksesi lisätietoja. Esiasetukset . 💡 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 | 5.5 kbps | −10 dB | Lyhyen kantaman esikaupunkialueet; kohtalainen rakennustiheys | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Esikaupunkialueet; kohtalainen rakennustiheys | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Esikaupunki-/maaseutualueet; kohtalainen kantama ja hitaampi nopeus | . | Long Turbo | ~10 km | 4.4 kbps | −12.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 | 5.5 kbps | −12.5 dB | EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Medium Fast -asetukseen | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Long Fast -asetukseen | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz -alue (62,5 kHz BW); välttää häiriöitä muiden laitteiden kanssa | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz -alue (62,5 kHz BW); verrattavissa Long Fast -asetukseen | . | 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ä. Sovelluksen esiasetusvalikossa ne näkyvät nimillä Lyhyt kantama - Nopea, Pitkä kantama - Nopea, Lite - Nopea, Kapea - Nopea ja niin edelleen. Modeemiesiasetuksen valitseminen . 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. | . ⚠️ Tärkeää: Kaikkien samalla kanavalla olevien radioiden täytyy käyttää samaa modeemiesiasetusta. Radiot, joiden modeemiesiasetukset eivät täsmää, eivät voi viestiä keskenään, vaikka ne käyttäisivät samaa taajuutta ja salausavainta. 💡 Vinkki: Yllä olevat 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 . | Asetus | Kuvaus | . | Näytön aikakatkaisu | Aika ennen näytön siirtymistä lepotilaan | . | Näyttöyksiköt | Metrinen tai imperiaalinen järjestelmä | . | OLED-tyyppi | Auto, SSD1306, SH1106, SH1107 | . | Kompassin suunta | Kompassinäytön kiertosäätö (0°, 90°, 180°, 270°) | . | Kompassipohjoinen | ⚠️ Vanhentunut — korvattu Kompassin suunta -asetuksella; näkyy edelleen vanhemmissa laiteohjelmistoversioissa | . Sijainnin asetukset . | Asetus | Kuvaus | . | GPS-käytössä | Ota GPS käyttöön tai poista käytöstä | . | GPS-päivitysväli | Kuinka usein GPS-paikannusta päivitetään | . | Sijainnin lähetys (s) | Kuinka usein sijaintia jaetaan | . | Älykäs sijainti | Ota liikkeeseen perustuva lähetys käyttöön | . | Kiinteä sijainti | Käytä manuaalisesti asetettua sijaintia | . Virran asetukset . | Asetus | Kuvaus | . | Virransäästö | Ota vähän virtaa kuluttava lepotila käyttöön | . | Sammuta jälkeen (s) | Automaattisen sammutuksen ajastin | . | ADC-kerroin | Akun jännitteen kalibrointikerroin | . | Odota Bluetoothia (s) | Aika Bluetooth-yhteyden odottamiseen käynnistyksen yhteydessä | . | Mesh SDS -aikakatkaisu (s) | Erittäin syvän lepotilan aikakatkaisu | . Verkon asetukset . | Asetus | Kuvaus | . | WiFi käytössä | Ota WiFi-radio käyttöön (ESP32-laitteet) | . | WiFi SSID | Verkon nimi, johon yhdistetään | . | WiFi PSK | Verkon salasana | . | NTP-palvelin | Ajan synkronointipalvelin (NTP-palvelin) | . | Syslog-palvelin | Etätietojen palvelin | . Bluetooth asetukset . | Asetus | Kuvaus | . | Bluetooth käytössä | Ota Bluetooth-radio käyttöön tai poista käytöstä | . | Pariliitostila | Kiinteä PIN-koodi, satunnainen PIN-koodi tai ei PIN-koodia | . | Kiinteä PIN-koodi | PIN-koodi pariliitosta varten (oletus: 123456) | . Turvallisuusasetukset . | Asetus | Kuvaus | . | Julkinen avain | Radiosi julkinen avain (vain luku) | . | Ylläpitäjän avain | Avain etähallintaa varten | . | Yksityinen avain | Radiosi yksityinen avain (käsittele turvallisesti) | . | Ylläpitokanava käytössä | ⚠️ Poistettu — määritetään nyt automaattisesti, kun ylläpitoavain asetetaan | . | Virheenkorjausloki | Tulosta reaaliaikainen virheenkorjausloki sarjaportin tai bluetoothin kautta | . | Sarjaportti käytössä | Ota sarjakonsoliyhteys käyttöön (siirretty laiteasetuksista) | . | Hallintatila | Rajoita muutokset muihin kuin ylläpitokanaviin | . | Varmuuskopioi avaimet | Tallenna radion avaimista salattu varmuuskopio tälle laitteelle (vain Android) | . | Palauta avaimet | Kirjoita varmuuskopioidut avaimet takaisin radioon (käytettävissä, kun varmuuskopio on olemassa) | . | Poista avaimen varmuuskopio | Poista tälle laitteelle tallennettu avainten varmuuskopio | . | Suojaustaso | Pakettien aitous – miten allekirjoittamattomia tai välitettyjä paketteja käsitellään: Tiukka, Tasapainoinen tai Yhteensopiva (edellyttää tuettua laiteohjelmistoa; Tiukka pyytää vahvistuksen) | . 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#asetukset", - - "relUrl": "/fi-rFI/user/settings-radio-user.html#asetukset" - },"4497": { - "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" - },"4498": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4499": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Descrición | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/gl-rES/user/settings-radio-user.html#user-settings", - - "relUrl": "/gl-rES/user/settings-radio-user.html#user-settings" - },"4500": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | Descrición | Default | . | Role | Node behavior (Client, Router, etc.) | Cliente | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Descrición | Default | . | Rexión | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Descrición | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Descrición | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Descrición | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Descrición | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Descrición | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Descrición | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/gl-rES/user/settings-radio-user.html#configuration" - },"4501": { - "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" - },"4502": { - "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" - },"4503": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4504": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Опис | . | Довга назва | Your display name (up to 39 characters) | . | Коротка назва | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html#user-settings", - - "relUrl": "/uk-rUA/user/settings-radio-user.html#user-settings" - },"4505": { - "doc": "Settings — Radio & User", - "title": "Налаштування", - "content": "Налаштування пристрою . | Setting | Опис | За замовчуванням | . | Роль | Node behavior (Client, Router, etc.) | Клієнт | . | Режим ретрансляції | How the node retransmits messages | Усі | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Налаштування LoRa . | Setting | Опис | За замовчуванням | . | Регіон | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Налаштування дисплею . | Setting | Опис | . | Screen Timeout | Time before display sleeps | . | Одиниці виміру | Metric or Imperial | . | Тип OLED | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Опис | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Інтелектуальне передавання позиції | Enable movement-based broadcasting | . | Фіксована позиція | Use a manually set position | . Налаштування живлення . | Setting | Опис | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Налаштування мережі . | Setting | Опис | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP-сервер | Time synchronization server | . | Syslog Server | Remote logging server | . Налаштування Bluetooth . | Setting | Опис | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Фіксований PIN | PIN code for pairing (default: 123456) | . Налаштування безпеки . | Setting | Опис | . | Відкритий ключ | Your node’s public key (read-only) | . | Ключ адміністратора | Key for remote administration | . | Приватний ключ | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Керований режим | Restrict non-admin channel changes | . | Резервні ключі | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#%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#налаштування" - },"4506": { - "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" - },"4507": { - "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" - },"4508": { + "relUrl": "/es-rES/user/settings-module-admin.html" + },"4445": { "doc": "Settings — Radio & User", "title": "Settings — Radio & User", "content": "Configure your radio hardware and user identity parameters. ", "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" - },"4509": { + },"4446": { "doc": "Settings — Radio & User", "title": "Benutzereinstellungen", "content": "User Profile . | Einstellung | Beschreibung | . | Langer Name | Your display name (up to 39 characters) | . | Kurzname | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", "url": "/Meshtastic-Android/main/de-rDE/user/settings-radio-user.html#benutzereinstellungen", "relUrl": "/de-rDE/user/settings-radio-user.html#benutzereinstellungen" - },"4510": { + },"4447": { "doc": "Settings — Radio & User", "title": "Einstellungen", "content": "Geräteeinstellungen . | Einstellung | Beschreibung | Standardwert | . | Rolle | Node behavior (Client, Router, etc.) | Client | . | Weiterleitungsmodus | How the node retransmits messages | Alle | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Deaktiviert | . LoRa Einstellungen . | Einstellung | Beschreibung | Standardwert | . | Region | Regulatory region for frequency bands | Unset (must configure) | . | Modem Voreinstellungen | Speed/range tradeoff | LongFast | . | Sprungweite | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequenzversatz | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | MEDIUM_FAST | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | MEDIUM_SLOW | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbit/s | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0,18 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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. 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. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Anzeigeeinstellungen . | Einstellung | Beschreibung | . | Anzeigeabschaltung | Time before display sleeps | . | Anzeigeeinheiten | Metric or Imperial | . | OLED Typ | Auto, SSD1306, SH1106, SH1107 | . | Kompassausrichtung | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Standorteinstellungen . | Einstellung | Beschreibung | . | GPS Enabled | Enable/disable GPS | . | GPS Aktualisierungsintervall | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Intelligente Position | Enable movement-based broadcasting | . | Fester Standort | Use a manually set position | . Energie Einstellungen . | Einstellung | Beschreibung | . | Energiesparen | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Netzwerkeinstellungen . | Einstellung | Beschreibung | . | WLAN aktiviert | Enable WiFi radio (ESP32 devices) | . | WLAN SSID | Network name to connect to | . | WLAN PSK | Netzwerkpasswort | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Einstellungen . | Einstellung | Beschreibung | . | Bluetooth Enabled | Enable/disable BLE radio | . | Kopplungsmodus | Fixed PIN, Random PIN, or No PIN | . | Feste PIN | PIN code for pairing (default: 123456) | . Sicherheitseinstellungen . | Einstellung | Beschreibung | . | Öffentlicher Schlüssel | Your node’s public key (read-only) | . | Administrativer Schlüssel | Key for remote administration | . | Privater Schlüssel | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Fehlersuchprotokolle (Debug) | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Verwalteter Modus | Restrict non-admin channel changes | . | Schlüssel sichern | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#einstellungen", "relUrl": "/de-rDE/user/settings-radio-user.html#einstellungen" - },"4511": { + },"4448": { "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" - },"4512": { + },"4449": { "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" - },"4513": { + },"4450": { "doc": "Settings — Radio & User", "title": "Settings — Radio & User", "content": "Configure your radio hardware and user identity parameters. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/settings-radio-user.html#settings--radio--user", + "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html#settings--radio--user", - "relUrl": "/hr-rHR/user/settings-radio-user.html#settings--radio--user" - },"4514": { + "relUrl": "/ca-rES/user/settings-radio-user.html#settings--radio--user" + },"4451": { "doc": "Settings — Radio & User", "title": "User Settings", - "content": "User Profile . | Setting | Opis | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/settings-radio-user.html#user-settings", + "content": "User Profile . | Setting | Descripció | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html#user-settings", - "relUrl": "/hr-rHR/user/settings-radio-user.html#user-settings" - },"4515": { + "relUrl": "/ca-rES/user/settings-radio-user.html#user-settings" + },"4452": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . | Setting | Opis | Zadano | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Opis | Zadano | . | Regija | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Opis | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Opis | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Opis | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Opis | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Postavke Bluetootha . | Setting | Opis | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Opis | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + "content": "Device Config . | Setting | Descripció | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Descripció | Default | . | Regió | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Descripció | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Descripció | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Descripció | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Descripció | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Descripció | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Descripció | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - "relUrl": "/hr-rHR/user/settings-radio-user.html#configuration" - },"4516": { + "relUrl": "/ca-rES/user/settings-radio-user.html#configuration" + },"4453": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html#related-topics", - "relUrl": "/hr-rHR/user/settings-radio-user.html#related-topics" - },"4517": { + "relUrl": "/ca-rES/user/settings-radio-user.html#related-topics" + },"4454": { "doc": "Settings — Radio & User", "title": "Settings — Radio & User", "content": " ", - "url": "/Meshtastic-Android/main/hr-rHR/user/settings-radio-user.html", + "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html", - "relUrl": "/hr-rHR/user/settings-radio-user.html" - },"4518": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4519": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Aprašymas | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/settings-radio-user.html#user-settings", - - "relUrl": "/lt-rLT/user/settings-radio-user.html#user-settings" - },"4520": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | Aprašymas | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Aprašymas | Default | . | Regionas | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Aprašymas | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Aprašymas | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Aprašymas | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Aprašymas | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Aprašymas | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Aprašymas | . | Viešasis raktas | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Privatus raktas | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/lt-rLT/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/lt-rLT/user/settings-radio-user.html#related-topics", - - "relUrl": "/lt-rLT/user/settings-radio-user.html#related-topics" - },"4522": { - "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" - },"4523": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html#settings--radio--user", - - "relUrl": "/en/user/settings-radio-user.html#settings--radio--user" - },"4524": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Description | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html#user-settings", - - "relUrl": "/en/user/settings-radio-user.html#user-settings" - },"4525": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | Description | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Description | Default | . | Region | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Description | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Description | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Description | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Description | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Description | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Description | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ", - "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html#configuration", - - "relUrl": "/en/user/settings-radio-user.html#configuration" - },"4526": { - "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" - },"4527": { - "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" - },"4528": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4529": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Leírás | . | Hosszú név | Your display name (up to 39 characters) | . | Rövid név | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/settings-radio-user.html#user-settings", - - "relUrl": "/hu-rHU/user/settings-radio-user.html#user-settings" - },"4530": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Eszközbeállítások . | Setting | Leírás | Alapértelmezett | . | Szerepkör | Node behavior (Client, Router, etc.) | Kliens | . | Újrasugárzási mód | How the node retransmits messages | Összes | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa beállítások . | Setting | Leírás | Alapértelmezett | . | Régió | Regulatory region for frequency bands | Unset (must configure) | . | Modem-előbeállítás | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Kijelző beállítások . | Setting | Leírás | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Pozíció beállítások . | Setting | Leírás | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Intelligens pozíció | Enable movement-based broadcasting | . | Rögzített pozíció | Use a manually set position | . Energia-beállítások . | Setting | Leírás | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Hálózati beállítások . | Setting | Leírás | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth beállítások . | Setting | Leírás | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Rögzített PIN | PIN code for pairing (default: 123456) | . Biztonsági beállítások . | Setting | Leírás | . | Nyilvános kulcs | Your node’s public key (read-only) | . | Admin kulcs | Key for remote administration | . | Privát kulcs | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Felügyelt mód | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/hu-rHU/user/settings-radio-user.html#configuration" - },"4531": { - "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" - },"4532": { - "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" - },"4533": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4534": { - "doc": "Settings — Radio & User", - "title": "Потребителски настройки", - "content": "User Profile . | Настройка | Описание | . | Дълго име | Your display name (up to 39 characters) | . | Кратко име | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "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#потребителски-настройки" - },"4535": { - "doc": "Settings — Radio & User", - "title": "Конфигурация", - "content": "Конфигуриране на устройството . | Настройка | Описание | По подразбиране | . | Роля | Node behavior (Client, Router, etc.) | Клиент | . | Режим на препредаване | How the node retransmits messages | Всички | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Конфигуриране на LoRa . | Настройка | Описание | По подразбиране | . | Регион | Regulatory region for frequency bands | Unset (must configure) | . | Предварително настроен модем | Speed/range tradeoff | LongFast | . | Лимит на отскоци | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Отместване на честотата | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Конфигуриране на дисплея . | Настройка | Описание | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | Тип OLED | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Конфигуриране на позицията . | Настройка | Описание | . | GPS Enabled | Enable/disable GPS | . | Интервал на актуализиране на GPS | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Интелигентна позиция | Enable movement-based broadcasting | . | Фиксирана позиция | Use a manually set position | . Конфигуриране на захранването . | Настройка | Описание | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Конфигуриране на мрежата . | Настройка | Описание | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Парола за мрежата | . | NTP сървър | Time synchronization server | . | Syslog Server | Remote logging server | . Конфигуриране на Bluetooth . | Настройка | Описание | . | Bluetooth Enabled | Enable/disable BLE radio | . | Режим на сдвояване | Fixed PIN, Random PIN, or No PIN | . | Фиксиран ПИН | PIN code for pairing (default: 123456) | . Конфигуриране на сигурността . | Настройка | Описание | . | Публичен ключ | Your node’s public key (read-only) | . | Администраторски ключ | Key for remote administration | . | Частен ключ | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Управляем режим | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Екранна снимка | . | Dropdown | | . | Toggle | | . | Slider | | . ", - "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#конфигурация" - },"4536": { - "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" - },"4537": { - "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" - },"4538": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4539": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Opis | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/settings-radio-user.html#user-settings", - - "relUrl": "/sl-rSI/user/settings-radio-user.html#user-settings" - },"4540": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | Opis | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Opis | Default | . | Regija | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Opis | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Opis | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Opis | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Opis | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Opis | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Opis | . | Javni ključ | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Zasebni ključ | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/sl-rSI/user/settings-radio-user.html#configuration" - },"4541": { - "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" - },"4542": { - "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" - },"4543": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4544": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Descrição | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/settings-radio-user.html#user-settings", - - "relUrl": "/pt-rPT/user/settings-radio-user.html#user-settings" - },"4545": { - "doc": "Settings — Radio & User", - "title": "Configuração", - "content": "Configuração do Dispositivo . | Setting | Descrição | Predefinição | . | Papel | Node behavior (Client, Router, etc.) | Cliente | . | Rebroadcast Mode | How the node retransmits messages | Tudo | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Configuração de LoRa . | Setting | Descrição | Predefinição | . | Região | Regulatory region for frequency bands | Unset (must configure) | . | Predefinição de modem | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuração do Ecrã . | Setting | Descrição | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Configuração da posição . | Setting | Descrição | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Posição Inteligente | Enable movement-based broadcasting | . | Posição fixa | Use a manually set position | . Configuração de Energia . | Setting | Descrição | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Configuração de Rede . | Setting | Descrição | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Configuração de Bluetooth . | Setting | Descrição | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | PIN fixo | PIN code for pairing (default: 123456) | . Configuração de Segurança . | Setting | Descrição | . | Chave pública | Your node’s public key (read-only) | . | Chave do Administrador | Key for remote administration | . | Chave privada | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Modo Administrado | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configura%C3%A7%C3%A3o", - - "relUrl": "/pt-rPT/user/settings-radio-user.html#configuração" - },"4546": { - "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" - },"4547": { - "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" - },"4548": { + "relUrl": "/ca-rES/user/settings-radio-user.html" + },"4455": { "doc": "Settings — Radio & User", "title": "Settings — Radio & User", "content": "Configure your radio hardware and user identity parameters. ", "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" - },"4549": { + },"4456": { "doc": "Settings — Radio & User", "title": "User Settings", "content": "User Profile . | Setting | Апісанне | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", "url": "/Meshtastic-Android/main/be-rBY/user/settings-radio-user.html#user-settings", "relUrl": "/be-rBY/user/settings-radio-user.html#user-settings" - },"4550": { + },"4457": { "doc": "Settings — Radio & User", "title": "Конфигурация", "content": "Device Config . | Setting | Апісанне | Default | . | Role | Node behavior (Client, Router, etc.) | CLIENT | . | Rebroadcast Mode | How the node retransmits messages | Усе | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Апісанне | Default | . | Рэгіён | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Апісанне | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Апісанне | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Апісанне | . |   | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Апісанне | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Апісанне | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Апісанне | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Прыватны ключ | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#%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#конфигурация" - },"4551": { + },"4458": { "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" - },"4552": { + },"4459": { "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" - },"4553": { + },"4460": { "doc": "Settings — Radio & User", "title": "Settings — Radio & User", "content": "Configure your radio hardware and user identity parameters. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/settings-radio-user.html#settings--radio--user", + "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html#settings--radio--user", - "relUrl": "/pt-rBR/user/settings-radio-user.html#settings--radio--user" - },"4554": { + "relUrl": "/uk-rUA/user/settings-radio-user.html#settings--radio--user" + },"4461": { "doc": "Settings — Radio & User", "title": "User Settings", - "content": "User Profile . | Setting | Descrição | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/settings-radio-user.html#user-settings", + "content": "User Profile . | Setting | Опис | . | Довга назва | Your display name (up to 39 characters) | . | Коротка назва | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html#user-settings", - "relUrl": "/pt-rBR/user/settings-radio-user.html#user-settings" - },"4555": { + "relUrl": "/uk-rUA/user/settings-radio-user.html#user-settings" + },"4462": { "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Configuração do Dispositivo . | Setting | Descrição | Padrão | . | Função | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Configuração do LoRa . | Setting | Descrição | Padrão | . | Região | Regulatory region for frequency bands | Unset (must configure) | . | Predefinição do Modem | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuração da Tela . | Setting | Descrição | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Configuração da Posição . | Setting | Descrição | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Configuração de Energia . | Setting | Descrição | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Configuração de Rede . | Setting | Descrição | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Configuração do Bluetooth . | Setting | Descrição | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | PIN fixo | PIN code for pairing (default: 123456) | . Configurações de Segurança . | Setting | Descrição | . | Chave Publica | Your node’s public key (read-only) | . | Chave do Administrador | Key for remote administration | . | Chave Privada | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Modo Administrado | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + "title": "Налаштування", + "content": "Налаштування пристрою . | Setting | Опис | За замовчуванням | . | Роль | Node behavior (Client, Router, etc.) | Клієнт | . | Режим ретрансляції | How the node retransmits messages | Усі | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Налаштування LoRa . | Setting | Опис | За замовчуванням | . | Регіон | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Налаштування дисплею . | Setting | Опис | . | Screen Timeout | Time before display sleeps | . | Одиниці виміру | Metric or Imperial | . | Тип OLED | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Опис | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Інтелектуальне передавання позиції | Enable movement-based broadcasting | . | Фіксована позиція | Use a manually set position | . Налаштування живлення . | Setting | Опис | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Налаштування мережі . | Setting | Опис | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP-сервер | Time synchronization server | . | Syslog Server | Remote logging server | . Налаштування Bluetooth . | Setting | Опис | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Фіксований PIN | PIN code for pairing (default: 123456) | . Налаштування безпеки . | Setting | Опис | . | Відкритий ключ | Your node’s public key (read-only) | . | Ключ адміністратора | Key for remote administration | . | Приватний ключ | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Керований режим | Restrict non-admin channel changes | . | Резервні ключі | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#%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": "/pt-rBR/user/settings-radio-user.html#configuration" - },"4556": { + "relUrl": "/uk-rUA/user/settings-radio-user.html#налаштування" + },"4463": { "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", + "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html#related-topics", - "relUrl": "/pt-rBR/user/settings-radio-user.html#related-topics" - },"4557": { + "relUrl": "/uk-rUA/user/settings-radio-user.html#related-topics" + },"4464": { "doc": "Settings — Radio & User", "title": "Settings — Radio & User", "content": " ", - "url": "/Meshtastic-Android/main/pt-rBR/user/settings-radio-user.html", + "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html", - "relUrl": "/pt-rBR/user/settings-radio-user.html" - },"4558": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4559": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Περιγραφή | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/el-rGR/user/settings-radio-user.html#user-settings", - - "relUrl": "/el-rGR/user/settings-radio-user.html#user-settings" - },"4560": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | Περιγραφή | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Περιγραφή | Default | . | Περιφέρεια | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Περιγραφή | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Περιγραφή | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Περιγραφή | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Περιγραφή | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Ρυθμίσεις Bluetooth . | Setting | Περιγραφή | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Περιγραφή | . | Δημόσιο Κλειδί | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Ιδιωτικό Κλειδί | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/el-rGR/user/settings-radio-user.html#configuration" - },"4561": { - "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" - },"4562": { - "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" - },"4563": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4564": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Descripción | . | Nombre largo | Your display name (up to 39 characters) | . | Nombre Corto | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/es-rES/user/settings-radio-user.html#user-settings", - - "relUrl": "/es-rES/user/settings-radio-user.html#user-settings" - },"4565": { - "doc": "Settings — Radio & User", - "title": "Configuración", - "content": "Configuración del dispositivo . | Setting | Descripción | Por defecto | . | Rol | Node behavior (Client, Router, etc.) | Cliente | . | Modo de retransmisión | How the node retransmits messages | Todos | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Configuración LoRa . | Setting | Descripción | Por defecto | . | Región | Regulatory region for frequency bands | Unset (must configure) | . | Modem predefinido | Speed/range tradeoff | LongFast | . | Límite de Saltos | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Desplazamiento de frecuencia | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuración de pantalla . | Setting | Descripción | . | Tiempo de espera de la pantalla | Time before display sleeps | . | Unidades de medidas | Metric or Imperial | . | Tipo de OLED | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Configuración de la posición . | Setting | Descripción | . | GPS Enabled | Enable/disable GPS | . | Intervalo de actualización GPS | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Ubicación inteligente | Enable movement-based broadcasting | . | Posición fija | Use a manually set position | . Configuración de elecenergía . | Setting | Descripción | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Configuración de la red . | Setting | Descripción | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Contraseña de red | . | Servidor NTP | Time synchronization server | . | Syslog Server | Remote logging server | . Configuración Bluetooth . | Setting | Descripción | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Pin fijo | PIN code for pairing (default: 123456) | . Configuración de la seguridad . | Setting | Descripción | . | Clave Pública | Your node’s public key (read-only) | . | Contraseña de administrador | Key for remote administration | . | Clave privada | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Modo “ya terminado de configurar” | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuraci%C3%B3n", - - "relUrl": "/es-rES/user/settings-radio-user.html#configuración" - },"4566": { - "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" - },"4567": { - "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" - },"4568": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4569": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Açıklaması | . | Uzun Ad | Your display name (up to 39 characters) | . | Kısa Ad | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/settings-radio-user.html#user-settings", - - "relUrl": "/tr-rTR/user/settings-radio-user.html#user-settings" - },"4570": { - "doc": "Settings — Radio & User", - "title": "Yapılandırma", - "content": "Cihaz Ayarı . | Setting | Açıklaması | Varsayılan | . | Rol | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | Hepsi | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Ayarı . | Setting | Açıklaması | Varsayılan | . | Bölge | Regulatory region for frequency bands | Unset (must configure) | . | Modem Ön Ayarı | Speed/range tradeoff | LongFast | . | Hop Limiti | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Akran Ayarı . | Setting | Açıklaması | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Tipi | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Konum Ayarı . | Setting | Açıklaması | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Güç Ayarı . | Setting | Açıklaması | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Ağ Ayarı . | Setting | Açıklaması | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Ağ şifresi | . | NTP Sunucusu | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Ayarı . | Setting | Açıklaması | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Sabit PIN | PIN code for pairing (default: 123456) | . Güvenlik Ayarı . | Setting | Açıklaması | . | Genel Anahtar | Your node’s public key (read-only) | . | Yönetici Anahtarı | Key for remote administration | . | Özel Anahtar | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Yönetilen Mod | Restrict non-admin channel changes | . | Anahtarları Yedekle | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#yap%C4%B1land%C4%B1rma", - - "relUrl": "/tr-rTR/user/settings-radio-user.html#yapılandırma" - },"4571": { - "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" - },"4572": { - "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" - },"4573": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4574": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Beskrivelse | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/no-rNO/user/settings-radio-user.html#user-settings", - - "relUrl": "/no-rNO/user/settings-radio-user.html#user-settings" - },"4575": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | Beskrivelse | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Beskrivelse | Default | . | Region | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Beskrivelse | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Beskrivelse | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Beskrivelse | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Beskrivelse | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Beskrivelse | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Beskrivelse | . | Offentlig nøkkel | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Privat nøkkel | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/no-rNO/user/settings-radio-user.html#configuration" - },"4576": { - "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" - },"4577": { - "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" - },"4578": { - "doc": "Настройки - Радио и пользователь", - "title": "Настройки - Радио и пользователь", - "content": "Настройте радиоустройство и параметры идентификации пользователя. ", - "url": "/Meshtastic-Android/main/ru-rRU/user/settings-radio-user.html", - - "relUrl": "/ru-rRU/user/settings-radio-user.html" - },"4579": { - "doc": "Настройки - Радио и пользователь", - "title": "Настройки пользователя", - "content": "Профиль пользователя . | Настройка | Описание | . | Полное имя | Ваше отображаемое имя (до 39 символов) | . | Короткое имя | 4-символьное сокращённое имя | . | Лицензированный оператор | Включите, если у вас есть лицензия радиолюбителя (позволяет использовать более высокую мощность) | . Применение изменений . После изменения настроек нажмите Сохранить чтобы записать конфигурацию в ваше радиоустройство. Устройство может перезагрузиться для применения изменений. ", - "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#настройки-пользователя" - },"4580": { - "doc": "Настройки - Радио и пользователь", - "title": "Настройки", - "content": "Настройки устройства . | Настройка | Описание | По умолчанию | . | Роль | Поведение ноды (Client, Router и т.д.) | Client | . | Режим ретрансляции | Как нода повторно передает сообщения | Всё | . | Передача информации ноды | Интервал для передачи информации ноды | 10800 | . | Двойное нажатие кнопки | Действие при двойном нажатии кнопки | Включено | . Настройка LoRa . | Настройка | Описание | По умолчанию | . | Регион / Страна | Область регулирования для диапазонов частот | Не установлено (необходимо настроить) | . | Режим работы модема | Компромисс между скоростью и дальностью | LongFast | . | Лимит хопов | Максимальное количество ретрансляций | 3 | . | Мощность передачи | Мощность передачи (дБм); 0 = максимально разрешённая для региона | 0 (максимум региона) | . | Частотное смещение | Точная настройка частоты (МГц) | 0 | . | Полоса пропускания канала | Настройка пропускной способности | По умолчанию для предустановки | . ⚠️ Важно: Вы обязаны установить свой регион перед отправкой. Работа без правильного региона может нарушать местные правила радиопользования. Смотрите руководство по настройке региона на сайте meshtastic.org для получения подробной информации. Предустановки модема . 💡 Совет: Значения порога SNR специально отрицательные. LoRa может декодировать сигналы ниже уровня шума, поэтому более отрицательный предел означает, что пресет допускает более слабый, шумный сигнал (больший радиус действия). Смотрите Как работает измеритель сигнала для полного объяснения. | Предустановка | Диапазон | Скорость | Предел SNR | Лучше всего для | . | Short Turbo | ~1 км | 21.9 кб/с | −7.5 дБ | Плотная городская застройка с прямой видимостью; приложения, требующие высокой передачи данных | . | Short Fast | ~3 км | 10.9 кб/с | −7.5 дБ | Городские районы; здания в пределах нескольких кварталов | . | Short Slow | ~5 км | 5.5 кб/с | -10 дБ | Пригородная зона с коротким диапазоном; умеренная плотность застройки | . | Medium Fast | ~5 км | 5.5 кб/с | −12.5 дБ | Пригородные районы; умеренная плотность застройки | . | Medium Slow | ~8 км | 1.1 кб/с | -15 дБ | Пригородный/сельский; умеренный диапазон со сниженной скоростью | . | Long Turbo | ~10 км | 4.4 кб/с | −12.5 дБ | Диапазон, похожий на Long Fast, но с полосой пропускания 500 кГц; более высокая пропускная способность | . | Long Fast | ~10 км | 1.1 кб/с | −17.5 дБ | Общее использование (по умолчанию) — сбалансированный диапазон и скорость | . | Long Moderate | ~20 км | 0.34 кб/с | −17.5 дБ | Сельская местность с некоторым рельефом; случайное использование | . | Lite Fast | ~5 км | 5.5 кб/с | −12.5 дБ | Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Medium Fast | . | Lite Slow | ~10 км | 1.1 кб/с | -15 дБ | Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Long Fast | . | Narrow Fast | ~5 км | 2.7 кб/с | -10 дБ | Диапазон RU 868 МГц (полоса пропускания 62,5 кГц); предотвращает помехи с другими устройствами | . | Narrow Slow | ~10 км | 1.1 кб/с | −12.5 дБ | Диапазон RU 868 МГц (ширина полосы 62,5 кГц); аналогично Long Fast | . | Long Slow | ~30 км | 0.18 кб/с | −20 дБ | ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки | . | Very Long Slow | ~40+ км | 0.09 кб/с | −20 дБ | ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки | . i Примечание: В этой таблице используются общие короткие имена. В выпадающем меню пресетов приложения они читаются как Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast и так далее. Выбор предустановки модема . Предустановка модема управляет основным компромиссом между дальностью и скоростью передачи данных: . | Медленные предустановки используют большее распространение, что позволяет декодировать сигналы при более слабых уровнях сигнала (ниже порога 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 — это настройка по умолчанию в сообществе и она обеспечит совместимость с другими в вашем регионе. | . ⚠️ Важно: Все ноды в одном канале должны использовать один и тот же пресет модема. Ноды с несовпадающими предустановками не смогут обмениваться данными, даже если они используют одну частоту и ключ шифрования. 💡 Совет: Указанные выше оценки дальности предполагают ровную местность и небольшие антенны. Преимущество высоты (вершина холма, крыша) значительно увеличивает эффективную дальность. Хорошо размещённый маршрутизатор с Long Fast часто может превзойти наземную ноду с Long Slow. Параметры дисплея . | Настройка | Описание | . | Время ожидания | Время до перехода в спящий режим | . | Единицы измерения | Метрическая или имперская | . | Тип OLED-дисплея | Авто, SSD1306, SH1106, SH1107 | . | Ориентация компаса | Смещение вращения для отображения компаса (0°, 90°, 180°, 270°) | . | Север компаса | ⚠️ Устарело — заменено на ориентацию компаса; по-прежнему видно в старой прошивке | . Настройки местоположения . | Настройка | Описание | . | GPS включен | Включение/отключение GPS | . | Интервал обновления GPS | Как часто получать GPS-фиксацию | . | Вещание позиции | Как часто делиться местоположением | . | Умная позиция | Включить трансляцию при движении | . | Фиксированная позиция | Использовать вручную заданное положение | . Настройка питания . | Настройка | Описание | . | Энергосбережение | Включить спящий режим с низким энергопотреблением | . | Завершение работы через | Таймер автоотключения при простое | . | Множитель ADC | Коэффициент калибровки напряжения батареи | . | Ожидание Bluetooth | Время ожидания подключения BLE при загрузке | . | Тайм-аут Mesh SDS | Тайм-аут сверхглубокого сна | . Настройка сети . | Настройка | Описание | . | WiFi включен | Включить радиомодуль WiFi (устройства ESP32) | . | WiFi SSID | Имя сети для подключения | . | WiFi PSK | Пароль сети | . | NTP-сервер | Сервер синхронизации времени | . | Syslog-сервер | Удалённый сервер логирования | . Настройка Bluetooth . | Настройка | Описание | . | Bluetooth включен | Включение/отключение BLE радиостанции | . | Режим сопряжения | Фиксированный PIN, случайный PIN или без PIN | . | Фиксированный PIN-код | PIN-код для сопряжения (по умолчанию: 123456) | . Настройки безопасности . | Настройка | Описание | . | Публичный ключ | Публичный ключ твоей ноды (только для чтения) | . | Ключ администратора | Ключ для удалённого администрирования | . | Приватный ключ | Приватный ключ твоей ноды (обращайся с ним осторожно) | . | Канал администратора включен | ⚠️ Удалено — теперь настраивается автоматически при установке ключа администратора | . | Журнал отладки | Выводить живой отладочный лог через последовательный порт/Bluetooth | . | Последовательная включена | Включить доступ к последовательной консоли (перемещено из настроек устройства) | . | Управляемый режим | Ограничить изменения канала для неадминистраторов | . | Резервное копирование | Сохранить зашифрованную резервную копию ключей ноды на этом устройстве (только для Android) | . | Восстановить ключи | Запишисать сохранённые ключи обратно на ноду (доступно, как только есть резервная копия) | . | Удалить резервную копию ключа | Удалить сохранённую резервную копию ключа с этого устройства | . | Уровень защиты | Подлинность пакета — как обрабатываются неподписанные или пересылаемые пакеты: Строго, Сбалансировано или Совместимо (требуется поддержка прошивкой; Строго требует подтверждения) | . Настройки используют стандартные элементы управления предпочтениями — выпадающие списки, переключатели и ползунки: . | Управление | Снимок экрана | . | Выпадающий список | | . | Переключатель | | . | Ползунок | | . ", - "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#настройки" - },"4581": { - "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#связанные-темы" - },"4582": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4583": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Beschrijving | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/settings-radio-user.html#user-settings", - - "relUrl": "/nl-rNL/user/settings-radio-user.html#user-settings" - },"4584": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Apparaat Configuratie . | Setting | Beschrijving | Standaard | . | Functie | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | Alles | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Configuratie . | Setting | Beschrijving | Standaard | . | Regio | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Weergave Configuratie . | Setting | Beschrijving | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Positie Configuratie . | Setting | Beschrijving | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Energie configuratie . | Setting | Beschrijving | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Netwerkconfiguratie . | Setting | Beschrijving | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Configuratie . | Setting | Beschrijving | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Vaste PIN | PIN code for pairing (default: 123456) | . Beveiligings Configuratie . | Setting | Beschrijving | . | Publieke sleutel | Your node’s public key (read-only) | . | Admin Sleutel | Key for remote administration | . | Privésleutel | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Beheerde modus | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/nl-rNL/user/settings-radio-user.html#configuration" - },"4585": { - "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" - },"4586": { - "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" - },"4587": { - "doc": "Seaded — raadio ja kasutaja", - "title": "Seaded — raadio ja kasutaja", - "content": "Configure your radio hardware and user identity parameters. ", - "url": "/Meshtastic-Android/main/et-rEE/user/settings-radio-user.html", - - "relUrl": "/et-rEE/user/settings-radio-user.html" - },"4588": { - "doc": "Seaded — raadio ja kasutaja", - "title": "Kasutaja seaded", - "content": "User Profile . | Setting | Kirjeldus | . | Täis nimi | Your display name (up to 39 characters) | . | Lühi nimi | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . Pärast sätete muutmist puuduta nuppu Salvesta, et konfiguratsioon raadiosse salvestada. Muudatuste rakendamiseks võib seade taaskäivituda. ", - "url": "/Meshtastic-Android/main/et-rEE/user/settings-radio-user.html#kasutaja-seaded", - - "relUrl": "/et-rEE/user/settings-radio-user.html#kasutaja-seaded" - },"4589": { - "doc": "Seaded — raadio ja kasutaja", - "title": "Sätted", - "content": "Seadme sätted . | Setting | Kirjeldus | Vaikimisi | . | Roll | Node behavior (Client, Router, etc.) | Klient | . | Kordusülekannete režiim | How the node retransmits messages | Kõik | . | Sõlme(de) teabe levitamine | Sõlme teabe levitamise intervall | 10800 | . | Topeltpuudutusnupp | Toiming topeltpuudutuse nupu korral | Keelatud | . LoRa sätted . | Setting | Kirjeldus | Vaikimisi | . | Regioon | Sagedusribade reguleerimispiirkond | Määramata (tuleb seadistada) | . | Modemi vaikesäte | Speed/range tradeoff | LongFast | . | Hüppete limiit | Maks uuesti saadetud hüpet | 3 | . | TX võimsus | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Sagedusnihe | Sageduse peenhäälestamine (MHz) | 0 | . | Kanali ribalaius | Bandwidth setting | Default for preset | . ⚠️ Tähtis: Enne edastamist peate oma piirkonna määrama. Operating without the correct region may violate local radio regulations. Lisateabe saamiseks vaadake regiooni seadistamise juhendit aadressil meshtastic.org. Modem Presets . 💡 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 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 | Linnaosad; hooned mõne kvartali raadiuses | . | Short Slow | ~5 km | 5.5 kbps | −10 dB | Äärelinna lühimaa; mõõdukas hoonestustihedus | . | Medium Fast | ~5 km | 5.5 kbps | −12,5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1,1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4,4 kbps | −12,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 | 5,5 kbps | −12,5 dB | EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Medium Fast | . | Lite Slow | ~10 km | 1,1 kbps | −15 dB | EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Long Fast | . | Narrow Fast | ~5 km | 2,7 kbps | −10 dB | EL 868 MHz sagedusala (62,5 kHz sagedusriba); väldib häireid teiste seadmetega | . | Narrow Slow | ~10 km | 1,1 kbps | −12,5 dB | EL 868 MHz sagedusala (62,5 kHz ribalaius); võrreldav Long Fast | . | 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. Rakenduse eelseadistatud rippmenüüs on need järgmised: Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, jne. 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. | 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. | 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. | . ⚠️ Tähtis: Kõik samal kanalil olevad sõlmed peavad kasutama sama modemi eelseadistust. Erinevate eelseadetega sõlmed ei saa suhelda isegi siis, kui neil on sama sagedus ja krüpteerimisvõti. 💡 Vihje: ulatuse hinnangud eeldavad tasast maastikku ja mõõdukaid antenne. 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. Ekraani sätted . | Setting | Kirjeldus | . | Screen Timeout | Time before display sleeps | . | Display Units | Meetriline või Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Vananenud — asendatud kompassi suunaga; nähtav endiselt vanemas püsivaras | . Asukoha sätted . | Setting | Kirjeldus | . | GPS lubatud | GPS lubamine/keelamine | . | GPS värskendamise intervall | Kui tihti GPS asukohta leida | . | Asukoha(de) levitamine | How often to share position | . | Nutikas asukoht | Liikumispõhise levitamise lubamine | . | Määratud asukoht | Use a manually set position | . Toite sätted . | Setting | Kirjeldus | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Aku pinge kalibreerimistegur | . | Oota sinihammast(id) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Ülisügava une ajalõpp | . Võrgu sätted . | Setting | Kirjeldus | . | WiFi lubatud | Luba WiFi (ESP32 seade) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP server | Time synchronization server | . | Syslog Server | Kauglogimise server | . Sinihamba sätted . | Setting | Kirjeldus | . | Sinihammas lubatud | Enable/disable BLE radio | . | Sidumisreziim | Määratud PIN kood, juhuslik PIN kood või PIN koodi pole | . | Fikseeritud PIN | Sidumise PIN (vaikimisi: 123456) | . Turva sätted . | Setting | Kirjeldus | . | Avalik võti | Sinu sõlme avalik võti (kirjutuskaitstud) | . | Administraatori võti | Kaughalduse võti | . | Salajane võti | Sinu sõlme privaatvõti (käsitsege turvaliselt) | . | Admin kanal lubatud | ⚠️ Eemaldatud — nüüd seadistatakse automaatselt, kui administraatori võti on määratud | . | Arendaja logi | Edasta reaalajas arendajalogi jadapordi/sinihamba ​​kaudu | . | Jadaühendus lubatud | Luba jadapordi konsoolile juurdepääs (teisaldatud seadme konfist) | . | Hallatud režiim | Piira mitte-administraatori kanali muudatusi | . | Taastevõtmed | Salvesta sõlme võtmete krüpteeritud varukoopia sellesse seadmesse (ainult Android) | . | Taasta võtmed | Kirjuta varundatud võtmed tagasi sõlme (saadaval siis, kui varukoopia on olemas) | . | Kustuta taastevõtmed | Eemalda salvestatud võtme varukoopia sellest seadmest | . | Protection Level | Pakettide autentsus – kuidas käsitletakse allkirjastamata või vahendatud pakette: range, tasakaalustatud või ühilduv (nõuab toetavat püsivara; range režiimi puhul küsitakse kinnitust) | . 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#s%C3%A4tted", - - "relUrl": "/et-rEE/user/settings-radio-user.html#sätted" - },"4590": { - "doc": "Seaded — raadio ja kasutaja", - "title": "Related Topics", - "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#related-topics", - - "relUrl": "/et-rEE/user/settings-radio-user.html#related-topics" - },"4591": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4592": { - "doc": "Settings — Radio & User", - "title": "Impostazioni Utente", - "content": "User Profile . | Impostazione | Descrizione | . | Nome Lungo | Your display name (up to 39 characters) | . | Nome Breve | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/it-rIT/user/settings-radio-user.html#impostazioni-utente", - - "relUrl": "/it-rIT/user/settings-radio-user.html#impostazioni-utente" - },"4593": { - "doc": "Settings — Radio & User", - "title": "Configurazione", - "content": "Configurazione Dispositivo . | Impostazione | Descrizione | Predefinito | . | Ruolo | Node behavior (Client, Router, etc.) | Client | . | Modalità Ritrasmissione | How the node retransmits messages | Tutti | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Configurazione LoRa . | Impostazione | Descrizione | Predefinito | . | Regione | Regulatory region for frequency bands | Unset (must configure) | . | Configurazione Modem | Speed/range tradeoff | LongFast | . | Limite di hop | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Offset Di Frequenza | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0,18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configurazione Schermo . | Impostazione | Descrizione | . | Timeout Schermo | Time before display sleeps | . | Mostra Unità | Metric or Imperial | . | Tipo OLED | Auto, SSD1306, SH1106, SH1107 | . | Orientamento bussola | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Configurazione Posizione . | Impostazione | Descrizione | . | GPS Enabled | Enable/disable GPS | . | Intervallo di aggiornamento GPS | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Posizione Smart | Enable movement-based broadcasting | . | Posizione Fissa | Use a manually set position | . Configurazione Alimentazione . | Impostazione | Descrizione | . | Risparmio energetico | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Configurazione Della Rete . | Impostazione | Descrizione | . | WiFi abilitato | Enable WiFi radio (ESP32 devices) | . | SSID WiFi | Network name to connect to | . | WiFi PSK | Password di rete | . | Server NTP | Time synchronization server | . | Syslog Server | Remote logging server | . Configurazione Bluetooth . | Impostazione | Descrizione | . | Bluetooth Enabled | Enable/disable BLE radio | . | Modalità di abbinamento | Fixed PIN, Random PIN, or No PIN | . | PIN Fisso | PIN code for pairing (default: 123456) | . Configurazione Sicurezza . | Impostazione | Descrizione | . | Chiave Pubblica | Your node’s public key (read-only) | . | Chiave Amministratore | Key for remote administration | . | Chiave Privata | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Log di debug | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Modalità Gestita | Restrict non-admin channel changes | . | Backup chiavi | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configurazione", - - "relUrl": "/it-rIT/user/settings-radio-user.html#configurazione" - },"4594": { - "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" - },"4595": { - "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" - },"4596": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4597": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | الوصف | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/settings-radio-user.html#user-settings", - - "relUrl": "/ar-rSA/user/settings-radio-user.html#user-settings" - },"4598": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Device Config . | Setting | الوصف | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | الوصف | Default | . | الجهة | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | الوصف | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | الوصف | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | الوصف | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | الوصف | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | الوصف | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | الوصف | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/ar-rSA/user/settings-radio-user.html#configuration" - },"4599": { - "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" - },"4600": { - "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" - },"4601": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4602": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Popis | . | Dlhé Meno | Your display name (up to 39 characters) | . | Krátke Meno | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/settings-radio-user.html#user-settings", - - "relUrl": "/sk-rSK/user/settings-radio-user.html#user-settings" - },"4603": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Konfigurácia Zariadenia . | Setting | Popis | Predvolené | . | Rola | Node behavior (Client, Router, etc.) | Klient | . | Rebroadcast Mode | How the node retransmits messages | Všetky | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Konfigurácia LoRa . | Setting | Popis | Predvolené | . | Región | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Konfigurácia Displeju . | Setting | Popis | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Popis | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Inteligentná poloha | Enable movement-based broadcasting | . | Fixná Pozícia | Use a manually set position | . Power Config . | Setting | Popis | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Konfigurácia siete . | Setting | Popis | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Konfigurácia Bluetooth . | Setting | Popis | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Pevný PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Popis | . | Verejný kľúč | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Súkromný kľúč | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/sk-rSK/user/settings-radio-user.html#configuration" - },"4604": { - "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" - },"4605": { - "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" - },"4606": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4607": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Setting | Opis | . | Długa nazwa | Your display name (up to 39 characters) | . | Krótka nazwa | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/settings-radio-user.html#user-settings", - - "relUrl": "/pl-rPL/user/settings-radio-user.html#user-settings" - },"4608": { - "doc": "Settings — Radio & User", - "title": "Konfiguracja", - "content": "Konfiguracja urządzenia . | Setting | Opis | Domyślny | . | Rola | Node behavior (Client, Router, etc.) | Klient | . | Tryb retransmisji | How the node retransmits messages | Wszystkie | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Wyłączony | . Konfiguracja LoRa . | Setting | Opis | Domyślny | . | Region | Regulatory region for frequency bands | Unset (must configure) | . | Ustawienie modemu | Speed/range tradeoff | LongFast | . | Limit przeskoków | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Przesunięcie częstotliwości | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Konfiguracja wyświetlacza . | Setting | Opis | . | Wygaszenie ekranu | Time before display sleeps | . | Jednostki wyświetlania | Metric or Imperial | . | Typ ekranu OLED | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Konfiguracja pozycjonowania . | Setting | Opis | . | GPS Enabled | Enable/disable GPS | . | Interwał aktualizacji pozycji GPS | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Inteligentne Pozycjonowanie | Enable movement-based broadcasting | . | Położenie stałe | Use a manually set position | . Konfiguracja zarządzania energią . | Setting | Opis | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Konfiguracja sieci . | Setting | Opis | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Hasło do sieci | . | Serwer NTP | Time synchronization server | . | Syslog Server | Remote logging server | . Konfiguracja Bluetooth . | Setting | Opis | . | Bluetooth Enabled | Enable/disable BLE radio | . | Tryb parowania | Fixed PIN, Random PIN, or No PIN | . | Stały PIN | PIN code for pairing (default: 123456) | . Konfiguracja zabezpieczeń . | Setting | Opis | . | Klucz publiczny | Your node’s public key (read-only) | . | Klucz administratora | Key for remote administration | . | Klucz prywatny | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Klucze zapasowe | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#konfiguracja", - - "relUrl": "/pl-rPL/user/settings-radio-user.html#konfiguracja" - },"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/pl-rPL/user/settings-radio-user.html#related-topics", - - "relUrl": "/pl-rPL/user/settings-radio-user.html#related-topics" - },"4610": { - "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" - },"4611": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4612": { - "doc": "Settings — Radio & User", - "title": "使用者設定", - "content": "User Profile . | 設定 | 描述說明 | . | 長名稱 | Your display name (up to 39 characters) | . | 簡短名稱 | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "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#使用者設定" - },"4613": { - "doc": "Settings — Radio & User", - "title": "設定", - "content": "設備設置 . | 設定 | 描述說明 | 默認 | . | 角色 | Node behavior (Client, Router, etc.) | 用戶端 | . | ## Rebroadcast Mode轉發廣播模式 | How the node retransmits messages | 全部 | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa規劃 . | 設定 | 描述說明 | 默認 | . | 地區 | Regulatory region for frequency bands | Unset (must configure) | . | 數據機預設值 (Modem Preset) | Speed/range tradeoff | LongFast | . | 躍點限制 | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | 頻率偏移量 | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | 中等快 | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | 中等慢 | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | 長度中等的 | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 顯示設置 . | 設定 | 描述說明 | . | 螢幕逾時 | Time before display sleeps | . | 顯示單位 | Metric or Imperial | . | OLED類型 | Auto, SSD1306, SH1106, SH1107 | . | 羅盤方位 | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . 位置設定 . | 設定 | 描述說明 | . | GPS Enabled | Enable/disable GPS | . | GPS 更新間隔 | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | 智慧定位 | Enable movement-based broadcasting | . | 固定位置 | Use a manually set position | . 電源設定 . | 設定 | 描述說明 | . | 省電模式 | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . 網路配置 . | 設定 | 描述說明 | . | 啟用 WiFi | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | 網路密碼 | . | NTP 伺服器 | Time synchronization server | . | Syslog Server | Remote logging server | . 藍牙配置 . | 設定 | 描述說明 | . | Bluetooth Enabled | Enable/disable BLE radio | . | 配對模式 | Fixed PIN, Random PIN, or No PIN | . | 固定 PIN | PIN code for pairing (default: 123456) | . 安全性設定 . | 設定 | 描述說明 | . | 公鑰 | Your node’s public key (read-only) | . | 管理金鑰 | Key for remote administration | . | 私鑰 | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | 除錯日誌 | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | 管理模式 | Restrict non-admin channel changes | . | 備份金鑰 | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | 螢幕截圖 | . | Dropdown | | . | Toggle | | . | Slider | | . ", - "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#設定" - },"4614": { - "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" - },"4615": { - "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" - },"4616": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4617": { - "doc": "Settings — Radio & User", - "title": "User Settings", - "content": "User Profile . | Nastavení | Popis | . | Dlouhé jméno | Your display name (up to 39 characters) | . | Krátké jméno | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-radio-user.html#user-settings", - - "relUrl": "/cs-rCZ/user/settings-radio-user.html#user-settings" - },"4618": { - "doc": "Settings — Radio & User", - "title": "Nastavení", - "content": "Nastavení zařízení . | Nastavení | Popis | Výchozí | . | Role | Node behavior (Client, Router, etc.) | Client | . | Režim opětovného vysílání | How the node retransmits messages | Vše | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa nastavení . | Nastavení | Popis | Výchozí | . | Region | Regulatory region for frequency bands | Unset (must configure) | . | Předvolba modemu | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Nastavení zobrazení . | Nastavení | Popis | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Nastavení pozice . | Nastavení | Popis | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Chytrá poloha | Enable movement-based broadcasting | . | Pevná poloha | Use a manually set position | . Nastavení napájení . | Nastavení | Popis | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Nastavení sítě . | Nastavení | Popis | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Nastavení bluetooth . | Nastavení | Popis | . | Bluetooth Enabled | Enable/disable BLE radio | . | Režim párování | Fixed PIN, Random PIN, or No PIN | . | Pevný PIN | PIN code for pairing (default: 123456) | . Nastavení zabezpečení . | Nastavení | Popis | . | Veřejný klíč | Your node’s public key (read-only) | . | Administrátorský klíč | Key for remote administration | . | Soukromý klíč | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Řízený režim | Restrict non-admin channel changes | . | Záloha klíčů | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#nastaven%C3%AD", - - "relUrl": "/cs-rCZ/user/settings-radio-user.html#nastavení" - },"4619": { - "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" - },"4620": { - "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" - },"4621": { - "doc": "Settings — Radio & User", - "title": "Settings — Radio & User", - "content": "Configure your radio hardware and user identity parameters. ", - "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" - },"4622": { - "doc": "Settings — Radio & User", - "title": "Paramètres utilisateur", - "content": "User Profile . | Setting | Description | . | Nom long | Your display name (up to 39 characters) | . | Nom court | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", - "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" - },"4623": { - "doc": "Settings — Radio & User", - "title": "Configuration", - "content": "Configuration de l’appareil . | Setting | Description | Par défaut | . | Rôle | Node behavior (Client, Router, etc.) | Client | . | Mode de réémission | How the node retransmits messages | Tout | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Désactivé | . Configuration LoRa . | Setting | Description | Par défaut | . | Région | Regulatory region for frequency bands | Unset (must configure) | . | Préréglage du modem | Speed/range tradeoff | LongFast | . | Limite de sauts | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Décalage de fréquence | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuration de l’écran . | Setting | Description | . | Délai d’extinction de l’écran | Time before display sleeps | . | Unités affichées | Metric or Imperial | . | Type d’OLED | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Configuration de la position . | Setting | Description | . | GPS Enabled | Enable/disable GPS | . | Intervalle de mise à jour GPS | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Position Intelligente | Enable movement-based broadcasting | . | Position fixe | Use a manually set position | . Configuration de l’alimentation . | Setting | Description | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Configuration du réseau . | Setting | Description | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Mot de passe du réseau | . | Serveur NTP | Time synchronization server | . | Syslog Server | Remote logging server | . Configuration Bluetooth . | Setting | Description | . | Bluetooth Enabled | Enable/disable BLE radio | . | Mode d’appairage | Fixed PIN, Random PIN, or No PIN | . | Code PIN fixe | PIN code for pairing (default: 123456) | . Configuration de sécurité . | Setting | Description | . | Clé publique | Your node’s public key (read-only) | . | Clé Admin | Key for remote administration | . | Clé privée | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Mode géré | Restrict non-admin channel changes | . | Sauvegarder les clés | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - - "relUrl": "/fr-rFR/user/settings-radio-user.html#configuration" - },"4624": { - "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" - },"4625": { - "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" - },"4626": { + "relUrl": "/uk-rUA/user/settings-radio-user.html" + },"4465": { "doc": "Settings — Radio & User", "title": "Settings — Radio & User", "content": "Configure your radio hardware and user identity parameters. ", "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" - },"4627": { + },"4466": { "doc": "Settings — Radio & User", "title": "用户设置", "content": "User Profile . | Setting | 说明 | . | 长名称 | Your display name (up to 39 characters) | . | 短名称 | 4-character abbreviated name | . | 持证操作员 | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", "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#用户设置" - },"4628": { + },"4467": { "doc": "Settings — Radio & User", "title": "Configuration", "content": "设备配置 . | Setting | 说明 | 默认 | . | 角色 | Node behavior (Client, Router, etc.) | 客户端 | . | 转播模式 | How the node retransmits messages | 全部 | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | 禁用 | . LoRa 配置 . | Setting | 说明 | 默认 | . | 区域 | Regulatory region for frequency bands | Unset (must configure) | . | 调制解调器预设 | Speed/range tradeoff | LongFast | . | 跳跃数限制 | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | 频率偏移(MHz | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 屏幕配置 . | Setting | 说明 | . | 屏幕超时时间 | Time before display sleeps | . | 显示单位 | Metric or Imperial | . | OLED 类型 | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . 定位配置 . | Setting | 说明 | . | GPS Enabled | Enable/disable GPS | . | GPS更新间隔 | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | 智能位置 | Enable movement-based broadcasting | . | 固定位置 | Use a manually set position | . 电源配置 . | Setting | 说明 | . | 省电模式 | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . 网络配置 . | Setting | 说明 | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | 网络密码 | . | NTP 服务器地址 | Time synchronization server | . | Syslog Server | Remote logging server | . 蓝牙配置 . | Setting | 说明 | . | Bluetooth Enabled | Enable/disable BLE radio | . | 配对模式 | Fixed PIN, Random PIN, or No PIN | . | 固定PIN码 | PIN code for pairing (default: 123456) | . 安全配置 . | Setting | 说明 | . | 公钥 | Your node’s public key (read-only) | . | 管理员密钥 | Key for remote administration | . | 私钥 | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | 管理模式 | Restrict non-admin channel changes | . | 备份密钥 | Save an encrypted backup of the node’s keys on this device (Android only) | . | 恢复密钥 | Write the backed-up keys back to the node (available once a backup exists) | . | 删除密钥备份 | Remove the stored key backup from this device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", "relUrl": "/zh-rCN/user/settings-radio-user.html#configuration" - },"4629": { + },"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/zh-rCN/user/settings-radio-user.html#related-topics", "relUrl": "/zh-rCN/user/settings-radio-user.html#related-topics" - },"4630": { + },"4469": { "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" - },"4631": { + },"4470": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4471": { + "doc": "Settings — Radio & User", + "title": "Потребителски настройки", + "content": "User Profile . | Настройка | Описание | . | Дълго име | Your display name (up to 39 characters) | . | Кратко име | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "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#потребителски-настройки" + },"4472": { + "doc": "Settings — Radio & User", + "title": "Конфигурация", + "content": "Конфигуриране на устройството . | Настройка | Описание | По подразбиране | . | Роля | Node behavior (Client, Router, etc.) | Клиент | . | Режим на препредаване | How the node retransmits messages | Всички | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Конфигуриране на LoRa . | Настройка | Описание | По подразбиране | . | Регион | Regulatory region for frequency bands | Unset (must configure) | . | Предварително настроен модем | Speed/range tradeoff | LongFast | . | Лимит на отскоци | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Отместване на честотата | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Конфигуриране на дисплея . | Настройка | Описание | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | Тип OLED | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Конфигуриране на позицията . | Настройка | Описание | . | GPS Enabled | Enable/disable GPS | . | Интервал на актуализиране на GPS | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Интелигентна позиция | Enable movement-based broadcasting | . | Фиксирана позиция | Use a manually set position | . Конфигуриране на захранването . | Настройка | Описание | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Конфигуриране на мрежата . | Настройка | Описание | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Парола за мрежата | . | NTP сървър | Time synchronization server | . | Syslog Server | Remote logging server | . Конфигуриране на Bluetooth . | Настройка | Описание | . | Bluetooth Enabled | Enable/disable BLE radio | . | Режим на сдвояване | Fixed PIN, Random PIN, or No PIN | . | Фиксиран ПИН | PIN code for pairing (default: 123456) | . Конфигуриране на сигурността . | Настройка | Описание | . | Публичен ключ | Your node’s public key (read-only) | . | Администраторски ключ | Key for remote administration | . | Частен ключ | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Управляем режим | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Екранна снимка | . | Dropdown | | . | Toggle | | . | Slider | | . ", + "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#конфигурация" + },"4473": { + "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" + },"4474": { + "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" + },"4475": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4476": { + "doc": "Settings — Radio & User", + "title": "使用者設定", + "content": "User Profile . | 設定 | 描述說明 | . | 長名稱 | Your display name (up to 39 characters) | . | 簡短名稱 | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "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#使用者設定" + },"4477": { + "doc": "Settings — Radio & User", + "title": "設定", + "content": "設備設置 . | 設定 | 描述說明 | 默認 | . | 角色 | Node behavior (Client, Router, etc.) | 用戶端 | . | ## Rebroadcast Mode轉發廣播模式 | How the node retransmits messages | 全部 | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa規劃 . | 設定 | 描述說明 | 默認 | . | 地區 | Regulatory region for frequency bands | Unset (must configure) | . | 數據機預設值 (Modem Preset) | Speed/range tradeoff | LongFast | . | 躍點限制 | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | 頻率偏移量 | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | 中等快 | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | 中等慢 | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | 長度中等的 | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 顯示設置 . | 設定 | 描述說明 | . | 螢幕逾時 | Time before display sleeps | . | 顯示單位 | Metric or Imperial | . | OLED類型 | Auto, SSD1306, SH1106, SH1107 | . | 羅盤方位 | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . 位置設定 . | 設定 | 描述說明 | . | GPS Enabled | Enable/disable GPS | . | GPS 更新間隔 | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | 智慧定位 | Enable movement-based broadcasting | . | 固定位置 | Use a manually set position | . 電源設定 . | 設定 | 描述說明 | . | 省電模式 | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . 網路配置 . | 設定 | 描述說明 | . | 啟用 WiFi | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | 網路密碼 | . | NTP 伺服器 | Time synchronization server | . | Syslog Server | Remote logging server | . 藍牙配置 . | 設定 | 描述說明 | . | Bluetooth Enabled | Enable/disable BLE radio | . | 配對模式 | Fixed PIN, Random PIN, or No PIN | . | 固定 PIN | PIN code for pairing (default: 123456) | . 安全性設定 . | 設定 | 描述說明 | . | 公鑰 | Your node’s public key (read-only) | . | 管理金鑰 | Key for remote administration | . | 私鑰 | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | 除錯日誌 | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | 管理模式 | Restrict non-admin channel changes | . | 備份金鑰 | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | 螢幕截圖 | . | Dropdown | | . | Toggle | | . | Slider | | . ", + "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#設定" + },"4478": { + "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" + },"4479": { + "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" + },"4480": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4481": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Опис | . | Дуго име | Your display name (up to 39 characters) | . | Кратко име | 4-character abbreviated name | . | Лиценцирани оператор | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-radio-user.html#user-settings", + + "relUrl": "/sr-rLatn/user/settings-radio-user.html#user-settings" + },"4482": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Подешавања уређаја . | Setting | Опис | Подразумевано | . | Улога | Node behavior (Client, Router, etc.) | Клијент | . | Режим реемитовања | How the node retransmits messages | Сви | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Онемогућено | . LoRA подешавања . | Setting | Опис | Подразумевано | . | Регион | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Подешавања приказа . | Setting | Опис | . | Screen Timeout | Time before display sleeps | . | Јединице приказа | Metric or Imperial | . | Тип OLED-а | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Подешавања позиције . | Setting | Опис | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Паметно позиционирање | Enable movement-based broadcasting | . | Фиксна локација | Use a manually set position | . Подешавања напајња . | Setting | Опис | . | Уштеда енергије | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Конфигурација мреже . | Setting | Опис | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Блутут подешавања . | Setting | Опис | . | Bluetooth Enabled | Enable/disable BLE radio | . | Мод упаривања | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Сигурносна подешавања . | Setting | Опис | . | Javni ključ | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Privatni ključ | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/sr-rLatn/user/settings-radio-user.html#configuration" + },"4483": { + "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" + },"4484": { + "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" + },"4485": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4486": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Nastavení | Popis | . | Dlouhé jméno | Your display name (up to 39 characters) | . | Krátké jméno | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-radio-user.html#user-settings", + + "relUrl": "/cs-rCZ/user/settings-radio-user.html#user-settings" + },"4487": { + "doc": "Settings — Radio & User", + "title": "Nastavení", + "content": "Nastavení zařízení . | Nastavení | Popis | Výchozí | . | Role | Node behavior (Client, Router, etc.) | Client | . | Režim opětovného vysílání | How the node retransmits messages | Vše | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa nastavení . | Nastavení | Popis | Výchozí | . | Region | Regulatory region for frequency bands | Unset (must configure) | . | Předvolba modemu | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Nastavení zobrazení . | Nastavení | Popis | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Nastavení pozice . | Nastavení | Popis | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Chytrá poloha | Enable movement-based broadcasting | . | Pevná poloha | Use a manually set position | . Nastavení napájení . | Nastavení | Popis | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Nastavení sítě . | Nastavení | Popis | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Nastavení bluetooth . | Nastavení | Popis | . | Bluetooth Enabled | Enable/disable BLE radio | . | Režim párování | Fixed PIN, Random PIN, or No PIN | . | Pevný PIN | PIN code for pairing (default: 123456) | . Nastavení zabezpečení . | Nastavení | Popis | . | Veřejný klíč | Your node’s public key (read-only) | . | Administrátorský klíč | Key for remote administration | . | Soukromý klíč | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Řízený režim | Restrict non-admin channel changes | . | Záloha klíčů | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#nastaven%C3%AD", + + "relUrl": "/cs-rCZ/user/settings-radio-user.html#nastavení" + },"4488": { + "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" + },"4489": { + "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" + },"4490": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html#settings--radio--user", + + "relUrl": "/en/user/settings-radio-user.html#settings--radio--user" + },"4491": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Description | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html#user-settings", + + "relUrl": "/en/user/settings-radio-user.html#user-settings" + },"4492": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | Description | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Description | Default | . | Region | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Description | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Description | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Description | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Description | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Description | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Description | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ", + "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html#configuration", + + "relUrl": "/en/user/settings-radio-user.html#configuration" + },"4493": { + "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" + },"4494": { + "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" + },"4495": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4496": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Opis | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/settings-radio-user.html#user-settings", + + "relUrl": "/sl-rSI/user/settings-radio-user.html#user-settings" + },"4497": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | Opis | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Opis | Default | . | Regija | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Opis | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Opis | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Opis | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Opis | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Opis | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Opis | . | Javni ključ | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Zasebni ključ | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/sl-rSI/user/settings-radio-user.html#configuration" + },"4498": { + "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" + },"4499": { + "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" + },"4500": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4501": { + "doc": "Settings — Radio & User", + "title": "Impostazioni Utente", + "content": "User Profile . | Impostazione | Descrizione | . | Nome Lungo | Your display name (up to 39 characters) | . | Nome Breve | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/it-rIT/user/settings-radio-user.html#impostazioni-utente", + + "relUrl": "/it-rIT/user/settings-radio-user.html#impostazioni-utente" + },"4502": { + "doc": "Settings — Radio & User", + "title": "Configurazione", + "content": "Configurazione Dispositivo . | Impostazione | Descrizione | Predefinito | . | Ruolo | Node behavior (Client, Router, etc.) | Client | . | Modalità Ritrasmissione | How the node retransmits messages | Tutti | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Configurazione LoRa . | Impostazione | Descrizione | Predefinito | . | Regione | Regulatory region for frequency bands | Unset (must configure) | . | Configurazione Modem | Speed/range tradeoff | LongFast | . | Limite di hop | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Offset Di Frequenza | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0,18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configurazione Schermo . | Impostazione | Descrizione | . | Timeout Schermo | Time before display sleeps | . | Mostra Unità | Metric or Imperial | . | Tipo OLED | Auto, SSD1306, SH1106, SH1107 | . | Orientamento bussola | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Configurazione Posizione . | Impostazione | Descrizione | . | GPS Enabled | Enable/disable GPS | . | Intervallo di aggiornamento GPS | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Posizione Smart | Enable movement-based broadcasting | . | Posizione Fissa | Use a manually set position | . Configurazione Alimentazione . | Impostazione | Descrizione | . | Risparmio energetico | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Configurazione Della Rete . | Impostazione | Descrizione | . | WiFi abilitato | Enable WiFi radio (ESP32 devices) | . | SSID WiFi | Network name to connect to | . | WiFi PSK | Password di rete | . | Server NTP | Time synchronization server | . | Syslog Server | Remote logging server | . Configurazione Bluetooth . | Impostazione | Descrizione | . | Bluetooth Enabled | Enable/disable BLE radio | . | Modalità di abbinamento | Fixed PIN, Random PIN, or No PIN | . | PIN Fisso | PIN code for pairing (default: 123456) | . Configurazione Sicurezza . | Impostazione | Descrizione | . | Chiave Pubblica | Your node’s public key (read-only) | . | Chiave Amministratore | Key for remote administration | . | Chiave Privata | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Log di debug | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Modalità Gestita | Restrict non-admin channel changes | . | Backup chiavi | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configurazione", + + "relUrl": "/it-rIT/user/settings-radio-user.html#configurazione" + },"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/it-rIT/user/settings-radio-user.html#related-topics", + + "relUrl": "/it-rIT/user/settings-radio-user.html#related-topics" + },"4504": { + "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" + },"4505": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4506": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Descrição | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/settings-radio-user.html#user-settings", + + "relUrl": "/pt-rBR/user/settings-radio-user.html#user-settings" + },"4507": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Configuração do Dispositivo . | Setting | Descrição | Padrão | . | Função | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Configuração do LoRa . | Setting | Descrição | Padrão | . | Região | Regulatory region for frequency bands | Unset (must configure) | . | Predefinição do Modem | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuração da Tela . | Setting | Descrição | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Configuração da Posição . | Setting | Descrição | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Configuração de Energia . | Setting | Descrição | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Configuração de Rede . | Setting | Descrição | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Configuração do Bluetooth . | Setting | Descrição | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | PIN fixo | PIN code for pairing (default: 123456) | . Configurações de Segurança . | Setting | Descrição | . | Chave Publica | Your node’s public key (read-only) | . | Chave do Administrador | Key for remote administration | . | Chave Privada | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Modo Administrado | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/pt-rBR/user/settings-radio-user.html#configuration" + },"4508": { + "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" + },"4509": { + "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" + },"4510": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4511": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Lýsing | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/is-rIS/user/settings-radio-user.html#user-settings", + + "relUrl": "/is-rIS/user/settings-radio-user.html#user-settings" + },"4512": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | Lýsing | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Lýsing | Default | . | Svæði | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Lýsing | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Lýsing | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Lýsing | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Lýsing | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Lýsing | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Lýsing | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/is-rIS/user/settings-radio-user.html#configuration" + },"4513": { + "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" + },"4514": { + "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" + },"4515": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4516": { + "doc": "Settings — Radio & User", + "title": "Paramètres utilisateur", + "content": "User Profile . | Setting | Description | . | Nom long | Your display name (up to 39 characters) | . | Nom court | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "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" + },"4517": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Configuration de l’appareil . | Setting | Description | Par défaut | . | Rôle | Node behavior (Client, Router, etc.) | Client | . | Mode de réémission | How the node retransmits messages | Tout | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Désactivé | . Configuration LoRa . | Setting | Description | Par défaut | . | Région | Regulatory region for frequency bands | Unset (must configure) | . | Préréglage du modem | Speed/range tradeoff | LongFast | . | Limite de sauts | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Décalage de fréquence | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuration de l’écran . | Setting | Description | . | Délai d’extinction de l’écran | Time before display sleeps | . | Unités affichées | Metric or Imperial | . | Type d’OLED | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Configuration de la position . | Setting | Description | . | GPS Enabled | Enable/disable GPS | . | Intervalle de mise à jour GPS | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Position Intelligente | Enable movement-based broadcasting | . | Position fixe | Use a manually set position | . Configuration de l’alimentation . | Setting | Description | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Configuration du réseau . | Setting | Description | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Mot de passe du réseau | . | Serveur NTP | Time synchronization server | . | Syslog Server | Remote logging server | . Configuration Bluetooth . | Setting | Description | . | Bluetooth Enabled | Enable/disable BLE radio | . | Mode d’appairage | Fixed PIN, Random PIN, or No PIN | . | Code PIN fixe | PIN code for pairing (default: 123456) | . Configuration de sécurité . | Setting | Description | . | Clé publique | Your node’s public key (read-only) | . | Clé Admin | Key for remote administration | . | Clé privée | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Mode géré | Restrict non-admin channel changes | . | Sauvegarder les clés | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/fr-rFR/user/settings-radio-user.html#configuration" + },"4518": { + "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" + },"4519": { + "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" + },"4520": { "doc": "Settings — Radio & User", "title": "Settings — Radio & User", "content": "Configure your radio hardware and user identity parameters. ", "url": "/Meshtastic-Android/main/srp/user/settings-radio-user.html#settings--radio--user", "relUrl": "/srp/user/settings-radio-user.html#settings--radio--user" - },"4632": { + },"4521": { "doc": "Settings — Radio & User", "title": "User Settings", "content": "User Profile . | Setting | Опис | . | Дуго име | Your display name (up to 39 characters) | . | Кратко име | 4-character abbreviated name | . | Лиценцирани оператор | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", "url": "/Meshtastic-Android/main/srp/user/settings-radio-user.html#user-settings", "relUrl": "/srp/user/settings-radio-user.html#user-settings" - },"4633": { + },"4522": { "doc": "Settings — Radio & User", "title": "Configuration", "content": "Подешавања уређаја . | Setting | Опис | Подразумевано | . | Улога | Node behavior (Client, Router, etc.) | Клијент | . | Режим реемитовања | How the node retransmits messages | Сви | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Онемогућено | . LoRA подешавања . | Setting | Опис | Подразумевано | . | Регион | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Подешавања приказа . | Setting | Опис | . | Screen Timeout | Time before display sleeps | . | Јединице приказа | Metric or Imperial | . | Тип OLED-а | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Подешавања позиције . | Setting | Опис | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Паметно позиционирање | Enable movement-based broadcasting | . | Фиксна локација | Use a manually set position | . Подешавања напајња . | Setting | Опис | . | Уштеда енергије | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Конфигурација мреже . | Setting | Опис | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Блутут подешавања . | Setting | Опис | . | Bluetooth Enabled | Enable/disable BLE radio | . | Мод упаривања | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Сигурносна подешавања . | Setting | Опис | . | Јавни кључ | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Приватни кључ | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ", "url": "/Meshtastic-Android/main/srp/user/settings-radio-user.html#configuration", "relUrl": "/srp/user/settings-radio-user.html#configuration" - },"4634": { + },"4523": { "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" - },"4635": { + },"4524": { "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" - },"4636": { + },"4525": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4526": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Popis | . | Dlhé Meno | Your display name (up to 39 characters) | . | Krátke Meno | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/settings-radio-user.html#user-settings", + + "relUrl": "/sk-rSK/user/settings-radio-user.html#user-settings" + },"4527": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Konfigurácia Zariadenia . | Setting | Popis | Predvolené | . | Rola | Node behavior (Client, Router, etc.) | Klient | . | Rebroadcast Mode | How the node retransmits messages | Všetky | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Konfigurácia LoRa . | Setting | Popis | Predvolené | . | Región | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Konfigurácia Displeju . | Setting | Popis | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Popis | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Inteligentná poloha | Enable movement-based broadcasting | . | Fixná Pozícia | Use a manually set position | . Power Config . | Setting | Popis | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Konfigurácia siete . | Setting | Popis | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Konfigurácia Bluetooth . | Setting | Popis | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Pevný PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Popis | . | Verejný kľúč | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Súkromný kľúč | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/sk-rSK/user/settings-radio-user.html#configuration" + },"4528": { + "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" + },"4529": { + "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" + },"4530": { + "doc": "Asetukset — Radio ja käyttäjä", + "title": "Asetukset — Radio ja käyttäjä", + "content": "Määritä radion laitteisto ja käyttäjätunnistetiedot. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/settings-radio-user.html", + + "relUrl": "/fi-rFI/user/settings-radio-user.html" + },"4531": { + "doc": "Asetukset — Radio ja käyttäjä", + "title": "Käyttäjäasetukset", + "content": "Käyttäjäprofiili . | Asetus | Kuvaus | . | Pitkä nimi | Näyttönimesi (enintään 39 merkkiä) | . | Lyhytnimi | 4-merkkinen lyhytnimi | . | Lisensoitu radioamatööri | Ota käyttöön, jos sinulla on radioamatöörilupa (mahdollistaa suuremman lähetystehon) | . Muutosten käyttöönotto . Asetusten muuttamisen jälkeen napauta Tallenna kirjoittaaksesi määritykset radioon. Laite voidaan käynnistää uudelleen muutosten käyttöönottoa varten. ", + "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" + },"4532": { + "doc": "Asetukset — Radio ja käyttäjä", + "title": "Asetukset", + "content": "Laitteen asetukset . | Asetus | Kuvaus | Oletus | . | Rooli | Radion rooli (Client, Router jne.) | Client | . | Uudelleenlähetyksen tila | Miten radio välittää viestejä eteenpäin | Kaikki | . | Radiotiedon lähetys (s) | Radion tietojen lähetysväli | 10800 | . | Kaksoisnapautuspainike | Toiminto painikkeen kaksoisnapautukselle | Ei käytössä | . LoRa:n asetukset . | Asetus | Kuvaus | Oletus | . | Alue | Taajuusalueiden sääntelyalue | Ei asetettu (on määritettävä) | . | Modeemin esiasetus | Nopeuden ja kantaman välinen kompromissi | LongFast | . | Hyppyraja | Suurin hyppyjen määrä | 3 | . | Lähetysteho | Lähetysteho (dBm): 0 = alueen sallima enimmäisteho | 0 (alueen enimmäisteho) | . | Taajuuspoikkeama | Taajuuden hienosäätö (MHz) | 0 | . | Kanavan kaistanleveys | Kaistanleveysasetus | Esiasetuksen oletusarvo | . ⚠️ Tärkeää: Sinun täytyy määrittää alueesi ennen lähettämistä. Lähettäminen väärällä alueasetuksella voi rikkoa paikallisia radiomääräyksiä. Katso alueasetusten määritysopas meshtastic.org-sivustolta saadaksesi lisätietoja. Esiasetukset . 💡 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 | 5.5 kbps | −10 dB | Lyhyen kantaman esikaupunkialueet; kohtalainen rakennustiheys | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Esikaupunkialueet; kohtalainen rakennustiheys | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Esikaupunki-/maaseutualueet; kohtalainen kantama ja hitaampi nopeus | . | Long Turbo | ~10 km | 4.4 kbps | −12.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 | 5.5 kbps | −12.5 dB | EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Medium Fast -asetukseen | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Long Fast -asetukseen | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz -alue (62,5 kHz BW); välttää häiriöitä muiden laitteiden kanssa | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz -alue (62,5 kHz BW); verrattavissa Long Fast -asetukseen | . | 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ä. Sovelluksen esiasetusvalikossa ne näkyvät nimillä Lyhyt kantama - Nopea, Pitkä kantama - Nopea, Lite - Nopea, Kapea - Nopea ja niin edelleen. Modeemiesiasetuksen valitseminen . 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. | . ⚠️ Tärkeää: Kaikkien samalla kanavalla olevien radioiden täytyy käyttää samaa modeemiesiasetusta. Radiot, joiden modeemiesiasetukset eivät täsmää, eivät voi viestiä keskenään, vaikka ne käyttäisivät samaa taajuutta ja salausavainta. 💡 Vinkki: Yllä olevat 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 . | Asetus | Kuvaus | . | Näytön aikakatkaisu | Aika ennen näytön siirtymistä lepotilaan | . | Näyttöyksiköt | Metrinen tai imperiaalinen järjestelmä | . | OLED-tyyppi | Auto, SSD1306, SH1106, SH1107 | . | Kompassin suunta | Kompassinäytön kiertosäätö (0°, 90°, 180°, 270°) | . | Kompassipohjoinen | ⚠️ Vanhentunut — korvattu Kompassin suunta -asetuksella; näkyy edelleen vanhemmissa laiteohjelmistoversioissa | . Sijainnin asetukset . | Asetus | Kuvaus | . | GPS-käytössä | Ota GPS käyttöön tai poista käytöstä | . | GPS-päivitysväli | Kuinka usein GPS-paikannusta päivitetään | . | Sijainnin lähetys (s) | Kuinka usein sijaintia jaetaan | . | Älykäs sijainti | Ota liikkeeseen perustuva lähetys käyttöön | . | Kiinteä sijainti | Käytä manuaalisesti asetettua sijaintia | . Virran asetukset . | Asetus | Kuvaus | . | Virransäästö | Ota vähän virtaa kuluttava lepotila käyttöön | . | Sammuta jälkeen (s) | Automaattisen sammutuksen ajastin | . | ADC-kerroin | Akun jännitteen kalibrointikerroin | . | Odota Bluetoothia (s) | Aika Bluetooth-yhteyden odottamiseen käynnistyksen yhteydessä | . | Mesh SDS -aikakatkaisu (s) | Erittäin syvän lepotilan aikakatkaisu | . Verkon asetukset . | Asetus | Kuvaus | . | WiFi käytössä | Ota WiFi-radio käyttöön (ESP32-laitteet) | . | WiFi SSID | Verkon nimi, johon yhdistetään | . | WiFi PSK | Verkon salasana | . | NTP-palvelin | Ajan synkronointipalvelin (NTP-palvelin) | . | Syslog-palvelin | Etätietojen palvelin | . Bluetooth asetukset . | Asetus | Kuvaus | . | Bluetooth käytössä | Ota Bluetooth-radio käyttöön tai poista käytöstä | . | Pariliitostila | Kiinteä PIN-koodi, satunnainen PIN-koodi tai ei PIN-koodia | . | Kiinteä PIN-koodi | PIN-koodi pariliitosta varten (oletus: 123456) | . Turvallisuusasetukset . | Asetus | Kuvaus | . | Julkinen avain | Radiosi julkinen avain (vain luku) | . | Ylläpitäjän avain | Avain etähallintaa varten | . | Yksityinen avain | Radiosi yksityinen avain (käsittele turvallisesti) | . | Ylläpitokanava käytössä | ⚠️ Poistettu — määritetään nyt automaattisesti, kun ylläpitoavain asetetaan | . | Virheenkorjausloki | Tulosta reaaliaikainen virheenkorjausloki sarjaportin tai bluetoothin kautta | . | Sarjaportti käytössä | Ota sarjakonsoliyhteys käyttöön (siirretty laiteasetuksista) | . | Hallintatila | Rajoita muutokset muihin kuin ylläpitokanaviin | . | Varmuuskopioi avaimet | Tallenna radion avaimista salattu varmuuskopio tälle laitteelle (vain Android) | . | Palauta avaimet | Kirjoita varmuuskopioidut avaimet takaisin radioon (käytettävissä, kun varmuuskopio on olemassa) | . | Poista avaimen varmuuskopio | Poista tälle laitteelle tallennettu avainten varmuuskopio | . | Suojaustaso | Pakettien aitous – miten allekirjoittamattomia tai välitettyjä paketteja käsitellään: Tiukka, Tasapainoinen tai Yhteensopiva (edellyttää tuettua laiteohjelmistoa; Tiukka pyytää vahvistuksen) | . 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#asetukset", + + "relUrl": "/fi-rFI/user/settings-radio-user.html#asetukset" + },"4533": { + "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" + },"4534": { + "doc": "Настройки - Радио и пользователь", + "title": "Настройки - Радио и пользователь", + "content": "Настройте радиоустройство и параметры идентификации пользователя. ", + "url": "/Meshtastic-Android/main/ru-rRU/user/settings-radio-user.html", + + "relUrl": "/ru-rRU/user/settings-radio-user.html" + },"4535": { + "doc": "Настройки - Радио и пользователь", + "title": "Настройки пользователя", + "content": "Профиль пользователя . | Настройка | Описание | . | Полное имя | Ваше отображаемое имя (до 39 символов) | . | Короткое имя | 4-символьное сокращённое имя | . | Лицензированный оператор | Включите, если у вас есть лицензия радиолюбителя (позволяет использовать более высокую мощность) | . Применение изменений . После изменения настроек нажмите Сохранить чтобы записать конфигурацию в ваше радиоустройство. Устройство может перезагрузиться для применения изменений. ", + "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#настройки-пользователя" + },"4536": { + "doc": "Настройки - Радио и пользователь", + "title": "Настройки", + "content": "Настройки устройства . | Настройка | Описание | По умолчанию | . | Роль | Поведение ноды (Client, Router и т.д.) | Client | . | Режим ретрансляции | Как нода повторно передает сообщения | Всё | . | Передача информации ноды | Интервал для передачи информации ноды | 10800 | . | Двойное нажатие кнопки | Действие при двойном нажатии кнопки | Включено | . Настройка LoRa . | Настройка | Описание | По умолчанию | . | Регион / Страна | Область регулирования для диапазонов частот | Не установлено (необходимо настроить) | . | Режим работы модема | Компромисс между скоростью и дальностью | LongFast | . | Лимит хопов | Максимальное количество ретрансляций | 3 | . | Мощность передачи | Мощность передачи (дБм); 0 = максимально разрешённая для региона | 0 (максимум региона) | . | Частотное смещение | Точная настройка частоты (МГц) | 0 | . | Полоса пропускания канала | Настройка пропускной способности | По умолчанию для предустановки | . ⚠️ Важно: Вы обязаны установить свой регион перед отправкой. Работа без правильного региона может нарушать местные правила радиопользования. Смотрите руководство по настройке региона на сайте meshtastic.org для получения подробной информации. Предустановки модема . 💡 Совет: Значения порога SNR специально отрицательные. LoRa может декодировать сигналы ниже уровня шума, поэтому более отрицательный предел означает, что пресет допускает более слабый, шумный сигнал (больший радиус действия). Смотрите Как работает измеритель сигнала для полного объяснения. | Предустановка | Диапазон | Скорость | Предел SNR | Лучше всего для | . | Short Turbo | ~1 км | 21.9 кб/с | −7.5 дБ | Плотная городская застройка с прямой видимостью; приложения, требующие высокой передачи данных | . | Short Fast | ~3 км | 10.9 кб/с | −7.5 дБ | Городские районы; здания в пределах нескольких кварталов | . | Short Slow | ~5 км | 5.5 кб/с | -10 дБ | Пригородная зона с коротким диапазоном; умеренная плотность застройки | . | Medium Fast | ~5 км | 5.5 кб/с | −12.5 дБ | Пригородные районы; умеренная плотность застройки | . | Medium Slow | ~8 км | 1.1 кб/с | -15 дБ | Пригородный/сельский; умеренный диапазон со сниженной скоростью | . | Long Turbo | ~10 км | 4.4 кб/с | −12.5 дБ | Диапазон, похожий на Long Fast, но с полосой пропускания 500 кГц; более высокая пропускная способность | . | Long Fast | ~10 км | 1.1 кб/с | −17.5 дБ | Общее использование (по умолчанию) — сбалансированный диапазон и скорость | . | Long Moderate | ~20 км | 0.34 кб/с | −17.5 дБ | Сельская местность с некоторым рельефом; случайное использование | . | Lite Fast | ~5 км | 5.5 кб/с | −12.5 дБ | Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Medium Fast | . | Lite Slow | ~10 км | 1.1 кб/с | -15 дБ | Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Long Fast | . | Narrow Fast | ~5 км | 2.7 кб/с | -10 дБ | Диапазон RU 868 МГц (полоса пропускания 62,5 кГц); предотвращает помехи с другими устройствами | . | Narrow Slow | ~10 км | 1.1 кб/с | −12.5 дБ | Диапазон RU 868 МГц (ширина полосы 62,5 кГц); аналогично Long Fast | . | Long Slow | ~30 км | 0.18 кб/с | −20 дБ | ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки | . | Very Long Slow | ~40+ км | 0.09 кб/с | −20 дБ | ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки | . i Примечание: В этой таблице используются общие короткие имена. В выпадающем меню пресетов приложения они читаются как Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast и так далее. Выбор предустановки модема . Предустановка модема управляет основным компромиссом между дальностью и скоростью передачи данных: . | Медленные предустановки используют большее распространение, что позволяет декодировать сигналы при более слабых уровнях сигнала (ниже порога 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 — это настройка по умолчанию в сообществе и она обеспечит совместимость с другими в вашем регионе. | . ⚠️ Важно: Все ноды в одном канале должны использовать один и тот же пресет модема. Ноды с несовпадающими предустановками не смогут обмениваться данными, даже если они используют одну частоту и ключ шифрования. 💡 Совет: Указанные выше оценки дальности предполагают ровную местность и небольшие антенны. Преимущество высоты (вершина холма, крыша) значительно увеличивает эффективную дальность. Хорошо размещённый маршрутизатор с Long Fast часто может превзойти наземную ноду с Long Slow. Параметры дисплея . | Настройка | Описание | . | Время ожидания | Время до перехода в спящий режим | . | Единицы измерения | Метрическая или имперская | . | Тип OLED-дисплея | Авто, SSD1306, SH1106, SH1107 | . | Ориентация компаса | Смещение вращения для отображения компаса (0°, 90°, 180°, 270°) | . | Север компаса | ⚠️ Устарело — заменено на ориентацию компаса; по-прежнему видно в старой прошивке | . Настройки местоположения . | Настройка | Описание | . | GPS включен | Включение/отключение GPS | . | Интервал обновления GPS | Как часто получать GPS-фиксацию | . | Вещание позиции | Как часто делиться местоположением | . | Умная позиция | Включить трансляцию при движении | . | Фиксированная позиция | Использовать вручную заданное положение | . Настройка питания . | Настройка | Описание | . | Энергосбережение | Включить спящий режим с низким энергопотреблением | . | Завершение работы через | Таймер автоотключения при простое | . | Множитель ADC | Коэффициент калибровки напряжения батареи | . | Ожидание Bluetooth | Время ожидания подключения BLE при загрузке | . | Тайм-аут Mesh SDS | Тайм-аут сверхглубокого сна | . Настройка сети . | Настройка | Описание | . | WiFi включен | Включить радиомодуль WiFi (устройства ESP32) | . | WiFi SSID | Имя сети для подключения | . | WiFi PSK | Пароль сети | . | NTP-сервер | Сервер синхронизации времени | . | Syslog-сервер | Удалённый сервер логирования | . Настройка Bluetooth . | Настройка | Описание | . | Bluetooth включен | Включение/отключение BLE радиостанции | . | Режим сопряжения | Фиксированный PIN, случайный PIN или без PIN | . | Фиксированный PIN-код | PIN-код для сопряжения (по умолчанию: 123456) | . Настройки безопасности . | Настройка | Описание | . | Публичный ключ | Публичный ключ твоей ноды (только для чтения) | . | Ключ администратора | Ключ для удалённого администрирования | . | Приватный ключ | Приватный ключ твоей ноды (обращайся с ним осторожно) | . | Канал администратора включен | ⚠️ Удалено — теперь настраивается автоматически при установке ключа администратора | . | Журнал отладки | Выводить живой отладочный лог через последовательный порт/Bluetooth | . | Последовательная включена | Включить доступ к последовательной консоли (перемещено из настроек устройства) | . | Управляемый режим | Ограничить изменения канала для неадминистраторов | . | Резервное копирование | Сохранить зашифрованную резервную копию ключей ноды на этом устройстве (только для Android) | . | Восстановить ключи | Запишисать сохранённые ключи обратно на ноду (доступно, как только есть резервная копия) | . | Удалить резервную копию ключа | Удалить сохранённую резервную копию ключа с этого устройства | . | Уровень защиты | Подлинность пакета — как обрабатываются неподписанные или пересылаемые пакеты: Строго, Сбалансировано или Совместимо (требуется поддержка прошивкой; Строго требует подтверждения) | . Настройки используют стандартные элементы управления предпочтениями — выпадающие списки, переключатели и ползунки: . | Управление | Снимок экрана | . | Выпадающий список | | . | Переключатель | | . | Ползунок | | . ", + "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#настройки" + },"4537": { + "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#связанные-темы" + },"4538": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4539": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | 설명 | . | 긴 이름 | Your display name (up to 39 characters) | . | 짧은 이름 | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/settings-radio-user.html#user-settings", + + "relUrl": "/ko-rKR/user/settings-radio-user.html#user-settings" + },"4540": { + "doc": "Settings — Radio & User", + "title": "설정", + "content": "장치 설정 . | Setting | 설명 | 기본값 | . | 역할 | Node behavior (Client, Router, etc.) | Client | . | 중계 모드 | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa 설정 . | Setting | 설명 | 기본값 | . | 지역 | Regulatory region for frequency bands | Unset (must configure) | . | 모뎀 프리셋 | Speed/range tradeoff | LongFast | . | Hop 제한 | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | 주파수 오프셋 | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 화면 설정 . | Setting | 설명 | . | 화면 끄기 시간 | Time before display sleeps | . | 단위 표시 | Metric or Imperial | . | OLED 타입 | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . 위치 설정 . | Setting | 설명 | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . 전원 설정 . | Setting | 설명 | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . 네트워크 설정 . | Setting | 설명 | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | 네트워크 암호 | . | NTP 서버 | Time synchronization server | . | Syslog Server | Remote logging server | . 블루투스 설정 . | Setting | 설명 | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | 고정 PIN | PIN code for pairing (default: 123456) | . 보안 설정 . | Setting | 설명 | . | 공개 키 | Your node’s public key (read-only) | . | Admin 키 | Key for remote administration | . | 개인 키 | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | 관리 모드 | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#%EC%84%A4%EC%A0%95", + + "relUrl": "/ko-rKR/user/settings-radio-user.html#설정" + },"4541": { + "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" + },"4542": { + "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" + },"4543": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4544": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Opis | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/settings-radio-user.html#user-settings", + + "relUrl": "/hr-rHR/user/settings-radio-user.html#user-settings" + },"4545": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | Opis | Zadano | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Opis | Zadano | . | Regija | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Opis | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Opis | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Opis | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Opis | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Postavke Bluetootha . | Setting | Opis | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Opis | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/hr-rHR/user/settings-radio-user.html#configuration" + },"4546": { + "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" + },"4547": { + "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" + },"4548": { "doc": "Settings — Radio & User", "title": "Settings — Radio & User", "content": "Configure your radio hardware and user identity parameters. ", "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" - },"4637": { + },"4549": { "doc": "Settings — Radio & User", "title": "User Settings", "content": "User Profile . | Setting | Përshkrimi | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", "url": "/Meshtastic-Android/main/sq-rAL/user/settings-radio-user.html#user-settings", "relUrl": "/sq-rAL/user/settings-radio-user.html#user-settings" - },"4638": { + },"4550": { "doc": "Settings — Radio & User", "title": "Configuration", "content": "Device Config . | Setting | Përshkrimi | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Përshkrimi | Default | . | Rajon | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Përshkrimi | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Përshkrimi | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Përshkrimi | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Përshkrimi | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Përshkrimi | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Përshkrimi | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", "relUrl": "/sq-rAL/user/settings-radio-user.html#configuration" - },"4639": { + },"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/sq-rAL/user/settings-radio-user.html#related-topics", "relUrl": "/sq-rAL/user/settings-radio-user.html#related-topics" - },"4640": { + },"4552": { "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" - },"4641": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html", + },"4553": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "url": "/Meshtastic-Android/main/no-rNO/user/settings-radio-user.html#settings--radio--user", - "relUrl": "/is-rIS/user/signal-meter.html" - },"4642": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "relUrl": "/no-rNO/user/settings-radio-user.html#settings--radio--user" + },"4554": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Beskrivelse | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/no-rNO/user/settings-radio-user.html#user-settings", - "relUrl": "/is-rIS/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4643": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "relUrl": "/no-rNO/user/settings-radio-user.html#user-settings" + },"4555": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | Beskrivelse | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Beskrivelse | Default | . | Region | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Beskrivelse | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Beskrivelse | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Beskrivelse | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Beskrivelse | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Beskrivelse | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Beskrivelse | . | Offentlig nøkkel | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Privat nøkkel | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - "relUrl": "/is-rIS/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4644": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/is-rIS/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4645": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/is-rIS/user/signal-meter.html#4-what-this-means-for-you" - },"4646": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4647": { - "doc": "How the Meshtastic Signal Meter Works", + "relUrl": "/no-rNO/user/settings-radio-user.html#configuration" + },"4556": { + "doc": "Settings — Radio & User", "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", + "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": "/is-rIS/user/signal-meter.html#related-topics" - },"4648": { - "doc": "Meshtastic の信号メーターの仕組み", - "title": "Meshtastic の信号メーターの仕組み", - "content": "Meshtastic の信号メーター（アプリでおなじみのバーやステータスの色）は、従来の携帯電話や WiFi ルーターの「バー」とはまったく異なる方法で計算されます。 . ほとんどの一般向けデバイスは、単に信号がどれだけ「大きい」かを測定します。 しかし Meshtastic は LoRa（Long Range）技術を使用しているため、その信号メーターは、メッシュが使用している具体的な設定を基準に、信号がどれだけ明瞭かを測定します。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html", + "relUrl": "/no-rNO/user/settings-radio-user.html#related-topics" + },"4557": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": " ", + "url": "/Meshtastic-Android/main/no-rNO/user/settings-radio-user.html", - "relUrl": "/ja-rJP/user/signal-meter.html" - },"4649": { - "doc": "Meshtastic の信号メーターの仕組み", - "title": "1. 2 つの指標：「大きさ」と「明瞭さ」", - "content": "LoRa の無線チップは、メッセージを受信するたびに 2 つの測定値を報告します： . | RSSI（受信信号強度インジケーター）： アンテナに届く生の電力の大きさ。 | SNR（信号対ノイズ比）： 背景のノイズと比較した信号の明瞭さ。 | . 💡 ヒント： たとえて言うと、友人があなたに話しかけているのを聞き取ろうとしている場面を想像してください。 . | RSSI は、その声がどれだけ大きいかです。 | ノイズフロアは、部屋の中の背景ノイズ（エアコン、他の人の話し声、交通音）です。 | SNR は、背景ノイズの中から友人の声をどれだけ簡単に聞き分けられるかです。 | . 耳をつんざくようなロックコンサートで友人が叫んでも、信号は非常に大きい（高い RSSI）一方で、背景ノイズのほうが大きいため（悪い SNR）、聞き取れません。 逆に、静まり返った図書館で友人がささやけば、信号は非常に弱い（低い RSSI）ものの、完璧に聞き取れます（非常に良い SNR）。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#1-2-%E3%81%A4%E3%81%AE%E6%8C%87%E6%A8%99%E5%A4%A7%E3%81%8D%E3%81%95%E3%81%A8%E6%98%8E%E7%9E%AD%E3%81%95", + "relUrl": "/no-rNO/user/settings-radio-user.html" + },"4558": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/settings-radio-user.html#settings--radio--user", - "relUrl": "/ja-rJP/user/signal-meter.html#1-2-つの指標大きさと明瞭さ" - },"4650": { - "doc": "Meshtastic の信号メーターの仕組み", - "title": "2. LoRa の魔法：「ノイズフロアの下」を聞き取る", - "content": "標準的な無線（FM や WiFi など）では、背景ノイズが信号より大きい（負の SNR）場合、受信機にはノイズしか聞こえません。 . LoRa は特別です。 **「スペクトラム拡散」**変調を使用しており、信号が背景ノイズの下深くに埋もれていても、無線機が数学的に信号を取り出せます。 そのため Meshtastic では、負の SNR 値が頻繁に見られます（例：-10 dB。これは信号が背景ノイズより 10 デシベル弱いことを意味します）。 . 使用している Meshtastic のプリセット（例：LongFast と ShortFast）に応じて、無線機には固有の SNR 限界があります。これは、メッセージがノイズに完全に埋もれてしまう前に許容できるノイズの絶対的な最大量です。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#2-lora-%E3%81%AE%E9%AD%94%E6%B3%95%E3%83%8E%E3%82%A4%E3%82%BA%E3%83%95%E3%83%AD%E3%82%A2%E3%81%AE%E4%B8%8B%E3%82%92%E8%81%9E%E3%81%8D%E5%8F%96%E3%82%8B", + "relUrl": "/lt-rLT/user/settings-radio-user.html#settings--radio--user" + },"4559": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Aprašymas | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/settings-radio-user.html#user-settings", - "relUrl": "/ja-rJP/user/signal-meter.html#2-lora-の魔法ノイズフロアの下を聞き取る" - },"4651": { - "doc": "Meshtastic の信号メーターの仕組み", - "title": "3. 信号メーターが品質を計算する仕組み", - "content": "アプリは、信号品質（なし・不良・普通・良）を SNR のみから、プリセットの SNR 限界を基準として評価します。これは前述の復調限界です。 この評価には、意図的に RSSI を含めていません。ローカルのノイズフロアが分からなければ、RSSI だけでは信号が実際に復調できるかどうかは分からないため、プリセット限界に対する SNR が意味のある指標になります。 （RSSI は、別の場所には引き続き表示されます。） . 評価はプリセット限界を基準とするため、同じ SNR でもプリセットによって評価が異なります。-15 dB は LongSlow では良好ですが、ShortFast では使い物になりません。 limit を現在のプリセットの SNR 限界とすると、アプリがバー（または色）を選ぶ方法は次のとおりです： . | レベル | バー | 基準 | 意味 | . | 良 | 3 | SNR がプリセットの limit を上回る | 信号が復調限界を十分に上回っています。良好な接続です。 | . | 普通 | 2 | limit より 5.5 dB 未満低い | 復調できますが、限界に近づいています。 | . | 不良 | 1 | limit より 5.5 dB〜7.5 dB 低い | プリセットが復元できるぎりぎりの境界です。 | . | なし | 0 | limit より 7.5 dB を超えて低い | 限界を下回っています。送信がノイズに埋もれて失われます。 | . 注意： 他の場所で見かけたことのある固定の SNR しきい値（-7 dB／-15 dB）は、現在ではルート追跡の結果で個々のホップに色を付けるためだけに使われ、ここで説明しているノードごとの信号メーターには使われません。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#3-%E4%BF%A1%E5%8F%B7%E3%83%A1%E3%83%BC%E3%82%BF%E3%83%BC%E3%81%8C%E5%93%81%E8%B3%AA%E3%82%92%E8%A8%88%E7%AE%97%E3%81%99%E3%82%8B%E4%BB%95%E7%B5%84%E3%81%BF", + "relUrl": "/lt-rLT/user/settings-radio-user.html#user-settings" + },"4560": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | Aprašymas | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Aprašymas | Default | . | Regionas | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Aprašymas | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Aprašymas | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Aprašymas | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Aprašymas | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Aprašymas | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Aprašymas | . | Viešasis raktas | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Privatus raktas | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - "relUrl": "/ja-rJP/user/signal-meter.html#3-信号メーターが品質を計算する仕組み" - },"4652": { - "doc": "Meshtastic の信号メーターの仕組み", - "title": "4. これがあなたにとって意味すること", - "content": "Meshtastic のメーターは**「明瞭さのメーター」**として機能するため、多くの人が予想するのとは異なる動作をします： . 💡 ヒント： RSSI が低くても慌てないでください。 -118 dBm のような、一見ひどい RSSI 値が表示されることがあります。 携帯電話なら、バーはゼロでしょう。 しかし SNR が +2 dB あれば、Meshtastic は依然として強い信号を表示します！ 図書館は静かなので、ささやき声も完璧に聞こえます。 . ⚠️ 警告： ローカルのノイズに注意してください。 大型のアンテナを接続して優れた RSSI（例：-90 dBm）が表示されているのに、信号メーターが **1 本（不良）**しか表示していない場合、問題があります。 これは、ローカルの干渉（安価な電源、ノイズの多いコンピューター、近くの電波塔など）が大量のノイズを発生させ、メッシュをかき消していることを意味します。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#4-%E3%81%93%E3%82%8C%E3%81%8C%E3%81%82%E3%81%AA%E3%81%9F%E3%81%AB%E3%81%A8%E3%81%A3%E3%81%A6%E6%84%8F%E5%91%B3%E3%81%99%E3%82%8B%E3%81%93%E3%81%A8", + "relUrl": "/lt-rLT/user/settings-radio-user.html#configuration" + },"4561": { + "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": "/ja-rJP/user/signal-meter.html#4-これがあなたにとって意味すること" - },"4653": { - "doc": "Meshtastic の信号メーターの仕組み", - "title": "信号情報が表示される場所", - "content": "アプリでは、信号データはいくつかの場所に表示されます： . | ノードリスト：各ノードの横にある信号バーのアイコン | ノードの詳細：デバイスメトリクスのセクションにある SNR、RSSI、信号品質 | ルート追跡：各中継ノードの、ホップごとの信号品質 | 信号メトリクス：メトリクスのグラフにある SNR と RSSI の履歴データ | . ", - "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": "/lt-rLT/user/settings-radio-user.html#related-topics" + },"4562": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": " ", + "url": "/Meshtastic-Android/main/lt-rLT/user/settings-radio-user.html", - "relUrl": "/ja-rJP/user/signal-meter.html#信号情報が表示される場所" - },"4654": { - "doc": "Meshtastic の信号メーターの仕組み", + "relUrl": "/lt-rLT/user/settings-radio-user.html" + },"4563": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4564": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | الوصف | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/settings-radio-user.html#user-settings", + + "relUrl": "/ar-rSA/user/settings-radio-user.html#user-settings" + },"4565": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | الوصف | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | الوصف | Default | . | الجهة | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | الوصف | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | الوصف | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | الوصف | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | الوصف | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | الوصف | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | الوصف | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/ar-rSA/user/settings-radio-user.html#configuration" + },"4566": { + "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" + },"4567": { + "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" + },"4568": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4569": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Descrição | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/settings-radio-user.html#user-settings", + + "relUrl": "/pt-rPT/user/settings-radio-user.html#user-settings" + },"4570": { + "doc": "Settings — Radio & User", + "title": "Configuração", + "content": "Configuração do Dispositivo . | Setting | Descrição | Predefinição | . | Papel | Node behavior (Client, Router, etc.) | Cliente | . | Rebroadcast Mode | How the node retransmits messages | Tudo | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Configuração de LoRa . | Setting | Descrição | Predefinição | . | Região | Regulatory region for frequency bands | Unset (must configure) | . | Predefinição de modem | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuração do Ecrã . | Setting | Descrição | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Configuração da posição . | Setting | Descrição | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Posição Inteligente | Enable movement-based broadcasting | . | Posição fixa | Use a manually set position | . Configuração de Energia . | Setting | Descrição | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Configuração de Rede . | Setting | Descrição | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Configuração de Bluetooth . | Setting | Descrição | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | PIN fixo | PIN code for pairing (default: 123456) | . Configuração de Segurança . | Setting | Descrição | . | Chave pública | Your node’s public key (read-only) | . | Chave do Administrador | Key for remote administration | . | Chave privada | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Modo Administrado | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configura%C3%A7%C3%A3o", + + "relUrl": "/pt-rPT/user/settings-radio-user.html#configuração" + },"4571": { + "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" + },"4572": { + "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" + },"4573": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4574": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | תיאור | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/settings-radio-user.html#user-settings", + + "relUrl": "/iw-rIL/user/settings-radio-user.html#user-settings" + },"4575": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | תיאור | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | תיאור | Default | . | אזור | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | תיאור | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | תיאור | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | תיאור | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | תיאור | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | תיאור | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | תיאור | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/iw-rIL/user/settings-radio-user.html#configuration" + },"4576": { + "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" + },"4577": { + "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" + },"4578": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4579": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Περιγραφή | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/el-rGR/user/settings-radio-user.html#user-settings", + + "relUrl": "/el-rGR/user/settings-radio-user.html#user-settings" + },"4580": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | Περιγραφή | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Περιγραφή | Default | . | Περιφέρεια | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Περιγραφή | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Περιγραφή | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Περιγραφή | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Περιγραφή | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Ρυθμίσεις Bluetooth . | Setting | Περιγραφή | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Περιγραφή | . | Δημόσιο Κλειδί | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Ιδιωτικό Κλειδί | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/el-rGR/user/settings-radio-user.html#configuration" + },"4581": { + "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" + },"4582": { + "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" + },"4583": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4584": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Descriere | . | Nume lung | Your display name (up to 39 characters) | . | Nume scurt | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/settings-radio-user.html#user-settings", + + "relUrl": "/ro-rRO/user/settings-radio-user.html#user-settings" + },"4585": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | Descriere | Prestabilit | . | Role | Node behavior (Client, Router, etc.) | Client | . | Mod de redifuzare | How the node retransmits messages | Toate | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Descriere | Prestabilit | . | Regiune | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Descriere | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Descriere | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Poziție inteligentă | Enable movement-based broadcasting | . | Poziție fixă | Use a manually set position | . Configurare Putere . | Setting | Descriere | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Descriere | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Configurare Bluetooth . | Setting | Descriere | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | PIN fix | PIN code for pairing (default: 123456) | . Security Config . | Setting | Descriere | . | Chei publice | Your node’s public key (read-only) | . | Cheie Administrator | Key for remote administration | . | Cheia privată | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Mod Gestionat | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/ro-rRO/user/settings-radio-user.html#configuration" + },"4586": { + "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" + },"4587": { + "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" + },"4588": { + "doc": "Seaded — raadio ja kasutaja", + "title": "Seaded — raadio ja kasutaja", + "content": "Configure your radio hardware and user identity parameters. ", + "url": "/Meshtastic-Android/main/et-rEE/user/settings-radio-user.html", + + "relUrl": "/et-rEE/user/settings-radio-user.html" + },"4589": { + "doc": "Seaded — raadio ja kasutaja", + "title": "Kasutaja seaded", + "content": "User Profile . | Setting | Kirjeldus | . | Täis nimi | Your display name (up to 39 characters) | . | Lühi nimi | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . Pärast sätete muutmist puuduta nuppu Salvesta, et konfiguratsioon raadiosse salvestada. Muudatuste rakendamiseks võib seade taaskäivituda. ", + "url": "/Meshtastic-Android/main/et-rEE/user/settings-radio-user.html#kasutaja-seaded", + + "relUrl": "/et-rEE/user/settings-radio-user.html#kasutaja-seaded" + },"4590": { + "doc": "Seaded — raadio ja kasutaja", + "title": "Sätted", + "content": "Seadme sätted . | Setting | Kirjeldus | Vaikimisi | . | Roll | Node behavior (Client, Router, etc.) | Klient | . | Kordusülekannete režiim | How the node retransmits messages | Kõik | . | Sõlme(de) teabe levitamine | Sõlme teabe levitamise intervall | 10800 | . | Topeltpuudutusnupp | Toiming topeltpuudutuse nupu korral | Keelatud | . LoRa sätted . | Setting | Kirjeldus | Vaikimisi | . | Regioon | Sagedusribade reguleerimispiirkond | Määramata (tuleb seadistada) | . | Modemi vaikesäte | Speed/range tradeoff | LongFast | . | Hüppete limiit | Maks uuesti saadetud hüpet | 3 | . | TX võimsus | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Sagedusnihe | Sageduse peenhäälestamine (MHz) | 0 | . | Kanali ribalaius | Bandwidth setting | Default for preset | . ⚠️ Tähtis: Enne edastamist peate oma piirkonna määrama. Operating without the correct region may violate local radio regulations. Lisateabe saamiseks vaadake regiooni seadistamise juhendit aadressil meshtastic.org. Modem Presets . 💡 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 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 | Linnaosad; hooned mõne kvartali raadiuses | . | Short Slow | ~5 km | 5.5 kbps | −10 dB | Äärelinna lühimaa; mõõdukas hoonestustihedus | . | Medium Fast | ~5 km | 5.5 kbps | −12,5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1,1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4,4 kbps | −12,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 | 5,5 kbps | −12,5 dB | EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Medium Fast | . | Lite Slow | ~10 km | 1,1 kbps | −15 dB | EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Long Fast | . | Narrow Fast | ~5 km | 2,7 kbps | −10 dB | EL 868 MHz sagedusala (62,5 kHz sagedusriba); väldib häireid teiste seadmetega | . | Narrow Slow | ~10 km | 1,1 kbps | −12,5 dB | EL 868 MHz sagedusala (62,5 kHz ribalaius); võrreldav Long Fast | . | 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. Rakenduse eelseadistatud rippmenüüs on need järgmised: Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, jne. 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. | 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. | 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. | . ⚠️ Tähtis: Kõik samal kanalil olevad sõlmed peavad kasutama sama modemi eelseadistust. Erinevate eelseadetega sõlmed ei saa suhelda isegi siis, kui neil on sama sagedus ja krüpteerimisvõti. 💡 Vihje: ulatuse hinnangud eeldavad tasast maastikku ja mõõdukaid antenne. 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. Ekraani sätted . | Setting | Kirjeldus | . | Screen Timeout | Time before display sleeps | . | Display Units | Meetriline või Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Vananenud — asendatud kompassi suunaga; nähtav endiselt vanemas püsivaras | . Asukoha sätted . | Setting | Kirjeldus | . | GPS lubatud | GPS lubamine/keelamine | . | GPS värskendamise intervall | Kui tihti GPS asukohta leida | . | Asukoha(de) levitamine | How often to share position | . | Nutikas asukoht | Liikumispõhise levitamise lubamine | . | Määratud asukoht | Use a manually set position | . Toite sätted . | Setting | Kirjeldus | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Aku pinge kalibreerimistegur | . | Oota sinihammast(id) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Ülisügava une ajalõpp | . Võrgu sätted . | Setting | Kirjeldus | . | WiFi lubatud | Luba WiFi (ESP32 seade) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP server | Time synchronization server | . | Syslog Server | Kauglogimise server | . Sinihamba sätted . | Setting | Kirjeldus | . | Sinihammas lubatud | Enable/disable BLE radio | . | Sidumisreziim | Määratud PIN kood, juhuslik PIN kood või PIN koodi pole | . | Fikseeritud PIN | Sidumise PIN (vaikimisi: 123456) | . Turva sätted . | Setting | Kirjeldus | . | Avalik võti | Sinu sõlme avalik võti (kirjutuskaitstud) | . | Administraatori võti | Kaughalduse võti | . | Salajane võti | Sinu sõlme privaatvõti (käsitsege turvaliselt) | . | Admin kanal lubatud | ⚠️ Eemaldatud — nüüd seadistatakse automaatselt, kui administraatori võti on määratud | . | Arendaja logi | Edasta reaalajas arendajalogi jadapordi/sinihamba ​​kaudu | . | Jadaühendus lubatud | Luba jadapordi konsoolile juurdepääs (teisaldatud seadme konfist) | . | Hallatud režiim | Piira mitte-administraatori kanali muudatusi | . | Taastevõtmed | Salvesta sõlme võtmete krüpteeritud varukoopia sellesse seadmesse (ainult Android) | . | Taasta võtmed | Kirjuta varundatud võtmed tagasi sõlme (saadaval siis, kui varukoopia on olemas) | . | Kustuta taastevõtmed | Eemalda salvestatud võtme varukoopia sellest seadmest | . | Protection Level | Pakettide autentsus – kuidas käsitletakse allkirjastamata või vahendatud pakette: range, tasakaalustatud või ühilduv (nõuab toetavat püsivara; range režiimi puhul küsitakse kinnitust) | . 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#s%C3%A4tted", + + "relUrl": "/et-rEE/user/settings-radio-user.html#sätted" + },"4591": { + "doc": "Seaded — raadio ja kasutaja", + "title": "Related Topics", + "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#related-topics", + + "relUrl": "/et-rEE/user/settings-radio-user.html#related-topics" + },"4592": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4593": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Cur síos | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/settings-radio-user.html#user-settings", + + "relUrl": "/ga-rIE/user/settings-radio-user.html#user-settings" + },"4594": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | Cur síos | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Cur síos | Default | . | Réigiún | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Cur síos | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Cur síos | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Cur síos | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Cur síos | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | 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 (default: 123456) | . Security Config . | Setting | Cur síos | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/ga-rIE/user/settings-radio-user.html#configuration" + },"4595": { + "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" + },"4596": { + "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" + },"4597": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4598": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Opis | . | Długa nazwa | Your display name (up to 39 characters) | . | Krótka nazwa | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/settings-radio-user.html#user-settings", + + "relUrl": "/pl-rPL/user/settings-radio-user.html#user-settings" + },"4599": { + "doc": "Settings — Radio & User", + "title": "Konfiguracja", + "content": "Konfiguracja urządzenia . | Setting | Opis | Domyślny | . | Rola | Node behavior (Client, Router, etc.) | Klient | . | Tryb retransmisji | How the node retransmits messages | Wszystkie | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Wyłączony | . Konfiguracja LoRa . | Setting | Opis | Domyślny | . | Region | Regulatory region for frequency bands | Unset (must configure) | . | Ustawienie modemu | Speed/range tradeoff | LongFast | . | Limit przeskoków | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Przesunięcie częstotliwości | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Konfiguracja wyświetlacza . | Setting | Opis | . | Wygaszenie ekranu | Time before display sleeps | . | Jednostki wyświetlania | Metric or Imperial | . | Typ ekranu OLED | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Konfiguracja pozycjonowania . | Setting | Opis | . | GPS Enabled | Enable/disable GPS | . | Interwał aktualizacji pozycji GPS | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Inteligentne Pozycjonowanie | Enable movement-based broadcasting | . | Położenie stałe | Use a manually set position | . Konfiguracja zarządzania energią . | Setting | Opis | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Konfiguracja sieci . | Setting | Opis | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Hasło do sieci | . | Serwer NTP | Time synchronization server | . | Syslog Server | Remote logging server | . Konfiguracja Bluetooth . | Setting | Opis | . | Bluetooth Enabled | Enable/disable BLE radio | . | Tryb parowania | Fixed PIN, Random PIN, or No PIN | . | Stały PIN | PIN code for pairing (default: 123456) | . Konfiguracja zabezpieczeń . | Setting | Opis | . | Klucz publiczny | Your node’s public key (read-only) | . | Klucz administratora | Key for remote administration | . | Klucz prywatny | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Klucze zapasowe | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#konfiguracja", + + "relUrl": "/pl-rPL/user/settings-radio-user.html#konfiguracja" + },"4600": { + "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" + },"4601": { + "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" + },"4602": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4603": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Beschrijving | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/settings-radio-user.html#user-settings", + + "relUrl": "/nl-rNL/user/settings-radio-user.html#user-settings" + },"4604": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Apparaat Configuratie . | Setting | Beschrijving | Standaard | . | Functie | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | Alles | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Configuratie . | Setting | Beschrijving | Standaard | . | Regio | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Weergave Configuratie . | Setting | Beschrijving | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Positie Configuratie . | Setting | Beschrijving | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Energie configuratie . | Setting | Beschrijving | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Netwerkconfiguratie . | Setting | Beschrijving | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Configuratie . | Setting | Beschrijving | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Vaste PIN | PIN code for pairing (default: 123456) | . Beveiligings Configuratie . | Setting | Beschrijving | . | Publieke sleutel | Your node’s public key (read-only) | . | Admin Sleutel | Key for remote administration | . | Privésleutel | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Beheerde modus | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", + + "relUrl": "/nl-rNL/user/settings-radio-user.html#configuration" + },"4605": { + "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" + },"4606": { + "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" + },"4607": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "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" + },"4608": { + "doc": "Settings — Radio & User", + "title": "Användarinställningar", + "content": "User Profile . | Setting | Beskrivning | . | Långt namn | Your display name (up to 39 characters) | . | Kort namn | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "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" + },"4609": { + "doc": "Settings — Radio & User", + "title": "Konfiguration", + "content": "Enhetskonfiguration . | Setting | Beskrivning | Förvald | . | Roll | Node behavior (Client, Router, etc.) | Client | . | Återutsändningsläge | How the node retransmits messages | Alla | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Beskrivning | Förvald | . | Region | Regulatory region for frequency bands | Unset (must configure) | . | Modem-förinställningar | Speed/range tradeoff | LongFast | . | Hoppgräns | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frekvensförskjutning | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Beskrivning | . | Tidsgräns för display | Time before display sleeps | . | Enheter | Metric or Imperial | . | OLED-typ | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Beskrivning | . | GPS Enabled | Enable/disable GPS | . | Intervall för GPS-uppdatering | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart position | Enable movement-based broadcasting | . | Fast plats | Use a manually set position | . Ströminställningar . | Setting | Beskrivning | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Beskrivning | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Nätverkslösenord | . | NTP-server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth-inställningar . | Setting | Beskrivning | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fast PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Beskrivning | . | Publik nyckel | Your node’s public key (read-only) | . | Admin-nyckel | Key for remote administration | . | Privat nyckel | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Hanterat läge | Restrict non-admin channel changes | . | Säkerhetskopiera nycklar | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#konfiguration", + + "relUrl": "/sv-rSE/user/settings-radio-user.html#konfiguration" + },"4610": { + "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" + },"4611": { + "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" + },"4612": { + "doc": "設定：無線機とユーザー", + "title": "設定：無線機とユーザー", + "content": "無線機のハードウェアと、ユーザーの識別情報のパラメーターを設定します。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/settings-radio-user.html", + + "relUrl": "/ja-rJP/user/settings-radio-user.html" + },"4613": { + "doc": "設定：無線機とユーザー", + "title": "ユーザー設定", + "content": "ユーザープロファイル . | 設定項目 | 説明 | . | 正式名称 | 表示名（最大 39 文字） | . | 短縮名 | 4 文字の短縮名 | . | 免許を持つ運用者 | アマチュア無線の免許を持っている場合に有効にします（より高い出力が可能になります） | . 変更を適用する . 設定を変更したら、「保存」をタップして構成を無線機に書き込みます。 変更を適用するために、デバイスが再起動することがあります。 . ", + "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#ユーザー設定" + },"4614": { + "doc": "設定：無線機とユーザー", + "title": "設定", + "content": "デバイスの設定 . | 設定項目 | 説明 | デフォルト | . | 役割 | ノードの動作（クライアント、ルーターなど） | クライアント | . | 再ブロードキャストモード | ノードがメッセージを再送信する方法 | すべて | . | ノード情報のブロードキャスト（秒） | ノード情報をブロードキャストする間隔 | 10800 | . | ダブルタップボタン | ボタンをダブルタップしたときの動作 | 無効 | . LoRa設定 . | 設定項目 | 説明 | デフォルト | . | リージョン | 周波数帯の規制リージョン | 未設定（要設定） | . | モデムプリセット | 速度と距離のトレードオフ | LongFast | . | ホップ数上限 | 再送信の最大ホップ数 | 3 | . | 送信出力 | 送信出力（dBm）。0 = リージョンで許可された最大値 | 0（リージョン最大） | . | 周波数オフセット | 周波数の微調整（MHz） | 0 | . | チャンネル帯域幅 | 帯域幅の設定 | プリセットのデフォルト | . ⚠️ 重要： 送信する前に、必ずリージョンを設定する必要があります。 正しいリージョンを設定せずに運用すると、現地の無線規制に違反するおそれがあります。 詳しくは、meshtastic.org の リージョン設定ガイド を参照してください。 . モデムプリセット . 💡 ヒント： 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 | 5.5 kbps | −10 dB | 郊外の短距離。中程度の建物密度 | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | 郊外エリア。中程度の建物密度 | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | 郊外・地方。中程度の距離で低速 | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Long Fast と同程度の距離だが 500 kHz 帯域幅。スループットが速い | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | 一般用途（デフォルト）：距離と速度のバランスが良い | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | 起伏のある地方。ときどき使う用途 | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD 帯（125 kHz 帯域幅）。Medium Fast に相当 | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD 帯（125 kHz 帯域幅）。Long Fast に相当 | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz 帯（62.5 kHz 帯域幅）。他のデバイスとの干渉を避ける | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz 帯（62.5 kHz 帯域幅）。Long Fast に相当 | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります | . ℹ️ 注意： この表では、一般的な短い名前を使用しています。 アプリのプリセットのドロップダウンでは、Short Range - Fast、Long Range - Fast、Lite - Fast、Narrow - Fast のように表示されます。 . モデムプリセットを選ぶ . モデムプリセットは、距離とデータ速度の基本的なトレードオフを制御します： . | 遅いプリセットは拡散をより多く使い、より弱い信号レベルでも復調できるようにします（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 のままにします。これはコミュニティのデフォルトで、地域内の他のユーザーとの互換性を確保します。 | . ⚠️ 重要： 同じチャンネル上のすべてのノードは、同じモデムプリセットを使用する必要があります。 プリセットが一致しないノードは、同じ周波数と暗号化鍵を共有していても通信できません。 . 💡 ヒント： 上記の距離の目安は、平坦な地形と一般的なアンテナを前提としています。 高所（丘の上、屋上）にあると、実効的な距離が大幅に伸びます。 適切に設置された Long Fast のルーターは、地上に置かれた Long Slow のノードを上回ることがよくあります。 . 表示設定 . | 設定項目 | 説明 | . | 画面のタイムアウト | ディスプレイがスリープするまでの時間 | . | 表示単位 | メートル法またはヤード・ポンド法 | . | OLED の種類 | 自動、SSD1306、SH1106、SH1107 | . | コンパスの向き | コンパス表示の回転オフセット（0°、90°、180°、270°） | . | コンパスの北 | ⚠️ 非推奨：コンパスの向きに置き換えられました。古いファームウェアではまだ表示されます | . 位置情報設定 . | 設定項目 | 説明 | . | GPS を有効化 | GPS の有効／無効 | . | GPS の更新間隔 | GPS 測位を取得する頻度 | . | 位置のブロードキャスト（秒） | 位置を共有する頻度 | . | スマート位置 | 移動に基づくブロードキャストを有効化 | . | 固定位置 | 手動で設定した位置を使用 | . 電源設定 . | 設定項目 | 説明 | . | 省電力 | 低電力のスリープモードを有効化 | . | シャットダウンまでの時間（秒） | アイドル時の自動シャットダウンタイマー | . | ADC 倍率 | バッテリー電圧の校正係数 | . | Bluetooth 待機時間（秒） | 起動時に BLE 接続を待つ時間 | . | メッシュ SDS タイムアウト（秒） | スーパーディープスリープのタイムアウト | . ネットワーク設定 . | 設定項目 | 説明 | . | WiFi を有効化 | WiFi 無線を有効化（ESP32 デバイス） | . | WiFi SSID | 接続先のネットワーク名 | . | WiFi PSK | ネットワークのパスワード | . | NTP サーバー | 時刻同期サーバー | . | Syslog サーバー | リモートログサーバー | . Bluetooth 設定 . | 設定項目 | 説明 | . | Bluetooth を有効化 | BLE 無線の有効／無効 | . | ペアリングモード | 固定 PIN、ランダム PIN、または PIN なし | . | 固定 PIN | ペアリング用の PIN コード（デフォルト：123456） | . セキュリティ設定 . | 設定項目 | 説明 | . | 公開鍵 | ノードの公開鍵（読み取り専用） | . | 管理者鍵 | リモート管理用の鍵 | . | 秘密鍵 | ノードの秘密鍵（安全に取り扱ってください） | . | 管理チャンネルを有効化 | ⚠️ 削除されました：管理者キーを設定すると自動的に構成されるようになりました | . | デバッグログ | シリアル／Bluetooth 経由でライブのデバッグログを出力 | . | シリアルを有効化 | シリアルコンソールへのアクセスを有効化（デバイスの設定から移動） | . | 管理モード | 管理者以外によるチャンネル変更を制限 | . | 鍵をバックアップ | ノードの鍵の暗号化されたバックアップを、このデバイスに保存します（Android のみ） | . | 鍵を復元 | バックアップした鍵をノードに書き戻します（バックアップがある場合に利用可能） | . | 鍵のバックアップを削除 | このデバイスに保存されている鍵のバックアップを削除します | . | 保護レベル | パケットの真正性。署名のないパケットや中継されたパケットをどう扱うか：厳格、バランス、互換（対応するファームウェアが必要。厳格は確認を求めます） | . 設定には、標準的な設定コントロール（ドロップダウン、トグル、スライダー）を使用します： . | コントロール | スクリーンショット | . | ドロップダウン | | . | トグル | | . | スライダー | | . ", + "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#設定" + },"4615": { + "doc": "設定：無線機とユーザー", "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", + "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/signal-meter.html#関連トピック" - },"4655": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html", + "relUrl": "/ja-rJP/user/settings-radio-user.html#関連トピック" + },"4616": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/settings-radio-user.html#settings--radio--user", - "relUrl": "/ca-rES/user/signal-meter.html" - },"4656": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "relUrl": "/hu-rHU/user/settings-radio-user.html#settings--radio--user" + },"4617": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Leírás | . | Hosszú név | Your display name (up to 39 characters) | . | Rövid név | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/settings-radio-user.html#user-settings", - "relUrl": "/ca-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4657": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "relUrl": "/hu-rHU/user/settings-radio-user.html#user-settings" + },"4618": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Eszközbeállítások . | Setting | Leírás | Alapértelmezett | . | Szerepkör | Node behavior (Client, Router, etc.) | Kliens | . | Újrasugárzási mód | How the node retransmits messages | Összes | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa beállítások . | Setting | Leírás | Alapértelmezett | . | Régió | Regulatory region for frequency bands | Unset (must configure) | . | Modem-előbeállítás | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Kijelző beállítások . | Setting | Leírás | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Pozíció beállítások . | Setting | Leírás | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Intelligens pozíció | Enable movement-based broadcasting | . | Rögzített pozíció | Use a manually set position | . Energia-beállítások . | Setting | Leírás | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Hálózati beállítások . | Setting | Leírás | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth beállítások . | Setting | Leírás | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Rögzített PIN | PIN code for pairing (default: 123456) | . Biztonsági beállítások . | Setting | Leírás | . | Nyilvános kulcs | Your node’s public key (read-only) | . | Admin kulcs | Key for remote administration | . | Privát kulcs | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Felügyelt mód | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - "relUrl": "/ca-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4658": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/ca-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4659": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/ca-rES/user/signal-meter.html#4-what-this-means-for-you" - },"4660": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4661": { - "doc": "How the Meshtastic Signal Meter Works", + "relUrl": "/hu-rHU/user/settings-radio-user.html#configuration" + },"4619": { + "doc": "Settings — Radio & User", "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", + "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": "/ca-rES/user/signal-meter.html#related-topics" - },"4662": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html", + "relUrl": "/hu-rHU/user/settings-radio-user.html#related-topics" + },"4620": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": " ", + "url": "/Meshtastic-Android/main/hu-rHU/user/settings-radio-user.html", - "relUrl": "/sr-rLatn/user/signal-meter.html" - },"4663": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "relUrl": "/hu-rHU/user/settings-radio-user.html" + },"4621": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/settings-radio-user.html#settings--radio--user", - "relUrl": "/sr-rLatn/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4664": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "relUrl": "/ht-rHT/user/settings-radio-user.html#settings--radio--user" + },"4622": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Deskripsyon | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/settings-radio-user.html#user-settings", - "relUrl": "/sr-rLatn/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4665": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Ниво | Bars | Criteria | Meaning | . | Dobro | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Prihvatljiv | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Loš | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Bez | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "relUrl": "/ht-rHT/user/settings-radio-user.html#user-settings" + },"4623": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | Deskripsyon | Default | . | Role | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Deskripsyon | Default | . | Rejyon | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Deskripsyon | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Deskripsyon | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Deskripsyon | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Deskripsyon | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Deskripsyon | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Deskripsyon | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - "relUrl": "/sr-rLatn/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4666": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/sr-rLatn/user/signal-meter.html#4-what-this-means-for-you" - },"4667": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4668": { - "doc": "How the Meshtastic Signal Meter Works", + "relUrl": "/ht-rHT/user/settings-radio-user.html#configuration" + },"4624": { + "doc": "Settings — Radio & User", "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", + "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": "/sr-rLatn/user/signal-meter.html#related-topics" - },"4669": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html", + "relUrl": "/ht-rHT/user/settings-radio-user.html#related-topics" + },"4625": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": " ", + "url": "/Meshtastic-Android/main/ht-rHT/user/settings-radio-user.html", - "relUrl": "/ko-rKR/user/signal-meter.html" - },"4670": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "relUrl": "/ht-rHT/user/settings-radio-user.html" + },"4626": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "url": "/Meshtastic-Android/main/gl-rES/user/settings-radio-user.html#settings--radio--user", - "relUrl": "/ko-rKR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4671": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "relUrl": "/gl-rES/user/settings-radio-user.html#settings--radio--user" + },"4627": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Descrición | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/gl-rES/user/settings-radio-user.html#user-settings", - "relUrl": "/ko-rKR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4672": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | 좋음 | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | 보통 | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | 나쁨 | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | 없음 | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "relUrl": "/gl-rES/user/settings-radio-user.html#user-settings" + },"4628": { + "doc": "Settings — Radio & User", + "title": "Configuration", + "content": "Device Config . | Setting | Descrición | Default | . | Role | Node behavior (Client, Router, etc.) | Cliente | . | Rebroadcast Mode | How the node retransmits messages | All | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Config . | Setting | Descrición | Default | . | Rexión | Regulatory region for frequency bands | Unset (must configure) | . | Modem Preset | Speed/range tradeoff | LongFast | . | Hop Limit | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . | Setting | Descrición | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Type | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Position Config . | Setting | Descrición | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Power Config . | Setting | Descrición | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Network Config . | Setting | Descrición | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Network password | . | NTP Server | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Config . | Setting | Descrición | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing (default: 123456) | . Security Config . | Setting | Descrición | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Key for remote administration | . | Private Key | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Managed Mode | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuration", - "relUrl": "/ko-rKR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4673": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/ko-rKR/user/signal-meter.html#4-what-this-means-for-you" - },"4674": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4675": { - "doc": "How the Meshtastic Signal Meter Works", + "relUrl": "/gl-rES/user/settings-radio-user.html#configuration" + },"4629": { + "doc": "Settings — Radio & User", "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", + "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": "/ko-rKR/user/signal-meter.html#related-topics" - },"4676": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html", + "relUrl": "/gl-rES/user/settings-radio-user.html#related-topics" + },"4630": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": " ", + "url": "/Meshtastic-Android/main/gl-rES/user/settings-radio-user.html", - "relUrl": "/ro-rRO/user/signal-meter.html" - },"4677": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "relUrl": "/gl-rES/user/settings-radio-user.html" + },"4631": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/settings-radio-user.html#settings--radio--user", - "relUrl": "/ro-rRO/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4678": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "relUrl": "/tr-rTR/user/settings-radio-user.html#settings--radio--user" + },"4632": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Açıklaması | . | Uzun Ad | Your display name (up to 39 characters) | . | Kısa Ad | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/settings-radio-user.html#user-settings", - "relUrl": "/ro-rRO/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4679": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bun | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Acceptabil | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Slab | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Niciunul | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "relUrl": "/tr-rTR/user/settings-radio-user.html#user-settings" + },"4633": { + "doc": "Settings — Radio & User", + "title": "Yapılandırma", + "content": "Cihaz Ayarı . | Setting | Açıklaması | Varsayılan | . | Rol | Node behavior (Client, Router, etc.) | Client | . | Rebroadcast Mode | How the node retransmits messages | Hepsi | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . LoRa Ayarı . | Setting | Açıklaması | Varsayılan | . | Bölge | Regulatory region for frequency bands | Unset (must configure) | . | Modem Ön Ayarı | Speed/range tradeoff | LongFast | . | Hop Limiti | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Offset | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Akran Ayarı . | Setting | Açıklaması | . | Screen Timeout | Time before display sleeps | . | Display Units | Metric or Imperial | . | OLED Tipi | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Konum Ayarı . | Setting | Açıklaması | . | GPS Enabled | Enable/disable GPS | . | GPS Update Interval | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Smart Position | Enable movement-based broadcasting | . | Fixed Position | Use a manually set position | . Güç Ayarı . | Setting | Açıklaması | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Ağ Ayarı . | Setting | Açıklaması | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Ağ şifresi | . | NTP Sunucusu | Time synchronization server | . | Syslog Server | Remote logging server | . Bluetooth Ayarı . | Setting | Açıklaması | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Sabit PIN | PIN code for pairing (default: 123456) | . Güvenlik Ayarı . | Setting | Açıklaması | . | Genel Anahtar | Your node’s public key (read-only) | . | Yönetici Anahtarı | Key for remote administration | . | Özel Anahtar | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Yönetilen Mod | Restrict non-admin channel changes | . | Anahtarları Yedekle | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#yap%C4%B1land%C4%B1rma", - "relUrl": "/ro-rRO/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4680": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/ro-rRO/user/signal-meter.html#4-what-this-means-for-you" - },"4681": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4682": { - "doc": "How the Meshtastic Signal Meter Works", + "relUrl": "/tr-rTR/user/settings-radio-user.html#yapılandırma" + },"4634": { + "doc": "Settings — Radio & User", "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", + "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": "/ro-rRO/user/signal-meter.html#related-topics" - },"4683": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html", + "relUrl": "/tr-rTR/user/settings-radio-user.html#related-topics" + },"4635": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": " ", + "url": "/Meshtastic-Android/main/tr-rTR/user/settings-radio-user.html", - "relUrl": "/ga-rIE/user/signal-meter.html" - },"4684": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "relUrl": "/tr-rTR/user/settings-radio-user.html" + },"4636": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": "Configure your radio hardware and user identity parameters. ", + "url": "/Meshtastic-Android/main/es-rES/user/settings-radio-user.html#settings--radio--user", - "relUrl": "/ga-rIE/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4685": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "relUrl": "/es-rES/user/settings-radio-user.html#settings--radio--user" + },"4637": { + "doc": "Settings — Radio & User", + "title": "User Settings", + "content": "User Profile . | Setting | Descripción | . | Nombre largo | Your display name (up to 39 characters) | . | Nombre Corto | 4-character abbreviated name | . | Licensed Operator | Enable if you hold an amateur radio license (enables higher power) | . Applying Changes . After modifying settings, tap Save to write the configuration to your radio. The device may reboot to apply changes. ", + "url": "/Meshtastic-Android/main/es-rES/user/settings-radio-user.html#user-settings", - "relUrl": "/ga-rIE/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4686": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Maith | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Ceart go leor | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Go dona | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Ní dhéanfaidh sé | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "relUrl": "/es-rES/user/settings-radio-user.html#user-settings" + },"4638": { + "doc": "Settings — Radio & User", + "title": "Configuración", + "content": "Configuración del dispositivo . | Setting | Descripción | Por defecto | . | Rol | Node behavior (Client, Router, etc.) | Cliente | . | Modo de retransmisión | How the node retransmits messages | Todos | . | Node Info Broadcast (s) | Interval for broadcasting node info | 10800 | . | Double-tap Button | Action for double-tap button press | Disabled | . Configuración LoRa . | Setting | Descripción | Por defecto | . | Región | Regulatory region for frequency bands | Unset (must configure) | . | Modem predefinido | Speed/range tradeoff | LongFast | . | Límite de Saltos | Maximum retransmit hops | 3 | . | TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Desplazamiento de frecuencia | Fine-tune frequency (MHz) | 0 | . | Channel Bandwidth | Bandwidth setting | Default for preset | . ⚠️ Important: You must set your region before transmitting. Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem Presets . 💡 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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 5.5 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.1 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 4.4 kbps | −12.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 5.5 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 1.1 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Long Slow | ~30 km | 0.18 kbps | −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. In the app’s preset dropdown they read as Short Range - Fast, Long Range - Fast, Lite - Fast, Narrow - Fast, and so on. Choosing a Modem Preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . ⚠️ Important: All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key. 💡 Tip: The range estimates above assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuración de pantalla . | Setting | Descripción | . | Tiempo de espera de la pantalla | Time before display sleeps | . | Unidades de medidas | Metric or Imperial | . | Tipo de OLED | Auto, SSD1306, SH1106, SH1107 | . | Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) | . | Compass North | ⚠️ Deprecated — replaced by Compass Orientation; still visible in older firmware | . Configuración de la posición . | Setting | Descripción | . | GPS Enabled | Enable/disable GPS | . | Intervalo de actualización GPS | How often to acquire GPS fix | . | Position Broadcast (s) | How often to share position | . | Ubicación inteligente | Enable movement-based broadcasting | . | Posición fija | Use a manually set position | . Configuración de elecenergía . | Setting | Descripción | . | Power Saving | Enable low-power sleep mode | . | Shutdown After (s) | Auto-shutdown idle timer | . | ADC Multiplier | Battery voltage calibration factor | . | Wait Bluetooth (s) | Time to wait for BLE connection at boot | . | Mesh SDS Timeout (s) | Super-deep-sleep timeout | . Configuración de la red . | Setting | Descripción | . | WiFi Enabled | Enable WiFi radio (ESP32 devices) | . | WiFi SSID | Network name to connect to | . | WiFi PSK | Contraseña de red | . | Servidor NTP | Time synchronization server | . | Syslog Server | Remote logging server | . Configuración Bluetooth . | Setting | Descripción | . | Bluetooth Enabled | Enable/disable BLE radio | . | Pairing Mode | Fixed PIN, Random PIN, or No PIN | . | Pin fijo | PIN code for pairing (default: 123456) | . Configuración de la seguridad . | Setting | Descripción | . | Clave Pública | Your node’s public key (read-only) | . | Contraseña de administrador | Key for remote administration | . | Clave privada | Your node’s private key (handle securely) | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Debug Log | Output live debug logging over serial/bluetooth | . | Serial Enabled | Enable serial console access (moved from Device Config) | . | Modo “ya terminado de configurar” | Restrict non-admin channel changes | . | Backup Keys | Save an encrypted backup of the node’s keys on this device (Android only) | . | 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 device | . | Protection Level | Packet authenticity — how unsigned or relayed packets are treated: Strict, Balanced, or Compatible (requires supporting firmware; Strict asks for confirmation) | . 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#configuraci%C3%B3n", - "relUrl": "/ga-rIE/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4687": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/ga-rIE/user/signal-meter.html#4-what-this-means-for-you" - },"4688": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4689": { - "doc": "How the Meshtastic Signal Meter Works", + "relUrl": "/es-rES/user/settings-radio-user.html#configuración" + },"4639": { + "doc": "Settings — Radio & User", "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", + "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": "/ga-rIE/user/signal-meter.html#related-topics" - },"4690": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html", + "relUrl": "/es-rES/user/settings-radio-user.html#related-topics" + },"4640": { + "doc": "Settings — Radio & User", + "title": "Settings — Radio & User", + "content": " ", + "url": "/Meshtastic-Android/main/es-rES/user/settings-radio-user.html", - "relUrl": "/iw-rIL/user/signal-meter.html" - },"4691": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/iw-rIL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4692": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/iw-rIL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4693": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/iw-rIL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4694": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/iw-rIL/user/signal-meter.html#4-what-this-means-for-you" - },"4695": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4696": { - "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" - },"4697": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html", - - "relUrl": "/sv-rSE/user/signal-meter.html" - },"4698": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/sv-rSE/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4699": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/sv-rSE/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4700": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bra | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Ok | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Dålig | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Ingen | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/sv-rSE/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4701": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/sv-rSE/user/signal-meter.html#4-what-this-means-for-you" - },"4702": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4703": { - "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" - },"4704": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html", - - "relUrl": "/ht-rHT/user/signal-meter.html" - },"4705": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/ht-rHT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4706": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/ht-rHT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4707": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bon | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Mwayen | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Move | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Pa gen | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/ht-rHT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4708": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/ht-rHT/user/signal-meter.html#4-what-this-means-for-you" - },"4709": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4710": { - "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" - },"4711": { - "doc": "Kuinka Meshtastic-signaalimittari toimii", - "title": "Kuinka Meshtastic-signaalimittari toimii", - "content": "Meshtasticin signaalimittari — sovelluksessa näkyvät tutut palkit tai tilan väri — lasketaan hyvin eri tavalla kuin perinteisen matkapuhelimen tai WiFi-reitittimen “palkit”. Useimmat kuluttajalaitteet mittaavat yksinkertaisesti signaalin “voimakkuutta”. Koska Meshtastic käyttää LoRa (Long Range) -teknologiaa, signaalimittari arvioi sen sijaan kuinka “selkeä” signaali on suhteessa käytössä olevan mesh-verkon asetuksiin. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html", - - "relUrl": "/fi-rFI/user/signal-meter.html" - },"4712": { - "doc": "Kuinka Meshtastic-signaalimittari toimii", - "title": "1. Kaksi mittaria: “voimakkuus” vs “selkeys”", - "content": "Aina kun LoRa-radio vastaanottaa viestin, se raportoi kaksi arvoa: . | RSSI (Received Signal Strength Indicator): kuinka “voimakas” antenniin saapuva signaali on. | SNR (Signal-to-Noise Ratio): kuinka “selkeä” signaali on suhteessa taustakohinaan. | . 💡 Vinkki: Ajattele asiaa näin — yrität kuulla ystäväsi puhetta. | RSSI on kuinka kovaa hän puhuu. | Melutaso (Noise Floor) on huoneen taustahäly (ilmastointi, muut ihmiset, liikenne). | SNR on se, kuinka hyvin erotat ystäväsi äänen taustamelusta. | . Jos ystäväsi huutaa rock-konsertissa, signaali on erittäin voimakas (korkea RSSI), mutta et silti ymmärrä häntä, koska kohina on liian suuri (huono SNR). Toisaalta, jos hän kuiskaa hiljaisessa kirjastossa, signaali voi olla heikko (matala RSSI), mutta ymmärrät silti hyvin (hyvä SNR). ", - "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#1-kaksi-mittaria-voimakkuus-vs-selkeys", - - "relUrl": "/fi-rFI/user/signal-meter.html#1-kaksi-mittaria-voimakkuus-vs-selkeys" - },"4713": { - "doc": "Kuinka Meshtastic-signaalimittari toimii", - "title": "2. LoRa:n “taika”: kuuleminen kohinan alta", - "content": "Tavallisessa radiossa (kuten FM- tai WiFi-yhteydessä), jos taustakohina on voimakkaampi kuin signaali (negatiivinen SNR), vastaanotin kuulee vain kohinaa. LoRa on erilainen. Se käyttää hajaspektritekniikkaa (Spread Spectrum), joka mahdollistaa signaalin erottamisen myös silloin, kun se on taustakohinan alla. Siksi Meshtasticissa näkyy usein negatiivisia SNR-arvoja (esim. -10 dB tarkoittaa, että signaali on 10 dB heikompi kuin kohina). Riippuen siitä, mitä Meshtastic-esiasetusta käytät (esim. “LongFast” vs. “ShortFast”), radiolla on tietty SNR-raja — eli suurin määrä kohinaa, jonka se kestää ennen kuin viesti alkaa kadota täysin kohinaan. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#2-loran-taika-kuuleminen-kohinan-alta", - - "relUrl": "/fi-rFI/user/signal-meter.html#2-loran-taika-kuuleminen-kohinan-alta" - },"4714": { - "doc": "Kuinka Meshtastic-signaalimittari toimii", - "title": "3. Kuinka signaalimittari laskee laadun", - "content": "Sovellus arvioi signaalin laadun (Ei, Huono, Kohtalainen tai Hyvä) pelkästään SNR-arvon perusteella, suhteessa esiasetuksen SNR-rajaan — eli demodulaation alarajaan, joka on kuvattu aiemmin. Se ei tarkoituksella ota RSSI-arvoa huomioon arvioinnissa: ilman paikallista kohinatasoa RSSI ei kerro, voidaanko signaali todella purkaa, joten SNR suhteessa esiasetuksen rajaan on merkityksellinen mittari. (RSSI näytetään edelleen muualla sovelluksessa.) . Koska arviointi perustuu esiasetuksen rajaan, sama SNR-arvo voi saada eri arvosanan eri esiasetuksilla — esimerkiksi -15 dB on hyvä arvo LongSlow-esiasetuksella, mutta käyttökelvoton ShortFast-esiasetuksella. Jos “raja” tarkoittaa käytössä olevan esiasetuksen SNR-rajaa, sovellus määrittää palkit (tai värin) seuraavasti: . | Taso | Palkit | Kriteerit | Merkitys | . | Hyvä | 3 | SNR esiasetuksen rajan yläpuolella | Signaali on selvästi demodulaation alarajan yläpuolella — hyvä yhteys. | . | Kohtalainen | 2 | alle 5,5 dB rajan alapuolella | Signaali voidaan vielä purkaa, mutta se on lähellä demodulaation alarajaa. | . | Huono | 1 | 5,5–7,5 dB rajan alapuolella | Signaali on aivan esiasetuksen palautumiskyvyn rajalla. | . | ei mitään | 0 | yli 7,5 dB “rajan” alapuolella | Signaali on demodulaation alarajan alapuolella — lähetys hukkuu kohinaan. | . Huomautus: Kiinteitä SNR-rajoja, joita olet ehkä nähnyt muualla (−7 dB / −15 dB), käytetään nykyisin vain traceroute-tulosten yksittäisten hyppyjen väritykseen — ei radion yleisen signaalin laadun arviointiin. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#3-kuinka-signaalimittari-laskee-laadun", - - "relUrl": "/fi-rFI/user/signal-meter.html#3-kuinka-signaalimittari-laskee-laadun" - },"4715": { - "doc": "Kuinka Meshtastic-signaalimittari toimii", - "title": "4. Mitä tämä tarkoittaa sinulle", - "content": "Koska Meshtasticin mittari toimii enemmän selkeysmittarina, se käyttäytyy eri tavalla kuin useimmat odottavat: . 💡 Vinkki: Älä huolestu matalasta RSSI-arvosta. Saatat nähdä näennäisesti erittäin huonon RSSI-arvon, kuten -118 dBm. Tavallisessa puhelimessa tämä tarkoittaisi käytännössä nollakenttää. Mutta jos SNR on esimerkiksi +2 dB, Meshtastic voi silti näyttää vahvaa signaalia! Kirjasto on hiljainen, joten kuiskaus kuuluu täydellisesti. ⚠️ Varoitus: Kiinnitä huomiota paikalliseen kohinaan. Jos liität suuren antennin ja näet hyvän RSSI-arvon (esim. -90 dBm), mutta signaalimittari näyttää silti vain 1 palkin (Huono), yhteydessä on ongelma. Se tarkoittaa paikallista häiriötä — esimerkiksi halpa virtalähde, kohiseva elektroniikka tai lähellä oleva radiolähetin voi luoda niin paljon kohinaa, että se peittää mesh-verkon. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#4-mit%C3%A4-t%C3%A4m%C3%A4-tarkoittaa-sinulle", - - "relUrl": "/fi-rFI/user/signal-meter.html#4-mitä-tämä-tarkoittaa-sinulle" - },"4716": { - "doc": "Kuinka Meshtastic-signaalimittari toimii", - "title": "Missä signaalitieto näkyy", - "content": "Sovelluksessa signaalidata näkyy useissa paikoissa: . | Radiolista — signaalipalkki jokaisen radion vieressä | Radion tiedot — SNR, RSSI ja signaalin laatu laitteen mittareissa | Reitinselvitys — signaalin laatu jokaisessa välivaiheessa jokaiselle välittävälle radiolle | Signaalimittarit — historiallinen SNR- ja RSSI-data mittauskaavioissa | . ", - "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" - },"4717": { - "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" - },"4718": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html", - - "relUrl": "/gl-rES/user/signal-meter.html" - },"4719": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/gl-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4720": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/gl-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4721": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/gl-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4722": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/gl-rES/user/signal-meter.html#4-what-this-means-for-you" - },"4723": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4724": { - "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" - },"4725": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html", - - "relUrl": "/uk-rUA/user/signal-meter.html" - },"4726": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/uk-rUA/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4727": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/uk-rUA/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4728": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Хороший | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Задовільний | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Поганий | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Жоден | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/uk-rUA/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4729": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/uk-rUA/user/signal-meter.html#4-what-this-means-for-you" - },"4730": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4731": { - "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" - },"4732": { + "relUrl": "/es-rES/user/settings-radio-user.html" + },"4641": { "doc": "Wie das Meshtastic Signal Meter funktioniert", "title": "Wie das Meshtastic Signal Meter funktioniert", "content": "Die Meshtastic-Signalanzeige – die vertrauten Balken oder die Statusfarbe in der App – wird ganz anders berechnet als die „Balken“ bei einem herkömmlichen Mobiltelefon oder WLAN-Router. Die meisten Endgeräte messen einfach, wie “laut” ein Signal ist. Da Meshtastic jedoch die LoRa Technologie (Long Range) verwendet, misst die Signalanzeige, wie klar das Signal ist – und zwar im Verhältnis zu den spezifischen Einstellungen, die in Ihrem Mesh-Netzwerk genutzt werden. ", "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html", "relUrl": "/de-rDE/user/signal-meter.html" - },"4733": { + },"4642": { "doc": "Wie das Meshtastic Signal Meter funktioniert", "title": "1. Die beiden Metriken: “Lautstärke” vs. “Klarheit”", "content": "Jedes Mal, wenn der LoRa Chip eine Nachricht empfängt, meldet er zwei Messwerte: . | RSSI (Received Signal Stength Indicator): die Lautstärke der rohen Energie, die deine Antenne trifft. | SNR (Signal-to-Noise Ratio) Die Klarheit des Signals im Vergleich zum Hintergrundrauschen. | . Tipp: Hier ist eine Analogie - stell dir vor, du versuchst einen Freund zu hören, der mit dir redet. | RSSI ist wie laut seine Stimme ist. | Der Rauschboden ist der Hintergrundlärm im Raum (Klimaanlage, andere sprechende Personen, Verkehr). | SNR ist wie einfach du die Stimme deines Freundes vom Hintergrundlärm unterscheiden kannst. | . Wenn dich ein Freund auf einem ohrenbetäubend lauten Rockkonzert anschreit, ist das Signal zwar extrem stark (hoher RSSI), aber du kannst ihn trotzdem nicht verstehen, weil die Hintergrundgeräusche lauter sind (schlechter Signal-Rauschabstand). Umgekehrt, wenn dein Freund dir etwas in einer todstillen Bibliothek zuflüstert, ist das Signal sehr schwach (geringer RSSI), aber du kannst ihn perfekt verstehen (Guter SNR). ", "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html#1-die-beiden-metriken-lautst%C3%A4rke-vs-klarheit", "relUrl": "/de-rDE/user/signal-meter.html#1-die-beiden-metriken-lautstärke-vs-klarheit" - },"4734": { + },"4643": { "doc": "Wie das Meshtastic Signal Meter funktioniert", "title": "2. Die Magie von LoRa: Empfangen “Unter dem Lärmboden”", "content": "Für standard Radios (wie FM oder WLAN) gilt, wenn das Hintergrundrauschen lauter ist, als das Signal (ein negativer SNR), hört der Empfänger nur Rauschen. LoRa ist speziell. Es nutzt die „Spread-Spectrum“-Modulation, die es dem Funkgerät ermöglicht, ein Signal mathematisch aus der Luft zu extrahieren, selbst wenn es tief unterhalb des Hintergrundrauschens liegt. Das ist der Grund weshalb du häufig negative SNR Werte (z.B. -10 dB, was bedeutet, dass das Signal 10 Dezibel schwächer ist, als das Hintergrundrauschen) in Meshtastic sehen wirst. Je nachdem, welche Meshtastic Voreinstellung Sie verwenden (z. B. LongFast vs. ShortFast), weist das Funkgerät einen spezifischen Signal-Rauschabstand Grenzwert auf – das absolute Maximum an Rauschen, das es tolerieren kann, bevor die Nachricht im Rauschen vollständig verloren geht. ", "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html#2-die-magie-von-lora-empfangen-unter-dem-l%C3%A4rmboden", "relUrl": "/de-rDE/user/signal-meter.html#2-die-magie-von-lora-empfangen-unter-dem-lärmboden" - },"4735": { + },"4644": { "doc": "Wie das Meshtastic Signal Meter funktioniert", "title": "3. Wie das Signal Meter die Qualität berechnet", "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. Der RSSI Wert wird bei der Bewertung bewusst nicht berücksichtigt: Ohne Kenntnis des lokalen Grundrauschens lässt sich anhand des RSSI nicht feststellen, ob ein Signal tatsächlich dekodierbar ist; daher ist das Verhältnis des Signal-Rauschabstandes zum festgelegten Grenzwert die aussagekräftige Messgröße. (RSSI is still displayed to you elsewhere.) . Da die Bewertung relativ zum voreingestellten Grenzwert erfolgt, kann derselbe Signal-Rauschabstand je nach Voreinstellung unterschiedlich bewertet werden: -15 dB gelten bei LongSlow als guter Wert, sind jedoch bei ShortFast unbrauchbar. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Niveau | Balken | Kriterium | Bedeutung | . | Gut | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Ordentliche Signalstärke | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Schlecht | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Keins | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Hinweis: Die festen Schwellenwerte des Signal-Rauschabstandes, die Sie möglicherweise an anderer Stelle gesehen haben (-7 dB / -15 dB), werden mittlerweile nur noch zur farblichen Kennzeichnung einzelner Sprünge in Traceroute Ergebnissen verwendet – nicht für die hier beschriebene Signalstärkeanzeige pro Knoten. ", "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html#3-wie-das-signal-meter-die-qualit%C3%A4t-berechnet", "relUrl": "/de-rDE/user/signal-meter.html#3-wie-das-signal-meter-die-qualität-berechnet" - },"4736": { + },"4645": { "doc": "Wie das Meshtastic Signal Meter funktioniert", "title": "4. Was das für dich bedeutet", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. Mit einem Handy hättest du Null Balken. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. Das bedeutet, dass lokale Störquellen vorliegen – etwa ein billiges Netzteil, ein störender Computer oder ein nahegelegener Funkturm –, die so starkes Rauschen erzeugen, dass sie Ihr Netzwerk überlagern. ", "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html#4-was-das-f%C3%BCr-dich-bedeutet", "relUrl": "/de-rDE/user/signal-meter.html#4-was-das-für-dich-bedeutet" - },"4737": { + },"4646": { "doc": "Wie das Meshtastic Signal Meter funktioniert", "title": "Where Signal Information Appears", "content": "In der App werden Signaldaten an mehreren Orten angezeigt: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", "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" - },"4738": { + },"4647": { "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" - },"4739": { + },"4648": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html", + "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html", - "relUrl": "/hr-rHR/user/signal-meter.html" - },"4740": { + "relUrl": "/ca-rES/user/signal-meter.html" + },"4649": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/hr-rHR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4741": { + "relUrl": "/ca-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4650": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/hr-rHR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4742": { + "relUrl": "/ca-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4651": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/hr-rHR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4743": { + "relUrl": "/ca-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4652": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/hr-rHR/user/signal-meter.html#4-what-this-means-for-you" - },"4744": { + "relUrl": "/ca-rES/user/signal-meter.html#4-what-this-means-for-you" + },"4653": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/hr-rHR/user/signal-meter.html#where-signal-information-appears" - },"4745": { + "relUrl": "/ca-rES/user/signal-meter.html#where-signal-information-appears" + },"4654": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#related-topics", - "relUrl": "/hr-rHR/user/signal-meter.html#related-topics" - },"4746": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html", - - "relUrl": "/lt-rLT/user/signal-meter.html" - },"4747": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/lt-rLT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4748": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/lt-rLT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4749": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Geras | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Pakankamas | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Silpnas | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Nėra | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/lt-rLT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4750": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/lt-rLT/user/signal-meter.html#4-what-this-means-for-you" - },"4751": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4752": { - "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" - },"4753": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/en/user/signal-meter.html", - - "relUrl": "/en/user/signal-meter.html" - },"4754": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/en/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/en/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4755": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/en/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/en/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4756": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/en/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/en/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4757": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/en/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/en/user/signal-meter.html#4-what-this-means-for-you" - },"4758": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/en/user/signal-meter.html#where-signal-information-appears", - - "relUrl": "/en/user/signal-meter.html#where-signal-information-appears" - },"4759": { - "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" - },"4760": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html", - - "relUrl": "/hu-rHU/user/signal-meter.html" - },"4761": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/hu-rHU/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4762": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/hu-rHU/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4763": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Jó | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Megfelelő | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Rossz | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Semmi | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/hu-rHU/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4764": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/hu-rHU/user/signal-meter.html#4-what-this-means-for-you" - },"4765": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4766": { - "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" - },"4767": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html", - - "relUrl": "/bg-rBG/user/signal-meter.html" - },"4768": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/bg-rBG/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4769": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/bg-rBG/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4770": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Добър | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Задоволителен | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Лош | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Няма | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/bg-rBG/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4771": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/bg-rBG/user/signal-meter.html#4-what-this-means-for-you" - },"4772": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4773": { - "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" - },"4774": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html", - - "relUrl": "/sl-rSI/user/signal-meter.html" - },"4775": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/sl-rSI/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4776": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/sl-rSI/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4777": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Dober | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Precejšen | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Slab | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Brez | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/sl-rSI/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4778": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/sl-rSI/user/signal-meter.html#4-what-this-means-for-you" - },"4779": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4780": { - "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" - },"4781": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html", - - "relUrl": "/pt-rPT/user/signal-meter.html" - },"4782": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/pt-rPT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4783": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/pt-rPT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4784": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bom | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Razoável | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Mau | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Nenhum | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/pt-rPT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4785": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/pt-rPT/user/signal-meter.html#4-what-this-means-for-you" - },"4786": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4787": { - "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" - },"4788": { + "relUrl": "/ca-rES/user/signal-meter.html#related-topics" + },"4655": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html", "relUrl": "/be-rBY/user/signal-meter.html" - },"4789": { + },"4656": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", "relUrl": "/be-rBY/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4790": { + },"4657": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", "relUrl": "/be-rBY/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4791": { + },"4658": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Нічога | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", "relUrl": "/be-rBY/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4792": { + },"4659": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html#4-what-this-means-for-you", "relUrl": "/be-rBY/user/signal-meter.html#4-what-this-means-for-you" - },"4793": { + },"4660": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", "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" - },"4794": { + },"4661": { "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" - },"4795": { + },"4662": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html", + + "relUrl": "/uk-rUA/user/signal-meter.html" + },"4663": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/uk-rUA/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4664": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/uk-rUA/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4665": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Хороший | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Задовільний | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Поганий | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Жоден | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/uk-rUA/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4666": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/uk-rUA/user/signal-meter.html#4-what-this-means-for-you" + },"4667": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4668": { + "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" + },"4669": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html", + + "relUrl": "/zh-rCN/user/signal-meter.html" + },"4670": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/zh-rCN/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4671": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/zh-rCN/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4672": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | 良好 | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | 一般 | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | 差 | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | 无 | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/zh-rCN/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4673": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/zh-rCN/user/signal-meter.html#4-what-this-means-for-you" + },"4674": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4675": { + "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" + },"4676": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html", + + "relUrl": "/bg-rBG/user/signal-meter.html" + },"4677": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/bg-rBG/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4678": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/bg-rBG/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4679": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Добър | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Задоволителен | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Лош | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Няма | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/bg-rBG/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4680": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/bg-rBG/user/signal-meter.html#4-what-this-means-for-you" + },"4681": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4682": { + "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" + },"4683": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html", + + "relUrl": "/zh-rTW/user/signal-meter.html" + },"4684": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. Meshtastic is an open source, decentralized, off-grid, privacy-respecting, encrypted communications platform built on affordable, readily available hardware. It enables you and your friends to communicate securely with text messages, share locations, and more over long ranges.", + "content": ". | It’s built on top of a software defined radio platform called LoRa, enabling inexpensive radios (based on popular chips like the ESP32, nRF52, and RP2040) to operate as long range, low power, and secure communicators. | Common hardware includes devices like the RAK WisBlock series, T-Beam, Heltec, and LilyGo boards. | Meshtastic supports communication over several radio channels, allowing you to separate traffic or experiment with different settings. You can configure parameters like the spreading factor, bandwidth, and coding rate to optimize for range, data rate, and reliability. These settings are often referred to as radio profiles, with common examples being “Long Fast” or “Mid Slow”. | Besides LoRa, Meshtastic devices can also communicate using BLE for short-range communication with smartphones and other devices. | Meshtastic devices can be configured using a variety of methods, including: . | A mobile app (available for Android and iOS) | A web-based interface | A CLI | An API | . | Meshtastic can also be integrated with other systems using protocols like MQTT. | You can extend the functionality of Meshtastic devices by writing your own firmware or connecting external sensors and devices using the GPIO, USB, UART, SPI, and I2C interfaces. | Meshtastic devices can be powered by batteries, USB, or other power sources. | Meshtastic supports Over-The-Air (OTA) firmware updates via LoRa, WiFi or Bluetooth. | Meshtastic allows for end-to-end encryption of messages. | Meshtastic devices can act as repeaters, extending the range of the network. The Two Metrics: “Loudness” vs. “Clarity” | . Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#1-meshtastic-is-an-open-source-decentralized-off-grid-privacy-respecting-encrypted-communications-platform-built-on-affordable-readily-available-hardware-it-enables-you-and-your-friends-to-communicate-securely-with-text-messages-share-locations-and-more-over-long-ranges", + + "relUrl": "/zh-rTW/user/signal-meter.html#1-meshtastic-is-an-open-source-decentralized-off-grid-privacy-respecting-encrypted-communications-platform-built-on-affordable-readily-available-hardware-it-enables-you-and-your-friends-to-communicate-securely-with-text-messages-share-locations-and-more-over-long-ranges" + },"4685": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/zh-rTW/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4686": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | —– | ————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————– | ————————————– | —————————————————————————————- | 良好 | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | 普通 | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | 不良 | 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/) | `5.5 dB` to `7.5 dB` below the `limit` | At the very edge of what the preset can recover. | 無 | 0 | more than `7.5 dB` below the `limit` | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/zh-rTW/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4687": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/zh-rTW/user/signal-meter.html#4-what-this-means-for-you" + },"4688": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4689": { + "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#相關主題" + },"4690": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html", + + "relUrl": "/sr-rLatn/user/signal-meter.html" + },"4691": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/sr-rLatn/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4692": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/sr-rLatn/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4693": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Ниво | Bars | Criteria | Meaning | . | Dobro | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Prihvatljiv | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Loš | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Bez | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/sr-rLatn/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4694": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/sr-rLatn/user/signal-meter.html#4-what-this-means-for-you" + },"4695": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4696": { + "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" + },"4697": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html", + + "relUrl": "/cs-rCZ/user/signal-meter.html" + },"4698": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/cs-rCZ/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4699": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/cs-rCZ/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4700": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Silný | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Slabý | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Špatný | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Žádný | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/cs-rCZ/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4701": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/cs-rCZ/user/signal-meter.html#4-what-this-means-for-you" + },"4702": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4703": { + "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" + },"4704": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/en/user/signal-meter.html", + + "relUrl": "/en/user/signal-meter.html" + },"4705": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/en/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/en/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4706": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/en/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/en/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4707": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/en/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/en/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4708": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/en/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/en/user/signal-meter.html#4-what-this-means-for-you" + },"4709": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "url": "/Meshtastic-Android/main/en/user/signal-meter.html#where-signal-information-appears", + + "relUrl": "/en/user/signal-meter.html#where-signal-information-appears" + },"4710": { + "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" + },"4711": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html", + + "relUrl": "/sl-rSI/user/signal-meter.html" + },"4712": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/sl-rSI/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4713": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/sl-rSI/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4714": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Dober | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Precejšen | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Slab | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Brez | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/sl-rSI/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4715": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/sl-rSI/user/signal-meter.html#4-what-this-means-for-you" + },"4716": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4717": { + "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" + },"4718": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html", + + "relUrl": "/it-rIT/user/signal-meter.html" + },"4719": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/it-rIT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4720": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/it-rIT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4721": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Buono | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Discreto | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Scarso | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Nessuno | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/it-rIT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4722": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/it-rIT/user/signal-meter.html#4-what-this-means-for-you" + },"4723": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4724": { + "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" + },"4725": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html", "relUrl": "/pt-rBR/user/signal-meter.html" - },"4796": { + },"4726": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", "relUrl": "/pt-rBR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4797": { + },"4727": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", "relUrl": "/pt-rBR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4798": { + },"4728": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bom | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Média | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Ruim | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Nenhum | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", "relUrl": "/pt-rBR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4799": { + },"4729": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html#4-what-this-means-for-you", "relUrl": "/pt-rBR/user/signal-meter.html#4-what-this-means-for-you" - },"4800": { + },"4730": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", "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" - },"4801": { + },"4731": { "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" - },"4802": { + },"4732": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html", + "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html", - "relUrl": "/el-rGR/user/signal-meter.html" - },"4803": { + "relUrl": "/is-rIS/user/signal-meter.html" + },"4733": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/el-rGR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4804": { + "relUrl": "/is-rIS/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4734": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/el-rGR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4805": { + "relUrl": "/is-rIS/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4735": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/el-rGR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4806": { + "relUrl": "/is-rIS/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4736": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/el-rGR/user/signal-meter.html#4-what-this-means-for-you" - },"4807": { + "relUrl": "/is-rIS/user/signal-meter.html#4-what-this-means-for-you" + },"4737": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/el-rGR/user/signal-meter.html#where-signal-information-appears" - },"4808": { + "relUrl": "/is-rIS/user/signal-meter.html#where-signal-information-appears" + },"4738": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#related-topics", - "relUrl": "/el-rGR/user/signal-meter.html#related-topics" - },"4809": { + "relUrl": "/is-rIS/user/signal-meter.html#related-topics" + },"4739": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html", + "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html", - "relUrl": "/es-rES/user/signal-meter.html" - },"4810": { + "relUrl": "/fr-rFR/user/signal-meter.html" + },"4740": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/es-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4811": { + "relUrl": "/fr-rFR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4741": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/es-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4812": { + "relUrl": "/fr-rFR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4742": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bien | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Aceptable | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Mal | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Ninguna | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bon | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Passable | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Mauvais | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Aucun | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/es-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4813": { + "relUrl": "/fr-rFR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4743": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/es-rES/user/signal-meter.html#4-what-this-means-for-you" - },"4814": { + "relUrl": "/fr-rFR/user/signal-meter.html#4-what-this-means-for-you" + },"4744": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/es-rES/user/signal-meter.html#where-signal-information-appears" - },"4815": { + "relUrl": "/fr-rFR/user/signal-meter.html#where-signal-information-appears" + },"4745": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#related-topics", - "relUrl": "/es-rES/user/signal-meter.html#related-topics" - },"4816": { + "relUrl": "/fr-rFR/user/signal-meter.html#related-topics" + },"4746": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html", + "url": "/Meshtastic-Android/main/srp/user/signal-meter.html", - "relUrl": "/tr-rTR/user/signal-meter.html" - },"4817": { + "relUrl": "/srp/user/signal-meter.html" + },"4747": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/tr-rTR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4818": { + "relUrl": "/srp/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4748": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/tr-rTR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4819": { + "relUrl": "/srp/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4749": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | İyi | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | İdare Eder | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Kötü | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Yok | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Ниво | Bars | Criteria | Meaning | . | Добро | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Прихватљив | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Лош | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Ништа | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/tr-rTR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4820": { + "relUrl": "/srp/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4750": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/tr-rTR/user/signal-meter.html#4-what-this-means-for-you" - },"4821": { + "relUrl": "/srp/user/signal-meter.html#4-what-this-means-for-you" + },"4751": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/tr-rTR/user/signal-meter.html#where-signal-information-appears" - },"4822": { + "relUrl": "/srp/user/signal-meter.html#where-signal-information-appears" + },"4752": { "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", + "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#related-topics", - "relUrl": "/tr-rTR/user/signal-meter.html#related-topics" - },"4823": { + "relUrl": "/srp/user/signal-meter.html#related-topics" + },"4753": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html", + "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html", - "relUrl": "/no-rNO/user/signal-meter.html" - },"4824": { + "relUrl": "/sk-rSK/user/signal-meter.html" + },"4754": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/no-rNO/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4825": { + "relUrl": "/sk-rSK/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4755": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/no-rNO/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4826": { + "relUrl": "/sk-rSK/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4756": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Godt | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Middelmådig | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Dårlig | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Ingen | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Dobrý | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Primeraný | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Zlý | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Žiadny | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/no-rNO/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4827": { + "relUrl": "/sk-rSK/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4757": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/no-rNO/user/signal-meter.html#4-what-this-means-for-you" - },"4828": { + "relUrl": "/sk-rSK/user/signal-meter.html#4-what-this-means-for-you" + },"4758": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/no-rNO/user/signal-meter.html#where-signal-information-appears" - },"4829": { + "relUrl": "/sk-rSK/user/signal-meter.html#where-signal-information-appears" + },"4759": { "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", + "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#related-topics", - "relUrl": "/no-rNO/user/signal-meter.html#related-topics" - },"4830": { + "relUrl": "/sk-rSK/user/signal-meter.html#related-topics" + },"4760": { + "doc": "Kuinka Meshtastic-signaalimittari toimii", + "title": "Kuinka Meshtastic-signaalimittari toimii", + "content": "Meshtasticin signaalimittari — sovelluksessa näkyvät tutut palkit tai tilan väri — lasketaan hyvin eri tavalla kuin perinteisen matkapuhelimen tai WiFi-reitittimen “palkit”. Useimmat kuluttajalaitteet mittaavat yksinkertaisesti signaalin “voimakkuutta”. Koska Meshtastic käyttää LoRa (Long Range) -teknologiaa, signaalimittari arvioi sen sijaan kuinka “selkeä” signaali on suhteessa käytössä olevan mesh-verkon asetuksiin. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html", + + "relUrl": "/fi-rFI/user/signal-meter.html" + },"4761": { + "doc": "Kuinka Meshtastic-signaalimittari toimii", + "title": "1. Kaksi mittaria: “voimakkuus” vs “selkeys”", + "content": "Aina kun LoRa-radio vastaanottaa viestin, se raportoi kaksi arvoa: . | RSSI (Received Signal Strength Indicator): kuinka “voimakas” antenniin saapuva signaali on. | SNR (Signal-to-Noise Ratio): kuinka “selkeä” signaali on suhteessa taustakohinaan. | . 💡 Vinkki: Ajattele asiaa näin — yrität kuulla ystäväsi puhetta. | RSSI on kuinka kovaa hän puhuu. | Melutaso (Noise Floor) on huoneen taustahäly (ilmastointi, muut ihmiset, liikenne). | SNR on se, kuinka hyvin erotat ystäväsi äänen taustamelusta. | . Jos ystäväsi huutaa rock-konsertissa, signaali on erittäin voimakas (korkea RSSI), mutta et silti ymmärrä häntä, koska kohina on liian suuri (huono SNR). Toisaalta, jos hän kuiskaa hiljaisessa kirjastossa, signaali voi olla heikko (matala RSSI), mutta ymmärrät silti hyvin (hyvä SNR). ", + "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#1-kaksi-mittaria-voimakkuus-vs-selkeys", + + "relUrl": "/fi-rFI/user/signal-meter.html#1-kaksi-mittaria-voimakkuus-vs-selkeys" + },"4762": { + "doc": "Kuinka Meshtastic-signaalimittari toimii", + "title": "2. LoRa:n “taika”: kuuleminen kohinan alta", + "content": "Tavallisessa radiossa (kuten FM- tai WiFi-yhteydessä), jos taustakohina on voimakkaampi kuin signaali (negatiivinen SNR), vastaanotin kuulee vain kohinaa. LoRa on erilainen. Se käyttää hajaspektritekniikkaa (Spread Spectrum), joka mahdollistaa signaalin erottamisen myös silloin, kun se on taustakohinan alla. Siksi Meshtasticissa näkyy usein negatiivisia SNR-arvoja (esim. -10 dB tarkoittaa, että signaali on 10 dB heikompi kuin kohina). Riippuen siitä, mitä Meshtastic-esiasetusta käytät (esim. “LongFast” vs. “ShortFast”), radiolla on tietty SNR-raja — eli suurin määrä kohinaa, jonka se kestää ennen kuin viesti alkaa kadota täysin kohinaan. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#2-loran-taika-kuuleminen-kohinan-alta", + + "relUrl": "/fi-rFI/user/signal-meter.html#2-loran-taika-kuuleminen-kohinan-alta" + },"4763": { + "doc": "Kuinka Meshtastic-signaalimittari toimii", + "title": "3. Kuinka signaalimittari laskee laadun", + "content": "Sovellus arvioi signaalin laadun (Ei, Huono, Kohtalainen tai Hyvä) pelkästään SNR-arvon perusteella, suhteessa esiasetuksen SNR-rajaan — eli demodulaation alarajaan, joka on kuvattu aiemmin. Se ei tarkoituksella ota RSSI-arvoa huomioon arvioinnissa: ilman paikallista kohinatasoa RSSI ei kerro, voidaanko signaali todella purkaa, joten SNR suhteessa esiasetuksen rajaan on merkityksellinen mittari. (RSSI näytetään edelleen muualla sovelluksessa.) . Koska arviointi perustuu esiasetuksen rajaan, sama SNR-arvo voi saada eri arvosanan eri esiasetuksilla — esimerkiksi -15 dB on hyvä arvo LongSlow-esiasetuksella, mutta käyttökelvoton ShortFast-esiasetuksella. Jos “raja” tarkoittaa käytössä olevan esiasetuksen SNR-rajaa, sovellus määrittää palkit (tai värin) seuraavasti: . | Taso | Palkit | Kriteerit | Merkitys | . | Hyvä | 3 | SNR esiasetuksen rajan yläpuolella | Signaali on selvästi demodulaation alarajan yläpuolella — hyvä yhteys. | . | Kohtalainen | 2 | alle 5,5 dB rajan alapuolella | Signaali voidaan vielä purkaa, mutta se on lähellä demodulaation alarajaa. | . | Huono | 1 | 5,5–7,5 dB rajan alapuolella | Signaali on aivan esiasetuksen palautumiskyvyn rajalla. | . | ei mitään | 0 | yli 7,5 dB “rajan” alapuolella | Signaali on demodulaation alarajan alapuolella — lähetys hukkuu kohinaan. | . Huomautus: Kiinteitä SNR-rajoja, joita olet ehkä nähnyt muualla (−7 dB / −15 dB), käytetään nykyisin vain traceroute-tulosten yksittäisten hyppyjen väritykseen — ei radion yleisen signaalin laadun arviointiin. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#3-kuinka-signaalimittari-laskee-laadun", + + "relUrl": "/fi-rFI/user/signal-meter.html#3-kuinka-signaalimittari-laskee-laadun" + },"4764": { + "doc": "Kuinka Meshtastic-signaalimittari toimii", + "title": "4. Mitä tämä tarkoittaa sinulle", + "content": "Koska Meshtasticin mittari toimii enemmän selkeysmittarina, se käyttäytyy eri tavalla kuin useimmat odottavat: . 💡 Vinkki: Älä huolestu matalasta RSSI-arvosta. Saatat nähdä näennäisesti erittäin huonon RSSI-arvon, kuten -118 dBm. Tavallisessa puhelimessa tämä tarkoittaisi käytännössä nollakenttää. Mutta jos SNR on esimerkiksi +2 dB, Meshtastic voi silti näyttää vahvaa signaalia! Kirjasto on hiljainen, joten kuiskaus kuuluu täydellisesti. ⚠️ Varoitus: Kiinnitä huomiota paikalliseen kohinaan. Jos liität suuren antennin ja näet hyvän RSSI-arvon (esim. -90 dBm), mutta signaalimittari näyttää silti vain 1 palkin (Huono), yhteydessä on ongelma. Se tarkoittaa paikallista häiriötä — esimerkiksi halpa virtalähde, kohiseva elektroniikka tai lähellä oleva radiolähetin voi luoda niin paljon kohinaa, että se peittää mesh-verkon. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#4-mit%C3%A4-t%C3%A4m%C3%A4-tarkoittaa-sinulle", + + "relUrl": "/fi-rFI/user/signal-meter.html#4-mitä-tämä-tarkoittaa-sinulle" + },"4765": { + "doc": "Kuinka Meshtastic-signaalimittari toimii", + "title": "Missä signaalitieto näkyy", + "content": "Sovelluksessa signaalidata näkyy useissa paikoissa: . | Radiolista — signaalipalkki jokaisen radion vieressä | Radion tiedot — SNR, RSSI ja signaalin laatu laitteen mittareissa | Reitinselvitys — signaalin laatu jokaisessa välivaiheessa jokaiselle välittävälle radiolle | Signaalimittarit — historiallinen SNR- ja RSSI-data mittauskaavioissa | . ", + "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" + },"4766": { + "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" + },"4767": { "doc": "Как работает измеритель сигнала Meshtastic", "title": "Как работает измеритель сигнала Meshtastic", "content": "Измеритель сигнала Meshtastic — знакомые полоски или цвет состояния в приложении — рассчитывается совсем иначе, чем “полоски” на обычном мобильном телефоне или WiFi-роутере. Большинство потребительских устройств просто измеряют, насколько “громкий” сигнал. Однако, поскольку Meshtastic использует технологию LoRa (Long Range), его измеритель сигнала оценивает, насколько чистый сигнал, относительно конкретных настроек вашей mesh-сети. ", "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html", "relUrl": "/ru-rRU/user/signal-meter.html" - },"4831": { + },"4768": { "doc": "Как работает измеритель сигнала Meshtastic", "title": "1. Две метрики: “Громкость” против “Чёткости”", "content": "Каждый раз, когда радиочип LoRa получает сообщение, он сообщает два измерения: . | RSSI (Индикатор уровня принятого сигнала): громкость необработанного сигнала, поступающего на твою антенну. | SNR (Соотношение сигнал/шум): Чёткость сигнала по сравнению с фоновым шумом. | . 💡 Совет: Вот аналогия — представь, что пытаешься услышать, что тебе говорит друг. | RSSI — это громкость его голоса. | Минимальный уровень шума — это фоновый шум в комнате (кондиционер, разговоры других людей, движение транспорта). | SNR — это то, насколько легко ты можешь различить голос твоего друга на фоне шума. | . Если твой друг кричит тебе на оглушительном рок-концерте, сигнал невероятно громкий (высокий RSSI), но ты всё равно не можешь его понять, потому что фоновый шум громче (плохое SNR). И наоборот, если твой друг шепчет тебе в абсолютно тихой библиотеке, сигнал очень слабый (низкий RSSI), но ты можешь его прекрасно понять (отличный SNR). ", "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html#1-%D0%B4%D0%B2%D0%B5-%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA%D0%B8-%D0%B3%D1%80%D0%BE%D0%BC%D0%BA%D0%BE%D1%81%D1%82%D1%8C-%D0%BF%D1%80%D0%BE%D1%82%D0%B8%D0%B2-%D1%87%D1%91%D1%82%D0%BA%D0%BE%D1%81%D1%82%D0%B8", "relUrl": "/ru-rRU/user/signal-meter.html#1-две-метрики-громкость-против-чёткости" - },"4832": { + },"4769": { "doc": "Как работает измеритель сигнала Meshtastic", "title": "2. Магия LoRa: слышит “ниже уровня шума”", "content": "Для обычных радиоприёмников (например, FM или WiFi), если фоновый шум громче сигнала (отрицательный SNR), приёмник просто слышит шум. LoRa особенная. Она использует модуляцию “широкополосного спектра”, которая позволяет радио математически извлекать сигнал из воздуха даже когда он глубоко под фоновым шумом. Вот почему ты часто будете видеть отрицательные значения SNR в Meshtastic (например, -10 дБ, что означает, что сигнал на 10 децибел слабее фонового шума). В зависимости от того, какой пресет Meshtastic ты используешь (например, LongFast или ShortFast), у радиоприемника есть определённый предел SNR — абсолютное максимальное количество шума, которое он может выдержать, прежде чем сообщение полностью потеряется в помехах. ", "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html#2-%D0%BC%D0%B0%D0%B3%D0%B8%D1%8F-lora-%D1%81%D0%BB%D1%8B%D1%88%D0%B8%D1%82-%D0%BD%D0%B8%D0%B6%D0%B5-%D1%83%D1%80%D0%BE%D0%B2%D0%BD%D1%8F-%D1%88%D1%83%D0%BC%D0%B0", "relUrl": "/ru-rRU/user/signal-meter.html#2-магия-lora-слышит-ниже-уровня-шума" - },"4833": { + },"4770": { "doc": "Как работает измеритель сигнала Meshtastic", "title": "3. Как измеритель сигнала рассчитывает качество", "content": "Приложение оценивает качество сигнала (Нет, Плохо, Средне или Хорошо) только по SNR, измеренному относительно установленного порога SNR — той самой демодуляционной границы, о которой говорилось выше. Он намеренно не учитывает RSSI в оценке: без локального уровня шума RSSI не может сказать, можно ли реально декодировать сигнал, поэтому показатель SNR по сравнению с установленным лимитом является значимой мерой. (RSSI всё ещё отображается где-то ещё.) . Поскольку рейтинг зависит от заранее заданного лимита, один и тот же SNR может оцениваться по-разному на разных пресетах — -15 dB нормально для LongSlow, но непригодно для ShortFast. Допустим, limit — это предел SNR у активного пресета, вот как приложение выбирает полоски (или цвет): . | Уровень | Деления | Критерии | Значение | . | Хороший | 3 | SNR выше установленного limit | Сигнал с запасом выше порога демодуляции — связь в порядке. | . | Средний | 2 | меньше чем на 5,5 дБ ниже limit | Понятно, но уже почти до пола. | . | Плохой | 1 | 5,5 дБ до 7,5 дБ ниже limit | На самом пределе того, что может восстановить пресет. | . | Отсутствует | 0 | более чем на 7,5 дБ ниже limit | Ниже порога — сигнал потерян из-за помех. | . Примечание: Фиксированные пороги SNR, которые вы могли видеть где-то ещё (-7 дБ / -15 дБ), теперь используются только для окрашивания отдельных хопов в результатах трассировки — а не для измерителя сигнала на каждой ноде, о которой идёт речь здесь. ", "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html#3-%D0%BA%D0%B0%D0%BA-%D0%B8%D0%B7%D0%BC%D0%B5%D1%80%D0%B8%D1%82%D0%B5%D0%BB%D1%8C-%D1%81%D0%B8%D0%B3%D0%BD%D0%B0%D0%BB%D0%B0-%D1%80%D0%B0%D1%81%D1%81%D1%87%D0%B8%D1%82%D1%8B%D0%B2%D0%B0%D0%B5%D1%82-%D0%BA%D0%B0%D1%87%D0%B5%D1%81%D1%82%D0%B2%D0%BE", "relUrl": "/ru-rRU/user/signal-meter.html#3-как-измеритель-сигнала-рассчитывает-качество" - },"4834": { + },"4771": { "doc": "Как работает измеритель сигнала Meshtastic", "title": "4. Что это значит для тебя", "content": "Поскольку измеритель Meshtastic действует как “Измеритель чёткости”, он ведёт себя иначе, чем ожидает большинство людей: . 💡 Совет: Не паниковать из-за низкого RSSI. Вы можете увидеть, например, такой вроде бы ужасный показатель RSSI, как -118 dBm. На сотовом телефоне у тебя было бы ноль делений. Но если отношение сигнал/шум (SNR) +2 дБ, Meshtastic все равно покажет сильный сигнал! Библиотека тихая, поэтому шепот слышен идеально. ⚠️ Внимание: Остерегайтесь локального шума. Если подключить огромную антенну и увидеть отличный RSSI (например, -90 dBm), но индикатор сигнала показывает всего 1 деление (Плохо), значит, у тебя проблема. Это означает, что у тебя есть местные помехи — возможно, дешевый источник питания, шумный компьютер или расположенная рядом радиовышка — создающие столько статического шума, что он заглушает сеть. ", "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html#4-%D1%87%D1%82%D0%BE-%D1%8D%D1%82%D0%BE-%D0%B7%D0%BD%D0%B0%D1%87%D0%B8%D1%82-%D0%B4%D0%BB%D1%8F-%D1%82%D0%B5%D0%B1%D1%8F", "relUrl": "/ru-rRU/user/signal-meter.html#4-что-это-значит-для-тебя" - },"4835": { + },"4772": { "doc": "Как работает измеритель сигнала Meshtastic", "title": "Где появляется информация о сигнале", "content": "В приложении данные сигнала отображаются в нескольких местах: . | Список нод — значок полос сигнала рядом с каждой нодой | Детали ноды — SNR, RSSI и качество сигнала в разделе метрик устройства | Трассировка — качество сигнала на каждой промежуточной ноде | Метрики сигнала — история данных SNR и RSSI на графиках метрик | . ", "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#где-появляется-информация-о-сигнале" - },"4836": { + },"4773": { "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#связанные-темы" + },"4774": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html", + + "relUrl": "/ko-rKR/user/signal-meter.html" + },"4775": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/ko-rKR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4776": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/ko-rKR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4777": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | 좋음 | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | 보통 | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | 나쁨 | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | 없음 | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/ko-rKR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4778": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/ko-rKR/user/signal-meter.html#4-what-this-means-for-you" + },"4779": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4780": { + "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" + },"4781": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html", + + "relUrl": "/hr-rHR/user/signal-meter.html" + },"4782": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/hr-rHR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4783": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/hr-rHR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4784": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/hr-rHR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4785": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/hr-rHR/user/signal-meter.html#4-what-this-means-for-you" + },"4786": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4787": { + "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" + },"4788": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html", + + "relUrl": "/sq-rAL/user/signal-meter.html" + },"4789": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/sq-rAL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4790": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/sq-rAL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4791": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Mirë | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Mesatar | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | I Keq | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Asnjë | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/sq-rAL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4792": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/sq-rAL/user/signal-meter.html#4-what-this-means-for-you" + },"4793": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4794": { + "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" + },"4795": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html", + + "relUrl": "/no-rNO/user/signal-meter.html" + },"4796": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/no-rNO/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4797": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/no-rNO/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4798": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Godt | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Middelmådig | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Dårlig | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Ingen | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/no-rNO/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4799": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/no-rNO/user/signal-meter.html#4-what-this-means-for-you" + },"4800": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4801": { + "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" + },"4802": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html", + + "relUrl": "/lt-rLT/user/signal-meter.html" + },"4803": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/lt-rLT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4804": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/lt-rLT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4805": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Geras | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Pakankamas | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Silpnas | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Nėra | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/lt-rLT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4806": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/lt-rLT/user/signal-meter.html#4-what-this-means-for-you" + },"4807": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4808": { + "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" + },"4809": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html", + + "relUrl": "/ar-rSA/user/signal-meter.html" + },"4810": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/ar-rSA/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4811": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/ar-rSA/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4812": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | جيد | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | مناسب | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | سيئ | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | لا يوجد | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/ar-rSA/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4813": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/ar-rSA/user/signal-meter.html#4-what-this-means-for-you" + },"4814": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4815": { + "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" + },"4816": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html", + + "relUrl": "/pt-rPT/user/signal-meter.html" + },"4817": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/pt-rPT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4818": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/pt-rPT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4819": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bom | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Razoável | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Mau | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Nenhum | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/pt-rPT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4820": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/pt-rPT/user/signal-meter.html#4-what-this-means-for-you" + },"4821": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4822": { + "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" + },"4823": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html", + + "relUrl": "/iw-rIL/user/signal-meter.html" + },"4824": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/iw-rIL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4825": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/iw-rIL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4826": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/iw-rIL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4827": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/iw-rIL/user/signal-meter.html#4-what-this-means-for-you" + },"4828": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4829": { + "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" + },"4830": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html", + + "relUrl": "/el-rGR/user/signal-meter.html" + },"4831": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/el-rGR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4832": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/el-rGR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4833": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/el-rGR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4834": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/el-rGR/user/signal-meter.html#4-what-this-means-for-you" + },"4835": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4836": { + "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" },"4837": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html", + "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html", - "relUrl": "/nl-rNL/user/signal-meter.html" + "relUrl": "/ro-rRO/user/signal-meter.html" },"4838": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/nl-rNL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + "relUrl": "/ro-rRO/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" },"4839": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/nl-rNL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + "relUrl": "/ro-rRO/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" },"4840": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Goed | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Matig | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Slecht | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Geen | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bun | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Acceptabil | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Slab | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Niciunul | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/nl-rNL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + "relUrl": "/ro-rRO/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" },"4841": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/nl-rNL/user/signal-meter.html#4-what-this-means-for-you" + "relUrl": "/ro-rRO/user/signal-meter.html#4-what-this-means-for-you" },"4842": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/nl-rNL/user/signal-meter.html#where-signal-information-appears" + "relUrl": "/ro-rRO/user/signal-meter.html#where-signal-information-appears" },"4843": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#related-topics", - "relUrl": "/nl-rNL/user/signal-meter.html#related-topics" + "relUrl": "/ro-rRO/user/signal-meter.html#related-topics" },"4844": { "doc": "Kuidas Meshtastic signaalimõõtur töötab", "title": "Kuidas Meshtastic signaalimõõtur töötab", @@ -33959,2522 +33959,2522 @@ "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html", + "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html", - "relUrl": "/it-rIT/user/signal-meter.html" + "relUrl": "/ga-rIE/user/signal-meter.html" },"4852": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/it-rIT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + "relUrl": "/ga-rIE/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" },"4853": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/it-rIT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + "relUrl": "/ga-rIE/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" },"4854": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Buono | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Discreto | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Scarso | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Nessuno | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Maith | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Ceart go leor | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Go dona | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Ní dhéanfaidh sé | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/it-rIT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + "relUrl": "/ga-rIE/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" },"4855": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/it-rIT/user/signal-meter.html#4-what-this-means-for-you" + "relUrl": "/ga-rIE/user/signal-meter.html#4-what-this-means-for-you" },"4856": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/it-rIT/user/signal-meter.html#where-signal-information-appears" + "relUrl": "/ga-rIE/user/signal-meter.html#where-signal-information-appears" },"4857": { "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#related-topics", - "relUrl": "/it-rIT/user/signal-meter.html#related-topics" + "relUrl": "/ga-rIE/user/signal-meter.html#related-topics" },"4858": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html", - - "relUrl": "/ar-rSA/user/signal-meter.html" - },"4859": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/ar-rSA/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4860": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/ar-rSA/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4861": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | جيد | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | مناسب | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | سيئ | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | لا يوجد | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/ar-rSA/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4862": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/ar-rSA/user/signal-meter.html#4-what-this-means-for-you" - },"4863": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4864": { - "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" - },"4865": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "How the Meshtastic Signal Meter Works", - "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html", - - "relUrl": "/sk-rSK/user/signal-meter.html" - },"4866": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", - "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - - "relUrl": "/sk-rSK/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4867": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", - "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - - "relUrl": "/sk-rSK/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4868": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Dobrý | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Primeraný | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Zlý | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Žiadny | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - - "relUrl": "/sk-rSK/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4869": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "4. What This Means for You", - "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#4-what-this-means-for-you", - - "relUrl": "/sk-rSK/user/signal-meter.html#4-what-this-means-for-you" - },"4870": { - "doc": "How the Meshtastic Signal Meter Works", - "title": "Where Signal Information Appears", - "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "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" - },"4871": { - "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" - },"4872": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html", "relUrl": "/pl-rPL/user/signal-meter.html" - },"4873": { + },"4859": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", "relUrl": "/pl-rPL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" - },"4874": { + },"4860": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", "relUrl": "/pl-rPL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4875": { + },"4861": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | dobry | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | wystarczający | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | słaby | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Brak | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", "relUrl": "/pl-rPL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4876": { + },"4862": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html#4-what-this-means-for-you", "relUrl": "/pl-rPL/user/signal-meter.html#4-what-this-means-for-you" - },"4877": { + },"4863": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", "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" - },"4878": { + },"4864": { "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" - },"4879": { + },"4865": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html", + "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html", - "relUrl": "/zh-rTW/user/signal-meter.html" - },"4880": { + "relUrl": "/nl-rNL/user/signal-meter.html" + },"4866": { "doc": "How the Meshtastic Signal Meter Works", - "title": "1. Meshtastic is an open source, decentralized, off-grid, privacy-respecting, encrypted communications platform built on affordable, readily available hardware. It enables you and your friends to communicate securely with text messages, share locations, and more over long ranges.", - "content": ". | It’s built on top of a software defined radio platform called LoRa, enabling inexpensive radios (based on popular chips like the ESP32, nRF52, and RP2040) to operate as long range, low power, and secure communicators. | Common hardware includes devices like the RAK WisBlock series, T-Beam, Heltec, and LilyGo boards. | Meshtastic supports communication over several radio channels, allowing you to separate traffic or experiment with different settings. You can configure parameters like the spreading factor, bandwidth, and coding rate to optimize for range, data rate, and reliability. These settings are often referred to as radio profiles, with common examples being “Long Fast” or “Mid Slow”. | Besides LoRa, Meshtastic devices can also communicate using BLE for short-range communication with smartphones and other devices. | Meshtastic devices can be configured using a variety of methods, including: . | A mobile app (available for Android and iOS) | A web-based interface | A CLI | An API | . | Meshtastic can also be integrated with other systems using protocols like MQTT. | You can extend the functionality of Meshtastic devices by writing your own firmware or connecting external sensors and devices using the GPIO, USB, UART, SPI, and I2C interfaces. | Meshtastic devices can be powered by batteries, USB, or other power sources. | Meshtastic supports Over-The-Air (OTA) firmware updates via LoRa, WiFi or Bluetooth. | Meshtastic allows for end-to-end encryption of messages. | Meshtastic devices can act as repeaters, extending the range of the network. The Two Metrics: “Loudness” vs. “Clarity” | . Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#1-meshtastic-is-an-open-source-decentralized-off-grid-privacy-respecting-encrypted-communications-platform-built-on-affordable-readily-available-hardware-it-enables-you-and-your-friends-to-communicate-securely-with-text-messages-share-locations-and-more-over-long-ranges", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/zh-rTW/user/signal-meter.html#1-meshtastic-is-an-open-source-decentralized-off-grid-privacy-respecting-encrypted-communications-platform-built-on-affordable-readily-available-hardware-it-enables-you-and-your-friends-to-communicate-securely-with-text-messages-share-locations-and-more-over-long-ranges" - },"4881": { + "relUrl": "/nl-rNL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4867": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/zh-rTW/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" - },"4882": { + "relUrl": "/nl-rNL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4868": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | —– | ————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————– | ————————————– | —————————————————————————————- | 良好 | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | 普通 | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | 不良 | 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/) | `5.5 dB` to `7.5 dB` below the `limit` | At the very edge of what the preset can recover. | 無 | 0 | more than `7.5 dB` below the `limit` | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Goed | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Matig | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Slecht | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Geen | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/zh-rTW/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" - },"4883": { + "relUrl": "/nl-rNL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4869": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/zh-rTW/user/signal-meter.html#4-what-this-means-for-you" - },"4884": { + "relUrl": "/nl-rNL/user/signal-meter.html#4-what-this-means-for-you" + },"4870": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/zh-rTW/user/signal-meter.html#where-signal-information-appears" - },"4885": { + "relUrl": "/nl-rNL/user/signal-meter.html#where-signal-information-appears" + },"4871": { "doc": "How the Meshtastic Signal Meter Works", - "title": "相關主題", + "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-rTW/user/signal-meter.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C", + "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#related-topics", - "relUrl": "/zh-rTW/user/signal-meter.html#相關主題" + "relUrl": "/nl-rNL/user/signal-meter.html#related-topics" + },"4872": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "How the Meshtastic Signal Meter Works", + "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html", + + "relUrl": "/sv-rSE/user/signal-meter.html" + },"4873": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", + "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", + "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + + "relUrl": "/sv-rSE/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + },"4874": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", + "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + + "relUrl": "/sv-rSE/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + },"4875": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "3. How the Signal Meter Calculates Quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bra | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Ok | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Dålig | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Ingen | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + + "relUrl": "/sv-rSE/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + },"4876": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "4. What This Means for You", + "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#4-what-this-means-for-you", + + "relUrl": "/sv-rSE/user/signal-meter.html#4-what-this-means-for-you" + },"4877": { + "doc": "How the Meshtastic Signal Meter Works", + "title": "Where Signal Information Appears", + "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", + "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" + },"4878": { + "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" + },"4879": { + "doc": "Meshtastic の信号メーターの仕組み", + "title": "Meshtastic の信号メーターの仕組み", + "content": "Meshtastic の信号メーター（アプリでおなじみのバーやステータスの色）は、従来の携帯電話や WiFi ルーターの「バー」とはまったく異なる方法で計算されます。 . ほとんどの一般向けデバイスは、単に信号がどれだけ「大きい」かを測定します。 しかし Meshtastic は LoRa（Long Range）技術を使用しているため、その信号メーターは、メッシュが使用している具体的な設定を基準に、信号がどれだけ明瞭かを測定します。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html", + + "relUrl": "/ja-rJP/user/signal-meter.html" + },"4880": { + "doc": "Meshtastic の信号メーターの仕組み", + "title": "1. 2 つの指標：「大きさ」と「明瞭さ」", + "content": "LoRa の無線チップは、メッセージを受信するたびに 2 つの測定値を報告します： . | RSSI（受信信号強度インジケーター）： アンテナに届く生の電力の大きさ。 | SNR（信号対ノイズ比）： 背景のノイズと比較した信号の明瞭さ。 | . 💡 ヒント： たとえて言うと、友人があなたに話しかけているのを聞き取ろうとしている場面を想像してください。 . | RSSI は、その声がどれだけ大きいかです。 | ノイズフロアは、部屋の中の背景ノイズ（エアコン、他の人の話し声、交通音）です。 | SNR は、背景ノイズの中から友人の声をどれだけ簡単に聞き分けられるかです。 | . 耳をつんざくようなロックコンサートで友人が叫んでも、信号は非常に大きい（高い RSSI）一方で、背景ノイズのほうが大きいため（悪い SNR）、聞き取れません。 逆に、静まり返った図書館で友人がささやけば、信号は非常に弱い（低い RSSI）ものの、完璧に聞き取れます（非常に良い SNR）。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#1-2-%E3%81%A4%E3%81%AE%E6%8C%87%E6%A8%99%E5%A4%A7%E3%81%8D%E3%81%95%E3%81%A8%E6%98%8E%E7%9E%AD%E3%81%95", + + "relUrl": "/ja-rJP/user/signal-meter.html#1-2-つの指標大きさと明瞭さ" + },"4881": { + "doc": "Meshtastic の信号メーターの仕組み", + "title": "2. LoRa の魔法：「ノイズフロアの下」を聞き取る", + "content": "標準的な無線（FM や WiFi など）では、背景ノイズが信号より大きい（負の SNR）場合、受信機にはノイズしか聞こえません。 . LoRa は特別です。 **「スペクトラム拡散」**変調を使用しており、信号が背景ノイズの下深くに埋もれていても、無線機が数学的に信号を取り出せます。 そのため Meshtastic では、負の SNR 値が頻繁に見られます（例：-10 dB。これは信号が背景ノイズより 10 デシベル弱いことを意味します）。 . 使用している Meshtastic のプリセット（例：LongFast と ShortFast）に応じて、無線機には固有の SNR 限界があります。これは、メッセージがノイズに完全に埋もれてしまう前に許容できるノイズの絶対的な最大量です。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#2-lora-%E3%81%AE%E9%AD%94%E6%B3%95%E3%83%8E%E3%82%A4%E3%82%BA%E3%83%95%E3%83%AD%E3%82%A2%E3%81%AE%E4%B8%8B%E3%82%92%E8%81%9E%E3%81%8D%E5%8F%96%E3%82%8B", + + "relUrl": "/ja-rJP/user/signal-meter.html#2-lora-の魔法ノイズフロアの下を聞き取る" + },"4882": { + "doc": "Meshtastic の信号メーターの仕組み", + "title": "3. 信号メーターが品質を計算する仕組み", + "content": "アプリは、信号品質（なし・不良・普通・良）を SNR のみから、プリセットの SNR 限界を基準として評価します。これは前述の復調限界です。 この評価には、意図的に RSSI を含めていません。ローカルのノイズフロアが分からなければ、RSSI だけでは信号が実際に復調できるかどうかは分からないため、プリセット限界に対する SNR が意味のある指標になります。 （RSSI は、別の場所には引き続き表示されます。） . 評価はプリセット限界を基準とするため、同じ SNR でもプリセットによって評価が異なります。-15 dB は LongSlow では良好ですが、ShortFast では使い物になりません。 limit を現在のプリセットの SNR 限界とすると、アプリがバー（または色）を選ぶ方法は次のとおりです： . | レベル | バー | 基準 | 意味 | . | 良 | 3 | SNR がプリセットの limit を上回る | 信号が復調限界を十分に上回っています。良好な接続です。 | . | 普通 | 2 | limit より 5.5 dB 未満低い | 復調できますが、限界に近づいています。 | . | 不良 | 1 | limit より 5.5 dB〜7.5 dB 低い | プリセットが復元できるぎりぎりの境界です。 | . | なし | 0 | limit より 7.5 dB を超えて低い | 限界を下回っています。送信がノイズに埋もれて失われます。 | . 注意： 他の場所で見かけたことのある固定の SNR しきい値（-7 dB／-15 dB）は、現在ではルート追跡の結果で個々のホップに色を付けるためだけに使われ、ここで説明しているノードごとの信号メーターには使われません。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#3-%E4%BF%A1%E5%8F%B7%E3%83%A1%E3%83%BC%E3%82%BF%E3%83%BC%E3%81%8C%E5%93%81%E8%B3%AA%E3%82%92%E8%A8%88%E7%AE%97%E3%81%99%E3%82%8B%E4%BB%95%E7%B5%84%E3%81%BF", + + "relUrl": "/ja-rJP/user/signal-meter.html#3-信号メーターが品質を計算する仕組み" + },"4883": { + "doc": "Meshtastic の信号メーターの仕組み", + "title": "4. これがあなたにとって意味すること", + "content": "Meshtastic のメーターは**「明瞭さのメーター」**として機能するため、多くの人が予想するのとは異なる動作をします： . 💡 ヒント： RSSI が低くても慌てないでください。 -118 dBm のような、一見ひどい RSSI 値が表示されることがあります。 携帯電話なら、バーはゼロでしょう。 しかし SNR が +2 dB あれば、Meshtastic は依然として強い信号を表示します！ 図書館は静かなので、ささやき声も完璧に聞こえます。 . ⚠️ 警告： ローカルのノイズに注意してください。 大型のアンテナを接続して優れた RSSI（例：-90 dBm）が表示されているのに、信号メーターが **1 本（不良）**しか表示していない場合、問題があります。 これは、ローカルの干渉（安価な電源、ノイズの多いコンピューター、近くの電波塔など）が大量のノイズを発生させ、メッシュをかき消していることを意味します。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#4-%E3%81%93%E3%82%8C%E3%81%8C%E3%81%82%E3%81%AA%E3%81%9F%E3%81%AB%E3%81%A8%E3%81%A3%E3%81%A6%E6%84%8F%E5%91%B3%E3%81%99%E3%82%8B%E3%81%93%E3%81%A8", + + "relUrl": "/ja-rJP/user/signal-meter.html#4-これがあなたにとって意味すること" + },"4884": { + "doc": "Meshtastic の信号メーターの仕組み", + "title": "信号情報が表示される場所", + "content": "アプリでは、信号データはいくつかの場所に表示されます： . | ノードリスト：各ノードの横にある信号バーのアイコン | ノードの詳細：デバイスメトリクスのセクションにある SNR、RSSI、信号品質 | ルート追跡：各中継ノードの、ホップごとの信号品質 | 信号メトリクス：メトリクスのグラフにある SNR と RSSI の履歴データ | . ", + "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#信号情報が表示される場所" + },"4885": { + "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#関連トピック" },"4886": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html", + "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html", - "relUrl": "/cs-rCZ/user/signal-meter.html" + "relUrl": "/hu-rHU/user/signal-meter.html" },"4887": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/cs-rCZ/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + "relUrl": "/hu-rHU/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" },"4888": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/cs-rCZ/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + "relUrl": "/hu-rHU/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" },"4889": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Silný | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Slabý | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Špatný | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Žádný | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Jó | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Megfelelő | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Rossz | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Semmi | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/cs-rCZ/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + "relUrl": "/hu-rHU/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" },"4890": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/cs-rCZ/user/signal-meter.html#4-what-this-means-for-you" + "relUrl": "/hu-rHU/user/signal-meter.html#4-what-this-means-for-you" },"4891": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/cs-rCZ/user/signal-meter.html#where-signal-information-appears" + "relUrl": "/hu-rHU/user/signal-meter.html#where-signal-information-appears" },"4892": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#related-topics", - "relUrl": "/cs-rCZ/user/signal-meter.html#related-topics" + "relUrl": "/hu-rHU/user/signal-meter.html#related-topics" },"4893": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html", + "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html", - "relUrl": "/fr-rFR/user/signal-meter.html" + "relUrl": "/ht-rHT/user/signal-meter.html" },"4894": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/fr-rFR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + "relUrl": "/ht-rHT/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" },"4895": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/fr-rFR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + "relUrl": "/ht-rHT/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" },"4896": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bon | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Passable | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Mauvais | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Aucun | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bon | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Mwayen | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Move | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Pa gen | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/fr-rFR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + "relUrl": "/ht-rHT/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" },"4897": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/fr-rFR/user/signal-meter.html#4-what-this-means-for-you" + "relUrl": "/ht-rHT/user/signal-meter.html#4-what-this-means-for-you" },"4898": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/fr-rFR/user/signal-meter.html#where-signal-information-appears" + "relUrl": "/ht-rHT/user/signal-meter.html#where-signal-information-appears" },"4899": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#related-topics", - "relUrl": "/fr-rFR/user/signal-meter.html#related-topics" + "relUrl": "/ht-rHT/user/signal-meter.html#related-topics" },"4900": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html", + "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html", - "relUrl": "/zh-rCN/user/signal-meter.html" + "relUrl": "/gl-rES/user/signal-meter.html" },"4901": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/zh-rCN/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + "relUrl": "/gl-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" },"4902": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/zh-rCN/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + "relUrl": "/gl-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" },"4903": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | 良好 | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | 一般 | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | 差 | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | 无 | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Good | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Fair | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Bad | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | None | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/zh-rCN/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + "relUrl": "/gl-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" },"4904": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/zh-rCN/user/signal-meter.html#4-what-this-means-for-you" + "relUrl": "/gl-rES/user/signal-meter.html#4-what-this-means-for-you" },"4905": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/zh-rCN/user/signal-meter.html#where-signal-information-appears" + "relUrl": "/gl-rES/user/signal-meter.html#where-signal-information-appears" },"4906": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#related-topics", - "relUrl": "/zh-rCN/user/signal-meter.html#related-topics" + "relUrl": "/gl-rES/user/signal-meter.html#related-topics" },"4907": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/srp/user/signal-meter.html", + "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html", - "relUrl": "/srp/user/signal-meter.html" + "relUrl": "/tr-rTR/user/signal-meter.html" },"4908": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/srp/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + "relUrl": "/tr-rTR/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" },"4909": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/srp/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + "relUrl": "/tr-rTR/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" },"4910": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Ниво | Bars | Criteria | Meaning | . | Добро | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Прихватљив | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Лош | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Ништа | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | İyi | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | İdare Eder | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Kötü | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Yok | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/srp/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + "relUrl": "/tr-rTR/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" },"4911": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/srp/user/signal-meter.html#4-what-this-means-for-you" + "relUrl": "/tr-rTR/user/signal-meter.html#4-what-this-means-for-you" },"4912": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/srp/user/signal-meter.html#where-signal-information-appears" + "relUrl": "/tr-rTR/user/signal-meter.html#where-signal-information-appears" },"4913": { "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#related-topics", - "relUrl": "/srp/user/signal-meter.html#related-topics" + "relUrl": "/tr-rTR/user/signal-meter.html#related-topics" },"4914": { "doc": "How the Meshtastic Signal Meter Works", "title": "How the Meshtastic Signal Meter Works", "content": "The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the “bars” on a traditional cell phone or WiFi router. Most consumer devices simply measure how “loud” a signal is. However, because Meshtastic uses LoRa (Long Range) technology, its signal meter measures how clear the signal is, relative to the specific settings your mesh is using. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html", + "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html", - "relUrl": "/sq-rAL/user/signal-meter.html" + "relUrl": "/es-rES/user/signal-meter.html" },"4915": { "doc": "How the Meshtastic Signal Meter Works", "title": "1. The Two Metrics: “Loudness” vs. “Clarity”", "content": "Every time the LoRa radio chip receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator): The loudness of the raw power hitting your antenna. | SNR (Signal-to-Noise Ratio): The clarity of the signal compared to the background static. | . 💡 Tip: Here’s an analogy — imagine you are trying to hear a friend talking to you. | RSSI is how loud their voice is. | The Noise Floor is the background noise in the room (air conditioning, other people talking, traffic). | SNR is how easily you can distinguish your friend’s voice from the background noise. | . If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can’t understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR). ", - "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", + "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity", - "relUrl": "/sq-rAL/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" + "relUrl": "/es-rES/user/signal-meter.html#1-the-two-metrics-loudness-vs-clarity" },"4916": { "doc": "How the Meshtastic Signal Meter Works", "title": "2. The Magic of LoRa: Hearing “Below the Noise Floor”", "content": "For standard radios (like FM or WiFi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static. LoRa is special. It uses “Spread Spectrum” modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep underneath the background noise. This is why you will frequently see negative SNR numbers in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static). Depending on which Meshtastic preset you are using (e.g., LongFast vs. ShortFast), the radio has a specific SNR Limit — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", + "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor", - "relUrl": "/sq-rAL/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" + "relUrl": "/es-rES/user/signal-meter.html#2-the-magic-of-lora-hearing-below-the-noise-floor" },"4917": { "doc": "How the Meshtastic Signal Meter Works", "title": "3. How the Signal Meter Calculates Quality", - "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Mirë | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Mesatar | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | I Keq | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Asnjë | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", + "content": "The app rates your signal quality (None, Bad, Fair, or Good) from SNR alone, measured relative to the preset’s SNR Limit — the demodulation floor described above. It deliberately does not factor RSSI into the rating: without the local noise floor, RSSI cannot tell you whether a signal is actually decodable, so SNR-versus-the-preset-limit is the meaningful measure. (RSSI is still displayed to you elsewhere.) . Because the rating is relative to the preset limit, the same SNR can rate differently on different presets — -15 dB is healthy on LongSlow but unusable on ShortFast. Letting limit be the active preset’s SNR Limit, here is how the app picks the bars (or color): . | Level | Bars | Criteria | Meaning | . | Bien | 3 | SNR above the preset’s limit | Signal is comfortably above the demodulation floor — healthy connection. | . | Aceptable | 2 | less than 5.5 dB below the limit | Decodable, but getting close to the floor. | . | Mal | 1 | 5.5 dB to 7.5 dB below the limit | At the very edge of what the preset can recover. | . | Ninguna | 0 | more than 7.5 dB below the limit | Below the floor — transmission lost to noise. | . Note: The fixed SNR thresholds you may have seen elsewhere (-7 dB / -15 dB) are now only used for coloring individual hops in traceroute results — not for the per-node signal meter described here. ", + "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality", - "relUrl": "/sq-rAL/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" + "relUrl": "/es-rES/user/signal-meter.html#3-how-the-signal-meter-calculates-quality" },"4918": { "doc": "How the Meshtastic Signal Meter Works", "title": "4. What This Means for You", "content": "Because Meshtastic’s meter acts as a “Clarity Meter”, it behaves differently than what most people expect: . 💡 Tip: Don’t panic over low RSSI. You might see a seemingly terrible RSSI value like -118 dBm. On a cell phone, you would have zero bars. But if you have an SNR of +2 dB, Meshtastic will still show a strong signal! The library is quiet, so the whisper is heard perfectly. ⚠️ Warning: Watch out for local noise. If you hook up a massive antenna and see a great RSSI (e.g., -90 dBm) but your signal meter is only showing 1 Bar (Bad), you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#4-what-this-means-for-you", + "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#4-what-this-means-for-you", - "relUrl": "/sq-rAL/user/signal-meter.html#4-what-this-means-for-you" + "relUrl": "/es-rES/user/signal-meter.html#4-what-this-means-for-you" },"4919": { "doc": "How the Meshtastic Signal Meter Works", "title": "Where Signal Information Appears", "content": "In the app, signal data is shown in several places: . | Node list — signal bars icon next to each node | Node detail — SNR, RSSI, and signal quality in the device metrics section | Traceroute — per-hop signal quality for each relay node | Signal metrics — historical SNR and RSSI data in the metrics charts | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#where-signal-information-appears", + "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#where-signal-information-appears", - "relUrl": "/sq-rAL/user/signal-meter.html#where-signal-information-appears" + "relUrl": "/es-rES/user/signal-meter.html#where-signal-information-appears" },"4920": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#related-topics", - "relUrl": "/sq-rAL/user/signal-meter.html#related-topics" + "relUrl": "/es-rES/user/signal-meter.html#related-topics" },"4921": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/is-rIS/user/tak.html", - - "relUrl": "/is-rIS/user/tak.html" - },"4922": { - "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" - },"4923": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Lýsing | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"4924": { - "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" - },"4925": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#tak-identity", - - "relUrl": "/is-rIS/user/tak.html#tak-identity" - },"4926": { - "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" - },"4927": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#usage-with-atak", - - "relUrl": "/is-rIS/user/tak.html#usage-with-atak" - },"4928": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"4929": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#security-considerations", - - "relUrl": "/is-rIS/user/tak.html#security-considerations" - },"4930": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#related-topics", - - "relUrl": "/is-rIS/user/tak.html#related-topics" - },"4931": { - "doc": "TAK 連携", - "title": "TAK 連携", - "content": "Meshtastic は Team Awareness Kit（TAK）エコシステムと連携し、Meshtastic のメッシュデバイスと、ATAK や WinTAK などの TAK アプリケーションとの相互運用を可能にします。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html", - - "relUrl": "/ja-rJP/user/tak.html" - },"4932": { - "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#概要" - },"4933": { - "doc": "TAK 連携", - "title": "セットアップ", - "content": "前提条件 . | ATAK（Android Team Awareness Kit）または WinTAK がインストールされていること | Meshtastic ATAK プラグインがインストールされていること | Meshtastic 無線機で TAK モジュールが有効になっていること | . 設定 . | 「設定 → モジュール設定 → TAK」に移動します。 | TAK モジュールを有効にします。 | TAK のチーム／グループ設定を構成します： | . | 設定項目 | 説明 | . | 有効 | TAK 相互運用を有効化 | . | モード | TAK 互換の出力モード | . ATAK プラグインのセットアップ . | プラグインリポジトリから Meshtastic ATAK プラグインをインストールします。 | ATAK を開き、Meshtastic プラグインを有効にします。 | プラグインは、ATAK とメッシュネットワークの間でメッセージを橋渡しします。 | . ローカル TAK サーバー . アプリはローカル TAK サーバーを実行することもでき、同じデバイス上の ATAK／iTAK が、リモートの TAK サーバーなしで直接接続できます。 サーバーは localhost のみ（127.0.0.1:8089）にバインドし、相互証明書認証（mTLS）による TLS を使用するため、ネットワーク上の他のデバイスからは到達できません。 「設定 → モジュール設定 → TAK → TAK サーバー」を開きます： . | ローカル TAK サーバーを有効化：同じデバイスからの ATAK／iTAK 接続用に、ポート 8089 でループバック専用の mTLS サーバーを起動します。 | 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#セットアップ" - },"4934": { - "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-の役割" - },"4935": { - "doc": "TAK 連携", - "title": "TAK のアイデンティティ", - "content": "TAK の役割を使用すると、ノードは TAK のマップに表示されるアイデンティティ情報をブロードキャストします： . | 設定項目 | 説明 | . | チームカラー | TAK のマップ上でのチームの色（例：ブルー、レッド、シアン、グリーン） | . | メンバーロール | 運用上の役割（チームメンバー、チームリード、HQ、メディック、RTO など） | . これらの設定は、TAK モジュールが有効なときに「設定 → モジュール設定 → TAK」に表示されます。 TAK のコールサインは別個の設定ではありません。Meshtastic のノード名から自動的に導かれます。 . 💡 ヒント： チーム／役割の色は、TAK の標準的な所属色です。 一貫したチーム割り当てを使うよう、TAK チームと調整してください。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html#tak-%E3%81%AE%E3%82%A2%E3%82%A4%E3%83%87%E3%83%B3%E3%83%86%E3%82%A3%E3%83%86%E3%82%A3", - - "relUrl": "/ja-rJP/user/tak.html#tak-のアイデンティティ" - },"4936": { - "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" - },"4937": { - "doc": "TAK 連携", - "title": "ATAK での使用", - "content": "設定が完了すると： . | Meshtastic のノードが、コールサインのラベル付きで ATAK のマップにマーカーとして表示されます | チャットメッセージを、メッシュと TAK ネットワークの間で橋渡しできます | 位置の更新が、Meshtastic と TAK の間で双方向に流れます | TAK Tracker のノードは自動的に PLI をブロードキャストします。ATAK 側の設定なしで、その位置が ATAK のマップに表示されます | . ⚠️ 注意： TAK 連携には、特定のノードの役割とモジュールの設定が必要です。 標準のクライアントノードは、自動的には TAK の運用に参加しません。 . ", - "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-での使用" - },"4938": { - "doc": "TAK 連携", - "title": "トラブルシューティング", - "content": "| 問題 | 原因 | 解決策 | . | ノードが ATAK のマップに表示されない | TAK モジュールが無効、または役割が正しくない | TAK モジュールが有効で、ノードの役割が TAK または TAK Tracker になっているか確認する | . | 位置の更新が古い | GPS 測位が失われた、または間隔が長すぎる | GPS の状態を確認し、位置情報設定で位置のブロードキャスト間隔を短くする | . | ATAK プラグインが「切断」と表示する | BLE 接続が失われた、またはプラグインがクラッシュした | Meshtastic アプリで Bluetooth を再接続し、その後 ATAK プラグインを再起動する | . | 図形、マーカー、ルートが橋渡しされない | 送信側のノードがレガシーな 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#トラブルシューティング" - },"4939": { - "doc": "TAK 連携", - "title": "セキュリティに関する注意", - "content": ". | TAK データは、あなたの位置とコールサインの情報を共有します | 機密性の高い環境で TAK を使用する場合は、チャンネルの暗号化を設定してください | TAK モジュールは、他の Meshtastic メッセージと同じチャンネル暗号化に従います | . ", - "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#セキュリティに関する注意" - },"4940": { - "doc": "TAK 連携", - "title": "関連トピック", - "content": ". | 設定：モジュールと管理：TAK モジュールの設定 | ノード：ノードリストの TAK と TAK Tracker の役割 | マップとウェイポイント：マップ上のノードの位置 | ATAK プラグインガイド：meshtastic.org にある詳細な ATAK セットアップ | . ", - "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#関連トピック" - },"4941": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/ca-rES/user/tak.html", - - "relUrl": "/ca-rES/user/tak.html" - },"4942": { - "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" - },"4943": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Descripció | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"4944": { - "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" - },"4945": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#tak-identity", - - "relUrl": "/ca-rES/user/tak.html#tak-identity" - },"4946": { - "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" - },"4947": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#usage-with-atak", - - "relUrl": "/ca-rES/user/tak.html#usage-with-atak" - },"4948": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"4949": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#security-considerations", - - "relUrl": "/ca-rES/user/tak.html#security-considerations" - },"4950": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#related-topics", - - "relUrl": "/ca-rES/user/tak.html#related-topics" - },"4951": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html", - - "relUrl": "/sr-rLatn/user/tak.html" - },"4952": { - "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" - },"4953": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Опис | . | Омогућено | Activate TAK interop | . | Мод | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"4954": { - "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" - },"4955": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#tak-identity", - - "relUrl": "/sr-rLatn/user/tak.html#tak-identity" - },"4956": { - "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" - },"4957": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#usage-with-atak", - - "relUrl": "/sr-rLatn/user/tak.html#usage-with-atak" - },"4958": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"4959": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#security-considerations", - - "relUrl": "/sr-rLatn/user/tak.html#security-considerations" - },"4960": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#related-topics", - - "relUrl": "/sr-rLatn/user/tak.html#related-topics" - },"4961": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html", - - "relUrl": "/ko-rKR/user/tak.html" - },"4962": { - "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" - },"4963": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . 설정 . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | 설명 | . | 활성화 | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"4964": { - "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" - },"4965": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#tak-identity", - - "relUrl": "/ko-rKR/user/tak.html#tak-identity" - },"4966": { - "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" - },"4967": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#usage-with-atak", - - "relUrl": "/ko-rKR/user/tak.html#usage-with-atak" - },"4968": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"4969": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#security-considerations", - - "relUrl": "/ko-rKR/user/tak.html#security-considerations" - },"4970": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#related-topics", - - "relUrl": "/ko-rKR/user/tak.html#related-topics" - },"4971": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html", - - "relUrl": "/ro-rRO/user/tak.html" - },"4972": { - "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" - },"4973": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Descriere | . | Activat | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"4974": { - "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" - },"4975": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#tak-identity", - - "relUrl": "/ro-rRO/user/tak.html#tak-identity" - },"4976": { - "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" - },"4977": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#usage-with-atak", - - "relUrl": "/ro-rRO/user/tak.html#usage-with-atak" - },"4978": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"4979": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#security-considerations", - - "relUrl": "/ro-rRO/user/tak.html#security-considerations" - },"4980": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#related-topics", - - "relUrl": "/ro-rRO/user/tak.html#related-topics" - },"4981": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html", - - "relUrl": "/ga-rIE/user/tak.html" - },"4982": { - "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" - },"4983": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Cur síos | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"4984": { - "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" - },"4985": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#tak-identity", - - "relUrl": "/ga-rIE/user/tak.html#tak-identity" - },"4986": { - "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" - },"4987": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#usage-with-atak", - - "relUrl": "/ga-rIE/user/tak.html#usage-with-atak" - },"4988": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"4989": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#security-considerations", - - "relUrl": "/ga-rIE/user/tak.html#security-considerations" - },"4990": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#related-topics", - - "relUrl": "/ga-rIE/user/tak.html#related-topics" - },"4991": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html", - - "relUrl": "/iw-rIL/user/tak.html" - },"4992": { - "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" - },"4993": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | תיאור | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"4994": { - "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" - },"4995": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#tak-identity", - - "relUrl": "/iw-rIL/user/tak.html#tak-identity" - },"4996": { - "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" - },"4997": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#usage-with-atak", - - "relUrl": "/iw-rIL/user/tak.html#usage-with-atak" - },"4998": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"4999": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#security-considerations", - - "relUrl": "/iw-rIL/user/tak.html#security-considerations" - },"5000": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#related-topics", - - "relUrl": "/iw-rIL/user/tak.html#related-topics" - },"5001": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html", - - "relUrl": "/sv-rSE/user/tak.html" - },"5002": { - "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" - },"5003": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Konfiguration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Beskrivning | . | Aktiverad | Activate TAK interop | . | Typ | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5004": { - "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" - },"5005": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#tak-identity", - - "relUrl": "/sv-rSE/user/tak.html#tak-identity" - },"5006": { - "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" - },"5007": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#usage-with-atak", - - "relUrl": "/sv-rSE/user/tak.html#usage-with-atak" - },"5008": { - "doc": "TAK Integration", - "title": "Felsökning", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5009": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#security-considerations", - - "relUrl": "/sv-rSE/user/tak.html#security-considerations" - },"5010": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#related-topics", - - "relUrl": "/sv-rSE/user/tak.html#related-topics" - },"5011": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html", - - "relUrl": "/ht-rHT/user/tak.html" - },"5012": { - "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" - },"5013": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Deskripsyon | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5014": { - "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" - },"5015": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#tak-identity", - - "relUrl": "/ht-rHT/user/tak.html#tak-identity" - },"5016": { - "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" - },"5017": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#usage-with-atak", - - "relUrl": "/ht-rHT/user/tak.html#usage-with-atak" - },"5018": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5019": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#security-considerations", - - "relUrl": "/ht-rHT/user/tak.html#security-considerations" - },"5020": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#related-topics", - - "relUrl": "/ht-rHT/user/tak.html#related-topics" - },"5021": { - "doc": "TAK-integraatio", - "title": "TAK-integraatio", - "content": "Meshtastic integroituu Team Awareness Kit (TAK) -ekosysteemiin, mahdollistaen yhteentoimivuuden Meshtastic-verkkoradioiden ja TAK-sovellusten kuten ATAK:n ja WinTAK:n välillä. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html", - - "relUrl": "/fi-rFI/user/tak.html" - },"5022": { - "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" - },"5023": { - "doc": "TAK-integraatio", - "title": "Asetukset", - "content": "Edellytykset . | ATAK (Android Team Awareness Kit) tai WinTAK asennettuna | Meshtastic ATAK -lisäosa asennettuna | TAK-moduuli käytössä Meshtastic-radiossasi | . Asetukset . | Siirry kohtaan Asetukset → Moduulin asetukset → TAK. | Ota TAK-moduuli käyttöön. | Määritä TAK-tiimin/ryhmän asetukset: | . | Asetus | Kuvaus | . | Käytössä | Ota TAK-yhteentoimivuus käyttöön | . | Tila | TAK-yhteensopiva lähtötila | . ATAK-lisäosan asennus . | Asenna Meshtastic ATAK -lisäosa lisäosien lähteestä. | Avaa ATAK ja ota Meshtastic-lisäosa käyttöön. | Lisäosa välittää viestejä ATAK:n ja mesh-verkkosi välillä. | . Paikallinen TAK-palvelin . Sovellus voi käyttää myös paikallista TAK-palvelinta, jolloin samalla laitteella oleva ATAK/iTAK voi muodostaa siihen suoran yhteyden ilman etäpalvelinta. Palvelin kuuntelee vain paikallisia yhteyksiä (127.0.0.1:8089) ja käyttää TLS:ää molemminpuolisella varmenteiden todentamisella. Avaa Asetukset → Moduuliasetukset → TAK → TAK-palvelin: . | Ota paikallinen TAK-palvelin käyttöön – käynnistää vain paikallisia yhteyksiä kuuntelevan mTLS-palvelimen portissa 8089 samalla laitteella toimivaa ATAK-/iTAK-yhteyttä varten. | 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" - },"5024": { - "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" - },"5025": { - "doc": "TAK-integraatio", - "title": "TAK-identiteetti", - "content": "Kun käytät TAK-rooleja, radiosi lähettää identiteettitietoja, jotka näkyvät TAK-kartoilla: . | Asetus | Kuvaus | . | Tiimin väri | TAK-kartan tiimiväri (esim. sininen, punainen, syaani, vihreä) | . | Jäsenen rooli | Operatiivinen roolisi (tiimin jäsen, tiimin johtaja, esikunta, ensihoitaja, viestivastaava jne.) | . Nämä asetukset näkyvät kohdassa Asetukset → Moduulin asetukset → TAK, kun TAK-moduuli on käytössä. 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. Koordinoi TAK-tiimisi kanssa yhtenäisten tiimimääritysten käyttämiseksi. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#tak-identiteetti", - - "relUrl": "/fi-rFI/user/tak.html#tak-identiteetti" - },"5026": { - "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" - },"5027": { - "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 | . ⚠️ Huom: TAK-integraatio vaatii tietyt laiteroolit ja moduuliasetukset. Tavalliset client-laitteet eivät osallistu TAK-toimintoihin automaattisesti. ", - "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" - },"5028": { - "doc": "TAK-integraatio", - "title": "Vianetsintä", - "content": "| Ongelma | Syy | Ratkaisu | . | Radio ei näy ATAK-kartalla | TAK-moduuli pois käytöstä tai väärä rooli | Varmista, että TAK-moduuli on käytössä ja rooli on joko TAK tai TAK Tracker | . | 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-lisäosa näyttää “yhteys katkennut” | Bluetooth-yhteys katkennut tai lisäosa on kaatunut | Yhdistä Bluetooth uudelleen Meshtastic-sovelluksessa ja käynnistä ATAK-lisäosa uudelleen | . | 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ä" - },"5029": { - "doc": "TAK-integraatio", - "title": "Tietoturvahuomiot", - "content": ". | TAK-data sisältää sijainti- ja kutsutunnustietoja | Varmista, että kanavan salaus on oikein määritetty, kun käytät TAK:ia arkaluonteisissa ympäristöissä | TAK-moduuli noudattaa samaa kanavasalausta kuin muut Meshtastic-viestit | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#tietoturvahuomiot", - - "relUrl": "/fi-rFI/user/tak.html#tietoturvahuomiot" - },"5030": { - "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 | ATAK-liitännäisen opas – yksityiskohtaiset ATAK-asennusohjeet meshtastic.org -sivustolla | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#aiheeseen-liittyv%C3%A4t-aiheet", - - "relUrl": "/fi-rFI/user/tak.html#aiheeseen-liittyvät-aiheet" - },"5031": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/gl-rES/user/tak.html", - - "relUrl": "/gl-rES/user/tak.html" - },"5032": { - "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" - },"5033": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Descrición | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5034": { - "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" - },"5035": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#tak-identity", - - "relUrl": "/gl-rES/user/tak.html#tak-identity" - },"5036": { - "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" - },"5037": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#usage-with-atak", - - "relUrl": "/gl-rES/user/tak.html#usage-with-atak" - },"5038": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5039": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#security-considerations", - - "relUrl": "/gl-rES/user/tak.html#security-considerations" - },"5040": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#related-topics", - - "relUrl": "/gl-rES/user/tak.html#related-topics" - },"5041": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html", - - "relUrl": "/uk-rUA/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/uk-rUA/user/tak.html#overview", - - "relUrl": "/uk-rUA/user/tak.html#overview" - },"5043": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Налаштування . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Опис | . | Увімкнено | Activate TAK interop | . | Режим | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5044": { - "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" - },"5045": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#tak-identity", - - "relUrl": "/uk-rUA/user/tak.html#tak-identity" - },"5046": { - "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" - },"5047": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#usage-with-atak", - - "relUrl": "/uk-rUA/user/tak.html#usage-with-atak" - },"5048": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5049": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#security-considerations", - - "relUrl": "/uk-rUA/user/tak.html#security-considerations" - },"5050": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#related-topics", - - "relUrl": "/uk-rUA/user/tak.html#related-topics" - },"5051": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic lässt sich in das Team Awareness Kit (TAK)-Ökosystem integrieren und ermöglicht so die Interoperabilität zwischen Meshtastic Geräten und TAK-Anwendungen wie ATAK und WinTAK. ", "url": "/Meshtastic-Android/main/de-rDE/user/tak.html", "relUrl": "/de-rDE/user/tak.html" - },"5052": { + },"4922": { "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" - },"5053": { + },"4923": { "doc": "TAK Integration", "title": "Einstellungen", "content": "Voraussetzungen . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Einstellungen . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Einstellung | Beschreibung | . | Aktiviert | Activate TAK interop | . | Betriebsmodus | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5054": { + },"4924": { "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" - },"5055": { + },"4925": { "doc": "TAK Integration", "title": "TAK Identity", "content": "When using TAK roles, your node broadcasts identity information that appears on TAK maps: . | Einstellung | Beschreibung | . | Teamfarbe | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Mitgliedsrolle | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#tak-identity", "relUrl": "/de-rDE/user/tak.html#tak-identity" - },"5056": { + },"4926": { "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" - },"5057": { + },"4927": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#usage-with-atak", "relUrl": "/de-rDE/user/tak.html#usage-with-atak" - },"5058": { + },"4928": { "doc": "TAK Integration", "title": "Fehlerbehebung", "content": "| Problem | Ursache | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5059": { + },"4929": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#security-considerations", "relUrl": "/de-rDE/user/tak.html#security-considerations" - },"5060": { + },"4930": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#related-topics", "relUrl": "/de-rDE/user/tak.html#related-topics" - },"5061": { + },"4931": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html", + "url": "/Meshtastic-Android/main/ca-rES/user/tak.html", - "relUrl": "/hr-rHR/user/tak.html" - },"5062": { + "relUrl": "/ca-rES/user/tak.html" + },"4932": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#overview", - "relUrl": "/hr-rHR/user/tak.html#overview" - },"5063": { + "relUrl": "/ca-rES/user/tak.html#overview" + },"4933": { "doc": "TAK Integration", "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Opis | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Descripció | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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": "/hr-rHR/user/tak.html#setup" - },"5064": { + "relUrl": "/ca-rES/user/tak.html#setup" + },"4934": { "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", + "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": "/hr-rHR/user/tak.html#tak-roles" - },"5065": { + "relUrl": "/ca-rES/user/tak.html#tak-roles" + },"4935": { "doc": "TAK Integration", "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#tak-identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#tak-identity", - "relUrl": "/hr-rHR/user/tak.html#tak-identity" - },"5066": { + "relUrl": "/ca-rES/user/tak.html#tak-identity" + },"4936": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#wire-format-v1--v2", - "relUrl": "/hr-rHR/user/tak.html#wire-format-v1--v2" - },"5067": { + "relUrl": "/ca-rES/user/tak.html#wire-format-v1--v2" + },"4937": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#usage-with-atak", + "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#usage-with-atak", - "relUrl": "/hr-rHR/user/tak.html#usage-with-atak" - },"5068": { + "relUrl": "/ca-rES/user/tak.html#usage-with-atak" + },"4938": { "doc": "TAK Integration", "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#troubleshooting", - "relUrl": "/hr-rHR/user/tak.html#troubleshooting" - },"5069": { + "relUrl": "/ca-rES/user/tak.html#troubleshooting" + },"4939": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#security-considerations", + "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#security-considerations", - "relUrl": "/hr-rHR/user/tak.html#security-considerations" - },"5070": { + "relUrl": "/ca-rES/user/tak.html#security-considerations" + },"4940": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#related-topics", + "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#related-topics", - "relUrl": "/hr-rHR/user/tak.html#related-topics" - },"5071": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html", - - "relUrl": "/lt-rLT/user/tak.html" - },"5072": { - "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" - },"5073": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Aprašymas | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5074": { - "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" - },"5075": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#tak-identity", - - "relUrl": "/lt-rLT/user/tak.html#tak-identity" - },"5076": { - "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" - },"5077": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#usage-with-atak", - - "relUrl": "/lt-rLT/user/tak.html#usage-with-atak" - },"5078": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5079": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#security-considerations", - - "relUrl": "/lt-rLT/user/tak.html#security-considerations" - },"5080": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#related-topics", - - "relUrl": "/lt-rLT/user/tak.html#related-topics" - },"5081": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/en/user/tak.html", - - "relUrl": "/en/user/tak.html" - },"5082": { - "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" - },"5083": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Description | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5084": { - "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" - },"5085": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/en/user/tak.html#tak-identity", - - "relUrl": "/en/user/tak.html#tak-identity" - },"5086": { - "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" - },"5087": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/en/user/tak.html#usage-with-atak", - - "relUrl": "/en/user/tak.html#usage-with-atak" - },"5088": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5089": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/en/user/tak.html#security-considerations", - - "relUrl": "/en/user/tak.html#security-considerations" - },"5090": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/en/user/tak.html#related-topics", - - "relUrl": "/en/user/tak.html#related-topics" - },"5091": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html", - - "relUrl": "/hu-rHU/user/tak.html" - },"5092": { - "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" - },"5093": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Leírás | . | Engedélyezve | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5094": { - "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" - },"5095": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#tak-identity", - - "relUrl": "/hu-rHU/user/tak.html#tak-identity" - },"5096": { - "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" - },"5097": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#usage-with-atak", - - "relUrl": "/hu-rHU/user/tak.html#usage-with-atak" - },"5098": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5099": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#security-considerations", - - "relUrl": "/hu-rHU/user/tak.html#security-considerations" - },"5100": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#related-topics", - - "relUrl": "/hu-rHU/user/tak.html#related-topics" - },"5101": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html", - - "relUrl": "/bg-rBG/user/tak.html" - },"5102": { - "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#преглед" - },"5103": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Конфигурация . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Настройка | Описание | . | Активиран | Activate TAK interop | . | Режим | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5104": { - "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" - },"5105": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that appears on TAK maps: . | Настройка | Описание | . | Цвят на екипа | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Роля на члена | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#tak-identity", - - "relUrl": "/bg-rBG/user/tak.html#tak-identity" - },"5106": { - "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" - },"5107": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#usage-with-atak", - - "relUrl": "/bg-rBG/user/tak.html#usage-with-atak" - },"5108": { - "doc": "TAK Integration", - "title": "Отстраняване на неизправности", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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#отстраняване-на-неизправности" - },"5109": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#security-considerations", - - "relUrl": "/bg-rBG/user/tak.html#security-considerations" - },"5110": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#related-topics", - - "relUrl": "/bg-rBG/user/tak.html#related-topics" - },"5111": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html", - - "relUrl": "/sl-rSI/user/tak.html" - },"5112": { - "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" - },"5113": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Opis | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5114": { - "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" - },"5115": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#tak-identity", - - "relUrl": "/sl-rSI/user/tak.html#tak-identity" - },"5116": { - "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" - },"5117": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#usage-with-atak", - - "relUrl": "/sl-rSI/user/tak.html#usage-with-atak" - },"5118": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5119": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#security-considerations", - - "relUrl": "/sl-rSI/user/tak.html#security-considerations" - },"5120": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#related-topics", - - "relUrl": "/sl-rSI/user/tak.html#related-topics" - },"5121": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html", - - "relUrl": "/pt-rPT/user/tak.html" - },"5122": { - "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" - },"5123": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuração . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Descrição | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5124": { - "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" - },"5125": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#tak-identity", - - "relUrl": "/pt-rPT/user/tak.html#tak-identity" - },"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/pt-rPT/user/tak.html#wire-format-v1--v2", - - "relUrl": "/pt-rPT/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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#usage-with-atak", - - "relUrl": "/pt-rPT/user/tak.html#usage-with-atak" - },"5128": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5129": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#security-considerations", - - "relUrl": "/pt-rPT/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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#related-topics", - - "relUrl": "/pt-rPT/user/tak.html#related-topics" - },"5131": { + "relUrl": "/ca-rES/user/tak.html#related-topics" + },"4941": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", "url": "/Meshtastic-Android/main/be-rBY/user/tak.html", "relUrl": "/be-rBY/user/tak.html" - },"5132": { + },"4942": { "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#абзор" - },"5133": { + },"4943": { "doc": "TAK Integration", "title": "Setup", "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Конфигурация . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Апісанне | . | Уключана | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5134": { + },"4944": { "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" - },"5135": { + },"4945": { "doc": "TAK Integration", "title": "TAK Identity", "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#tak-identity", "relUrl": "/be-rBY/user/tak.html#tak-identity" - },"5136": { + },"4946": { "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" - },"5137": { + },"4947": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#usage-with-atak", "relUrl": "/be-rBY/user/tak.html#usage-with-atak" - },"5138": { + },"4948": { "doc": "TAK Integration", "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5139": { + },"4949": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#security-considerations", "relUrl": "/be-rBY/user/tak.html#security-considerations" - },"5140": { + },"4950": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#related-topics", "relUrl": "/be-rBY/user/tak.html#related-topics" - },"5141": { + },"4951": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html", + + "relUrl": "/uk-rUA/user/tak.html" + },"4952": { + "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" + },"4953": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Налаштування . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Опис | . | Увімкнено | Activate TAK interop | . | Режим | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"4954": { + "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" + },"4955": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#tak-identity", + + "relUrl": "/uk-rUA/user/tak.html#tak-identity" + },"4956": { + "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" + },"4957": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#usage-with-atak", + + "relUrl": "/uk-rUA/user/tak.html#usage-with-atak" + },"4958": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"4959": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#security-considerations", + + "relUrl": "/uk-rUA/user/tak.html#security-considerations" + },"4960": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#related-topics", + + "relUrl": "/uk-rUA/user/tak.html#related-topics" + },"4961": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html", + + "relUrl": "/zh-rCN/user/tak.html" + },"4962": { + "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#总览" + },"4963": { + "doc": "TAK Integration", + "title": "Setup", + "content": "前置条件 . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | 说明 | . | Enabled | Activate TAK interop | . | 模式 | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"4964": { + "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" + },"4965": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that appears on TAK maps: . | Setting | 说明 | . | 队伍颜色 | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | 成员角色 | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#tak-identity", + + "relUrl": "/zh-rCN/user/tak.html#tak-identity" + },"4966": { + "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" + },"4967": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#usage-with-atak", + + "relUrl": "/zh-rCN/user/tak.html#usage-with-atak" + },"4968": { + "doc": "TAK Integration", + "title": "问题排查", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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#问题排查" + },"4969": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#security-considerations", + + "relUrl": "/zh-rCN/user/tak.html#security-considerations" + },"4970": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#related-topics", + + "relUrl": "/zh-rCN/user/tak.html#related-topics" + },"4971": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html", + + "relUrl": "/bg-rBG/user/tak.html" + },"4972": { + "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#преглед" + },"4973": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Конфигурация . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Настройка | Описание | . | Активиран | Activate TAK interop | . | Режим | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"4974": { + "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" + },"4975": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that appears on TAK maps: . | Настройка | Описание | . | Цвят на екипа | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Роля на члена | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#tak-identity", + + "relUrl": "/bg-rBG/user/tak.html#tak-identity" + },"4976": { + "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" + },"4977": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#usage-with-atak", + + "relUrl": "/bg-rBG/user/tak.html#usage-with-atak" + },"4978": { + "doc": "TAK Integration", + "title": "Отстраняване на неизправности", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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#отстраняване-на-неизправности" + },"4979": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#security-considerations", + + "relUrl": "/bg-rBG/user/tak.html#security-considerations" + },"4980": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#related-topics", + + "relUrl": "/bg-rBG/user/tak.html#related-topics" + },"4981": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html", + + "relUrl": "/zh-rTW/user/tak.html" + },"4982": { + "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#概觀" + },"4983": { + "doc": "TAK Integration", + "title": "設定", + "content": "先決條件 . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . 設定 . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | 設定 | 描述說明 | . | 已啟用 | Activate TAK interop | . | 模式 | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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#設定" + },"4984": { + "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" + },"4985": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that appears on TAK maps: . | 設定 | 描述說明 | . | 隊伍顏色 | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | 隊員角色 | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#tak-identity", + + "relUrl": "/zh-rTW/user/tak.html#tak-identity" + },"4986": { + "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" + },"4987": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#usage-with-atak", + + "relUrl": "/zh-rTW/user/tak.html#usage-with-atak" + },"4988": { + "doc": "TAK Integration", + "title": "故障排除", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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#故障排除" + },"4989": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#security-considerations", + + "relUrl": "/zh-rTW/user/tak.html#security-considerations" + },"4990": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#related-topics", + + "relUrl": "/zh-rTW/user/tak.html#related-topics" + },"4991": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html", + + "relUrl": "/sr-rLatn/user/tak.html" + },"4992": { + "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" + },"4993": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Опис | . | Омогућено | Activate TAK interop | . | Мод | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"4994": { + "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" + },"4995": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#tak-identity", + + "relUrl": "/sr-rLatn/user/tak.html#tak-identity" + },"4996": { + "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" + },"4997": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#usage-with-atak", + + "relUrl": "/sr-rLatn/user/tak.html#usage-with-atak" + },"4998": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"4999": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#security-considerations", + + "relUrl": "/sr-rLatn/user/tak.html#security-considerations" + },"5000": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#related-topics", + + "relUrl": "/sr-rLatn/user/tak.html#related-topics" + },"5001": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html", + + "relUrl": "/cs-rCZ/user/tak.html" + },"5002": { + "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" + },"5003": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Nastavení . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Nastavení | Popis | . | Povoleno | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5004": { + "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" + },"5005": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#tak-identity", + + "relUrl": "/cs-rCZ/user/tak.html#tak-identity" + },"5006": { + "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" + },"5007": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#usage-with-atak", + + "relUrl": "/cs-rCZ/user/tak.html#usage-with-atak" + },"5008": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5009": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#security-considerations", + + "relUrl": "/cs-rCZ/user/tak.html#security-considerations" + },"5010": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#related-topics", + + "relUrl": "/cs-rCZ/user/tak.html#related-topics" + },"5011": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/en/user/tak.html", + + "relUrl": "/en/user/tak.html" + },"5012": { + "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" + },"5013": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Description | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5014": { + "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" + },"5015": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/en/user/tak.html#tak-identity", + + "relUrl": "/en/user/tak.html#tak-identity" + },"5016": { + "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" + },"5017": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/en/user/tak.html#usage-with-atak", + + "relUrl": "/en/user/tak.html#usage-with-atak" + },"5018": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5019": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/en/user/tak.html#security-considerations", + + "relUrl": "/en/user/tak.html#security-considerations" + },"5020": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/en/user/tak.html#related-topics", + + "relUrl": "/en/user/tak.html#related-topics" + },"5021": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html", + + "relUrl": "/sl-rSI/user/tak.html" + },"5022": { + "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" + },"5023": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Opis | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5024": { + "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" + },"5025": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#tak-identity", + + "relUrl": "/sl-rSI/user/tak.html#tak-identity" + },"5026": { + "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" + },"5027": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#usage-with-atak", + + "relUrl": "/sl-rSI/user/tak.html#usage-with-atak" + },"5028": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5029": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#security-considerations", + + "relUrl": "/sl-rSI/user/tak.html#security-considerations" + },"5030": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#related-topics", + + "relUrl": "/sl-rSI/user/tak.html#related-topics" + },"5031": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/it-rIT/user/tak.html", + + "relUrl": "/it-rIT/user/tak.html" + },"5032": { + "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" + },"5033": { + "doc": "TAK Integration", + "title": "Configurazione", + "content": "Prerequisiti . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configurazione . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Impostazione | Descrizione | . | Abilitato | Activate TAK interop | . | Modalità | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5034": { + "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" + },"5035": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#tak-identity", + + "relUrl": "/it-rIT/user/tak.html#tak-identity" + },"5036": { + "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" + },"5037": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#usage-with-atak", + + "relUrl": "/it-rIT/user/tak.html#usage-with-atak" + },"5038": { + "doc": "TAK Integration", + "title": "Risoluzione problemi", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5039": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#security-considerations", + + "relUrl": "/it-rIT/user/tak.html#security-considerations" + },"5040": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#related-topics", + + "relUrl": "/it-rIT/user/tak.html#related-topics" + },"5041": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html", "relUrl": "/pt-rBR/user/tak.html" - },"5142": { + },"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/pt-rBR/user/tak.html#overview", "relUrl": "/pt-rBR/user/tak.html#overview" - },"5143": { + },"5043": { "doc": "TAK Integration", "title": "Setup", "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Descrição | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5144": { + },"5044": { "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" - },"5145": { + },"5045": { "doc": "TAK Integration", "title": "TAK Identity", "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#tak-identity", "relUrl": "/pt-rBR/user/tak.html#tak-identity" - },"5146": { + },"5046": { "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" - },"5147": { + },"5047": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#usage-with-atak", "relUrl": "/pt-rBR/user/tak.html#usage-with-atak" - },"5148": { + },"5048": { "doc": "TAK Integration", "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5149": { + },"5049": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#security-considerations", "relUrl": "/pt-rBR/user/tak.html#security-considerations" - },"5150": { + },"5050": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#related-topics", "relUrl": "/pt-rBR/user/tak.html#related-topics" - },"5151": { + },"5051": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/el-rGR/user/tak.html", + "url": "/Meshtastic-Android/main/is-rIS/user/tak.html", - "relUrl": "/el-rGR/user/tak.html" - },"5152": { + "relUrl": "/is-rIS/user/tak.html" + },"5052": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#overview", - "relUrl": "/el-rGR/user/tak.html#overview" - },"5153": { + "relUrl": "/is-rIS/user/tak.html#overview" + },"5053": { "doc": "TAK Integration", "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Περιγραφή | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Lýsing | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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": "/el-rGR/user/tak.html#setup" - },"5154": { + "relUrl": "/is-rIS/user/tak.html#setup" + },"5054": { "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", + "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": "/el-rGR/user/tak.html#tak-roles" - },"5155": { + "relUrl": "/is-rIS/user/tak.html#tak-roles" + },"5055": { "doc": "TAK Integration", "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#tak-identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#tak-identity", - "relUrl": "/el-rGR/user/tak.html#tak-identity" - },"5156": { + "relUrl": "/is-rIS/user/tak.html#tak-identity" + },"5056": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#wire-format-v1--v2", - "relUrl": "/el-rGR/user/tak.html#wire-format-v1--v2" - },"5157": { + "relUrl": "/is-rIS/user/tak.html#wire-format-v1--v2" + },"5057": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#usage-with-atak", + "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#usage-with-atak", - "relUrl": "/el-rGR/user/tak.html#usage-with-atak" - },"5158": { + "relUrl": "/is-rIS/user/tak.html#usage-with-atak" + },"5058": { "doc": "TAK Integration", "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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", + "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#troubleshooting", - "relUrl": "/el-rGR/user/tak.html#troubleshooting" - },"5159": { + "relUrl": "/is-rIS/user/tak.html#troubleshooting" + },"5059": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#security-considerations", + "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#security-considerations", - "relUrl": "/el-rGR/user/tak.html#security-considerations" - },"5160": { + "relUrl": "/is-rIS/user/tak.html#security-considerations" + },"5060": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#related-topics", + "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#related-topics", - "relUrl": "/el-rGR/user/tak.html#related-topics" - },"5161": { + "relUrl": "/is-rIS/user/tak.html#related-topics" + },"5061": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/es-rES/user/tak.html", + "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html", - "relUrl": "/es-rES/user/tak.html" - },"5162": { - "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" - },"5163": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuración . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Descripción | . | Habilitado | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5164": { - "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" - },"5165": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/es-rES/user/tak.html#tak-identity", - - "relUrl": "/es-rES/user/tak.html#tak-identity" - },"5166": { - "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" - },"5167": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/es-rES/user/tak.html#usage-with-atak", - - "relUrl": "/es-rES/user/tak.html#usage-with-atak" - },"5168": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5169": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/es-rES/user/tak.html#security-considerations", - - "relUrl": "/es-rES/user/tak.html#security-considerations" - },"5170": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/es-rES/user/tak.html#related-topics", - - "relUrl": "/es-rES/user/tak.html#related-topics" - },"5171": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html", - - "relUrl": "/tr-rTR/user/tak.html" - },"5172": { - "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ış" - },"5173": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Yapılandırma . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Açıklaması | . | Açık | Activate TAK interop | . | Mod | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5174": { - "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" - },"5175": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#tak-identity", - - "relUrl": "/tr-rTR/user/tak.html#tak-identity" - },"5176": { - "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" - },"5177": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#usage-with-atak", - - "relUrl": "/tr-rTR/user/tak.html#usage-with-atak" - },"5178": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5179": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#security-considerations", - - "relUrl": "/tr-rTR/user/tak.html#security-considerations" - },"5180": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#related-topics", - - "relUrl": "/tr-rTR/user/tak.html#related-topics" - },"5181": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/no-rNO/user/tak.html", - - "relUrl": "/no-rNO/user/tak.html" - },"5182": { + "relUrl": "/fr-rFR/user/tak.html" + },"5062": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#overview", - "relUrl": "/no-rNO/user/tak.html#overview" - },"5183": { + "relUrl": "/fr-rFR/user/tak.html#overview" + },"5063": { "doc": "TAK Integration", "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Beskrivelse | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Description | . | Activé | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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": "/no-rNO/user/tak.html#setup" - },"5184": { + "relUrl": "/fr-rFR/user/tak.html#setup" + },"5064": { "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", + "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": "/no-rNO/user/tak.html#tak-roles" - },"5185": { + "relUrl": "/fr-rFR/user/tak.html#tak-roles" + },"5065": { "doc": "TAK Integration", "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#tak-identity", + "content": "When using TAK roles, your node broadcasts identity information that appears on TAK maps: . | Setting | Description | . | Couleur de l’équipe | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Rôle Membre | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#tak-identity", - "relUrl": "/no-rNO/user/tak.html#tak-identity" - },"5186": { + "relUrl": "/fr-rFR/user/tak.html#tak-identity" + },"5066": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#wire-format-v1--v2", - "relUrl": "/no-rNO/user/tak.html#wire-format-v1--v2" - },"5187": { + "relUrl": "/fr-rFR/user/tak.html#wire-format-v1--v2" + },"5067": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#usage-with-atak", + "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#usage-with-atak", - "relUrl": "/no-rNO/user/tak.html#usage-with-atak" - },"5188": { + "relUrl": "/fr-rFR/user/tak.html#usage-with-atak" + },"5068": { "doc": "TAK Integration", "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#troubleshooting", - "relUrl": "/no-rNO/user/tak.html#troubleshooting" - },"5189": { + "relUrl": "/fr-rFR/user/tak.html#troubleshooting" + },"5069": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#security-considerations", + "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#security-considerations", - "relUrl": "/no-rNO/user/tak.html#security-considerations" - },"5190": { + "relUrl": "/fr-rFR/user/tak.html#security-considerations" + },"5070": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#related-topics", + "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#related-topics", - "relUrl": "/no-rNO/user/tak.html#related-topics" - },"5191": { + "relUrl": "/fr-rFR/user/tak.html#related-topics" + },"5071": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/srp/user/tak.html", + + "relUrl": "/srp/user/tak.html" + },"5072": { + "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" + },"5073": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Опис | . | Омогућено | Activate TAK interop | . | Мод | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5074": { + "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" + },"5075": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/srp/user/tak.html#tak-identity", + + "relUrl": "/srp/user/tak.html#tak-identity" + },"5076": { + "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" + },"5077": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/srp/user/tak.html#usage-with-atak", + + "relUrl": "/srp/user/tak.html#usage-with-atak" + },"5078": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5079": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/srp/user/tak.html#security-considerations", + + "relUrl": "/srp/user/tak.html#security-considerations" + },"5080": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/srp/user/tak.html#related-topics", + + "relUrl": "/srp/user/tak.html#related-topics" + },"5081": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html", + + "relUrl": "/sk-rSK/user/tak.html" + },"5082": { + "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" + },"5083": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Popis | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5084": { + "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" + },"5085": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#tak-identity", + + "relUrl": "/sk-rSK/user/tak.html#tak-identity" + },"5086": { + "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" + },"5087": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#usage-with-atak", + + "relUrl": "/sk-rSK/user/tak.html#usage-with-atak" + },"5088": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5089": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#security-considerations", + + "relUrl": "/sk-rSK/user/tak.html#security-considerations" + },"5090": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#related-topics", + + "relUrl": "/sk-rSK/user/tak.html#related-topics" + },"5091": { + "doc": "TAK-integraatio", + "title": "TAK-integraatio", + "content": "Meshtastic integroituu Team Awareness Kit (TAK) -ekosysteemiin, mahdollistaen yhteentoimivuuden Meshtastic-verkkoradioiden ja TAK-sovellusten kuten ATAK:n ja WinTAK:n välillä. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html", + + "relUrl": "/fi-rFI/user/tak.html" + },"5092": { + "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" + },"5093": { + "doc": "TAK-integraatio", + "title": "Asetukset", + "content": "Edellytykset . | ATAK (Android Team Awareness Kit) tai WinTAK asennettuna | Meshtastic ATAK -lisäosa asennettuna | TAK-moduuli käytössä Meshtastic-radiossasi | . Asetukset . | Siirry kohtaan Asetukset → Moduulin asetukset → TAK. | Ota TAK-moduuli käyttöön. | Määritä TAK-tiimin/ryhmän asetukset: | . | Asetus | Kuvaus | . | Käytössä | Ota TAK-yhteentoimivuus käyttöön | . | Tila | TAK-yhteensopiva lähtötila | . ATAK-lisäosan asennus . | Asenna Meshtastic ATAK -lisäosa lisäosien lähteestä. | Avaa ATAK ja ota Meshtastic-lisäosa käyttöön. | Lisäosa välittää viestejä ATAK:n ja mesh-verkkosi välillä. | . Paikallinen TAK-palvelin . Sovellus voi käyttää myös paikallista TAK-palvelinta, jolloin samalla laitteella oleva ATAK/iTAK voi muodostaa siihen suoran yhteyden ilman etäpalvelinta. Palvelin kuuntelee vain paikallisia yhteyksiä (127.0.0.1:8089) ja käyttää TLS:ää molemminpuolisella varmenteiden todentamisella. Avaa Asetukset → Moduuliasetukset → TAK → TAK-palvelin: . | Ota paikallinen TAK-palvelin käyttöön – käynnistää vain paikallisia yhteyksiä kuuntelevan mTLS-palvelimen portissa 8089 samalla laitteella toimivaa ATAK-/iTAK-yhteyttä varten. | 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" + },"5094": { + "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" + },"5095": { + "doc": "TAK-integraatio", + "title": "TAK-identiteetti", + "content": "Kun käytät TAK-rooleja, radiosi lähettää identiteettitietoja, jotka näkyvät TAK-kartoilla: . | Asetus | Kuvaus | . | Tiimin väri | TAK-kartan tiimiväri (esim. sininen, punainen, syaani, vihreä) | . | Jäsenen rooli | Operatiivinen roolisi (tiimin jäsen, tiimin johtaja, esikunta, ensihoitaja, viestivastaava jne.) | . Nämä asetukset näkyvät kohdassa Asetukset → Moduulin asetukset → TAK, kun TAK-moduuli on käytössä. 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. Koordinoi TAK-tiimisi kanssa yhtenäisten tiimimääritysten käyttämiseksi. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#tak-identiteetti", + + "relUrl": "/fi-rFI/user/tak.html#tak-identiteetti" + },"5096": { + "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" + },"5097": { + "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 | . ⚠️ Huom: TAK-integraatio vaatii tietyt laiteroolit ja moduuliasetukset. Tavalliset client-laitteet eivät osallistu TAK-toimintoihin automaattisesti. ", + "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" + },"5098": { + "doc": "TAK-integraatio", + "title": "Vianetsintä", + "content": "| Ongelma | Syy | Ratkaisu | . | Radio ei näy ATAK-kartalla | TAK-moduuli pois käytöstä tai väärä rooli | Varmista, että TAK-moduuli on käytössä ja rooli on joko TAK tai TAK Tracker | . | 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-lisäosa näyttää “yhteys katkennut” | Bluetooth-yhteys katkennut tai lisäosa on kaatunut | Yhdistä Bluetooth uudelleen Meshtastic-sovelluksessa ja käynnistä ATAK-lisäosa uudelleen | . | 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ä" + },"5099": { + "doc": "TAK-integraatio", + "title": "Tietoturvahuomiot", + "content": ". | TAK-data sisältää sijainti- ja kutsutunnustietoja | Varmista, että kanavan salaus on oikein määritetty, kun käytät TAK:ia arkaluonteisissa ympäristöissä | TAK-moduuli noudattaa samaa kanavasalausta kuin muut Meshtastic-viestit | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#tietoturvahuomiot", + + "relUrl": "/fi-rFI/user/tak.html#tietoturvahuomiot" + },"5100": { + "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 | ATAK-liitännäisen opas – yksityiskohtaiset ATAK-asennusohjeet meshtastic.org -sivustolla | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#aiheeseen-liittyv%C3%A4t-aiheet", + + "relUrl": "/fi-rFI/user/tak.html#aiheeseen-liittyvät-aiheet" + },"5101": { "doc": "Интеграция TAK", "title": "Интеграция TAK", "content": "Meshtastic интегрируется с экосистемой Team Awareness Kit (TAK), обеспечивая взаимодействие между устройствами mesh-сети Meshtastic и приложениями TAK, такими как ATAK и WinTAK. ", "url": "/Meshtastic-Android/main/ru-rRU/user/tak.html", "relUrl": "/ru-rRU/user/tak.html" - },"5192": { + },"5102": { "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#обзор" - },"5193": { + },"5103": { "doc": "Интеграция TAK", "title": "Настройка", "content": "Необходимые условия . | Установлен ATAK (Android Team Awareness Kit) или WinTAK | Установлен Meshtastic ATAK Plugin | Модуль TAK включён на вашем радио Meshtastic | . Настройки . | Перейдите в Настройки → Конфигурация модулей → TAK. | Включите модуль TAK. | Настройте параметры команды/группы TAK: | . | Настройка | Описание | . | Включено | Активировано взаимодействие с TAK | . | Режим обмена | Режим вывода, совместимый с TAK | . Настройка плагина ATAK . | Установите Meshtastic ATAK Plugin из репозитория плагинов. | Откройте ATAK и включите плагин Meshtastic. | Плагин соединяет сообщения между ATAK и твоей mesh-сетью. | . Локальный TAK-сервер . Приложение также может запускать локальный TAK-сервер, чтобы ATAK/iTAK на том же устройстве могли подключаться напрямую, без удалённого TAK-сервера. Сервер привязывается только к локальному хосту (127.0.0.1:8089) и использует TLS с взаимной аутентификацией по сертификатам (mTLS), поэтому он недоступен с других устройств в сети. Откройте Настройки → Конфигурация модулей → TAK → TAK-сервер: . | Включить локальный TAK-сервер — запускает mTLS-сервер только на локальную петлю на порту 8089 для подключений ATAK/iTAK с того же устройства. | Экспорт пакета данных 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#настройка" - },"5194": { + },"5104": { "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" - },"5195": { + },"5105": { "doc": "Интеграция TAK", "title": "Идентификация в TAK", "content": "При использовании ролей TAK твоя нода передаёт идентификационную информацию, которая отображается на картах TAK: . | Настройка | Описание | . | Цвет команды | Цвет твоей команды на карте TAK (например, Синий, Красный, Голубой, Зелёный) | . | Роль участника | Твоя оперативная роль (Team Member, Team Lead, HQ, Medic, RTO и т. д.) | . Эти настройки появляются в Настройки → Конфигурация модулей → TAK, когда модуль TAK включён. Твой позывной в TAK не задаётся отдельно — он автоматически берётся из имени твоей ноды Meshtastic. 💡 Совет: Цвета команд/ролей являются стандартными цветами принадлежности в TAK. Согласуй с твоей командой TAK использование единообразных назначений команд. ", "url": "/Meshtastic-Android/main/ru-rRU/user/tak.html#%D0%B8%D0%B4%D0%B5%D0%BD%D1%82%D0%B8%D1%84%D0%B8%D0%BA%D0%B0%D1%86%D0%B8%D1%8F-%D0%B2-tak", "relUrl": "/ru-rRU/user/tak.html#идентификация-в-tak" - },"5196": { + },"5106": { "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" - },"5197": { + },"5107": { "doc": "Интеграция TAK", "title": "Использование с ATAK", "content": "После настройки: . | Ноды Meshtastic отображаются как маркеры на карте ATAK с подписями позывных | Сообщения чата могут передаваться между mesh-сетью и сетями TAK | Обновления местоположения передаются двунаправленно между Meshtastic и TAK | Ноды TAK Tracker автоматически передают PLI — их координаты отображаются на картах ATAK без какой-либо настройки на стороне ATAK | . ⚠️ Примечание: Для интеграции с TAK требуются определённые роли нод и настройка модуля. Стандартные клиентские ноды не участвуют в операциях TAK автоматически. ", "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" - },"5198": { + },"5108": { "doc": "Интеграция TAK", "title": "Устранение неполадок", "content": "| Проблема | Причина | Решение | . | Нода не отображается на карте ATAK | Модуль TAK отключён или выбрана неверная роль | Убедитесь, что модуль TAK включён, а роль ноды — TAK или TAK Tracker | . | Данные о местоположении устарели | Потерян сигнал GPS или слишком большой интервал | Проверьте состояние GPS; уменьшите интервал передачи координат в настройках Position Config | . | Плагин ATAK показывает “не подключён” | Потеряно соединение BLE или произошёл сбой плагина | Переподключите Bluetooth в приложении Meshtastic, затем перезапустите плагин ATAK | . | Фигуры, маркеры или маршруты не передаются | Отправляющая нода использует устаревший 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#устранение-неполадок" - },"5199": { + },"5109": { "doc": "Интеграция TAK", "title": "Соображения безопасности", "content": ". | Данные TAK передают ваше местоположение и позывной | Убедись, что шифрование канала настроено при использовании TAK в чувствительных средах | Модуль TAK соблюдает то же шифрование канала, что и другие сообщения Meshtastic | . ", "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#соображения-безопасности" - },"5200": { + },"5110": { "doc": "Интеграция TAK", "title": "Связанные темы", "content": ". | Настройки — Модули и администрирование — конфигурация модуля TAK | Ноды — роли TAK и TAK Tracker в списке нод | Карта и путевые точки — расположение нод на карте | Руководство по плагину ATAK — подробная настройка ATAK на meshtastic.org | . ", "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#связанные-темы" + },"5111": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html", + + "relUrl": "/ko-rKR/user/tak.html" + },"5112": { + "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" + },"5113": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . 설정 . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | 설명 | . | 활성화 | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5114": { + "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" + },"5115": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#tak-identity", + + "relUrl": "/ko-rKR/user/tak.html#tak-identity" + },"5116": { + "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" + },"5117": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#usage-with-atak", + + "relUrl": "/ko-rKR/user/tak.html#usage-with-atak" + },"5118": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5119": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#security-considerations", + + "relUrl": "/ko-rKR/user/tak.html#security-considerations" + },"5120": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#related-topics", + + "relUrl": "/ko-rKR/user/tak.html#related-topics" + },"5121": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html", + + "relUrl": "/hr-rHR/user/tak.html" + },"5122": { + "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" + },"5123": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Opis | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5124": { + "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" + },"5125": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#tak-identity", + + "relUrl": "/hr-rHR/user/tak.html#tak-identity" + },"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/hr-rHR/user/tak.html#wire-format-v1--v2", + + "relUrl": "/hr-rHR/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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#usage-with-atak", + + "relUrl": "/hr-rHR/user/tak.html#usage-with-atak" + },"5128": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5129": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#security-considerations", + + "relUrl": "/hr-rHR/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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#related-topics", + + "relUrl": "/hr-rHR/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 mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html", + + "relUrl": "/sq-rAL/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/sq-rAL/user/tak.html#overview", + + "relUrl": "/sq-rAL/user/tak.html#overview" + },"5133": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Përshkrimi | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5134": { + "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" + },"5135": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#tak-identity", + + "relUrl": "/sq-rAL/user/tak.html#tak-identity" + },"5136": { + "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" + },"5137": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#usage-with-atak", + + "relUrl": "/sq-rAL/user/tak.html#usage-with-atak" + },"5138": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5139": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#security-considerations", + + "relUrl": "/sq-rAL/user/tak.html#security-considerations" + },"5140": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#related-topics", + + "relUrl": "/sq-rAL/user/tak.html#related-topics" + },"5141": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/no-rNO/user/tak.html", + + "relUrl": "/no-rNO/user/tak.html" + },"5142": { + "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" + },"5143": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Beskrivelse | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5144": { + "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" + },"5145": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#tak-identity", + + "relUrl": "/no-rNO/user/tak.html#tak-identity" + },"5146": { + "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" + },"5147": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#usage-with-atak", + + "relUrl": "/no-rNO/user/tak.html#usage-with-atak" + },"5148": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5149": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#security-considerations", + + "relUrl": "/no-rNO/user/tak.html#security-considerations" + },"5150": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#related-topics", + + "relUrl": "/no-rNO/user/tak.html#related-topics" + },"5151": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html", + + "relUrl": "/lt-rLT/user/tak.html" + },"5152": { + "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" + },"5153": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Aprašymas | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5154": { + "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" + },"5155": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#tak-identity", + + "relUrl": "/lt-rLT/user/tak.html#tak-identity" + },"5156": { + "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" + },"5157": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#usage-with-atak", + + "relUrl": "/lt-rLT/user/tak.html#usage-with-atak" + },"5158": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5159": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#security-considerations", + + "relUrl": "/lt-rLT/user/tak.html#security-considerations" + },"5160": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#related-topics", + + "relUrl": "/lt-rLT/user/tak.html#related-topics" + },"5161": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html", + + "relUrl": "/ar-rSA/user/tak.html" + },"5162": { + "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" + },"5163": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | الوصف | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5164": { + "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" + },"5165": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#tak-identity", + + "relUrl": "/ar-rSA/user/tak.html#tak-identity" + },"5166": { + "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" + },"5167": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#usage-with-atak", + + "relUrl": "/ar-rSA/user/tak.html#usage-with-atak" + },"5168": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5169": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#security-considerations", + + "relUrl": "/ar-rSA/user/tak.html#security-considerations" + },"5170": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#related-topics", + + "relUrl": "/ar-rSA/user/tak.html#related-topics" + },"5171": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html", + + "relUrl": "/pt-rPT/user/tak.html" + },"5172": { + "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" + },"5173": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuração . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Descrição | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5174": { + "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" + },"5175": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#tak-identity", + + "relUrl": "/pt-rPT/user/tak.html#tak-identity" + },"5176": { + "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" + },"5177": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#usage-with-atak", + + "relUrl": "/pt-rPT/user/tak.html#usage-with-atak" + },"5178": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5179": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#security-considerations", + + "relUrl": "/pt-rPT/user/tak.html#security-considerations" + },"5180": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#related-topics", + + "relUrl": "/pt-rPT/user/tak.html#related-topics" + },"5181": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html", + + "relUrl": "/iw-rIL/user/tak.html" + },"5182": { + "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" + },"5183": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | תיאור | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5184": { + "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" + },"5185": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#tak-identity", + + "relUrl": "/iw-rIL/user/tak.html#tak-identity" + },"5186": { + "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" + },"5187": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#usage-with-atak", + + "relUrl": "/iw-rIL/user/tak.html#usage-with-atak" + },"5188": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5189": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#security-considerations", + + "relUrl": "/iw-rIL/user/tak.html#security-considerations" + },"5190": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#related-topics", + + "relUrl": "/iw-rIL/user/tak.html#related-topics" + },"5191": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/el-rGR/user/tak.html", + + "relUrl": "/el-rGR/user/tak.html" + },"5192": { + "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" + },"5193": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Περιγραφή | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5194": { + "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" + },"5195": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#tak-identity", + + "relUrl": "/el-rGR/user/tak.html#tak-identity" + },"5196": { + "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" + },"5197": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#usage-with-atak", + + "relUrl": "/el-rGR/user/tak.html#usage-with-atak" + },"5198": { + "doc": "TAK Integration", + "title": "Troubleshooting", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5199": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#security-considerations", + + "relUrl": "/el-rGR/user/tak.html#security-considerations" + },"5200": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#related-topics", + + "relUrl": "/el-rGR/user/tak.html#related-topics" },"5201": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html", + "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html", - "relUrl": "/nl-rNL/user/tak.html" + "relUrl": "/ro-rRO/user/tak.html" },"5202": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#overview", - "relUrl": "/nl-rNL/user/tak.html#overview" + "relUrl": "/ro-rRO/user/tak.html#overview" },"5203": { "doc": "TAK Integration", "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Beschrijving | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Descriere | . | Activat | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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": "/nl-rNL/user/tak.html#setup" + "relUrl": "/ro-rRO/user/tak.html#setup" },"5204": { "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", + "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": "/nl-rNL/user/tak.html#tak-roles" + "relUrl": "/ro-rRO/user/tak.html#tak-roles" },"5205": { "doc": "TAK Integration", "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#tak-identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#tak-identity", - "relUrl": "/nl-rNL/user/tak.html#tak-identity" + "relUrl": "/ro-rRO/user/tak.html#tak-identity" },"5206": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#wire-format-v1--v2", - "relUrl": "/nl-rNL/user/tak.html#wire-format-v1--v2" + "relUrl": "/ro-rRO/user/tak.html#wire-format-v1--v2" },"5207": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#usage-with-atak", + "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#usage-with-atak", - "relUrl": "/nl-rNL/user/tak.html#usage-with-atak" + "relUrl": "/ro-rRO/user/tak.html#usage-with-atak" },"5208": { "doc": "TAK Integration", "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#troubleshooting", - "relUrl": "/nl-rNL/user/tak.html#troubleshooting" + "relUrl": "/ro-rRO/user/tak.html#troubleshooting" },"5209": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#security-considerations", + "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#security-considerations", - "relUrl": "/nl-rNL/user/tak.html#security-considerations" + "relUrl": "/ro-rRO/user/tak.html#security-considerations" },"5210": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#related-topics", + "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#related-topics", - "relUrl": "/nl-rNL/user/tak.html#related-topics" + "relUrl": "/ro-rRO/user/tak.html#related-topics" },"5211": { "doc": "TAK integratsioon", "title": "TAK integratsioon", @@ -36549,3761 +36549,3761 @@ "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/it-rIT/user/tak.html", + "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html", - "relUrl": "/it-rIT/user/tak.html" + "relUrl": "/ga-rIE/user/tak.html" },"5222": { "doc": "TAK Integration", - "title": "Panoramica", + "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/it-rIT/user/tak.html#panoramica", + "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#overview", - "relUrl": "/it-rIT/user/tak.html#panoramica" + "relUrl": "/ga-rIE/user/tak.html#overview" },"5223": { "doc": "TAK Integration", - "title": "Configurazione", - "content": "Prerequisiti . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configurazione . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Impostazione | Descrizione | . | Abilitato | Activate TAK interop | . | Modalità | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Cur síos | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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": "/it-rIT/user/tak.html#configurazione" + "relUrl": "/ga-rIE/user/tak.html#setup" },"5224": { "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", + "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": "/it-rIT/user/tak.html#tak-roles" + "relUrl": "/ga-rIE/user/tak.html#tak-roles" },"5225": { "doc": "TAK Integration", "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#tak-identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#tak-identity", - "relUrl": "/it-rIT/user/tak.html#tak-identity" + "relUrl": "/ga-rIE/user/tak.html#tak-identity" },"5226": { "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", + "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": "/it-rIT/user/tak.html#wire-format-v1--v2" + "relUrl": "/ga-rIE/user/tak.html#wire-format-v1--v2" },"5227": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#usage-with-atak", + "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#usage-with-atak", - "relUrl": "/it-rIT/user/tak.html#usage-with-atak" + "relUrl": "/ga-rIE/user/tak.html#usage-with-atak" },"5228": { "doc": "TAK Integration", - "title": "Risoluzione problemi", + "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#troubleshooting", - "relUrl": "/it-rIT/user/tak.html#risoluzione-problemi" + "relUrl": "/ga-rIE/user/tak.html#troubleshooting" },"5229": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#security-considerations", + "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#security-considerations", - "relUrl": "/it-rIT/user/tak.html#security-considerations" + "relUrl": "/ga-rIE/user/tak.html#security-considerations" },"5230": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#related-topics", + "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#related-topics", - "relUrl": "/it-rIT/user/tak.html#related-topics" + "relUrl": "/ga-rIE/user/tak.html#related-topics" },"5231": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html", - - "relUrl": "/ar-rSA/user/tak.html" - },"5232": { - "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" - },"5233": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | الوصف | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5234": { - "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" - },"5235": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#tak-identity", - - "relUrl": "/ar-rSA/user/tak.html#tak-identity" - },"5236": { - "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" - },"5237": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#usage-with-atak", - - "relUrl": "/ar-rSA/user/tak.html#usage-with-atak" - },"5238": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5239": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#security-considerations", - - "relUrl": "/ar-rSA/user/tak.html#security-considerations" - },"5240": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#related-topics", - - "relUrl": "/ar-rSA/user/tak.html#related-topics" - },"5241": { - "doc": "TAK Integration", - "title": "TAK Integration", - "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html", - - "relUrl": "/sk-rSK/user/tak.html" - },"5242": { - "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" - },"5243": { - "doc": "TAK Integration", - "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Popis | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5244": { - "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" - },"5245": { - "doc": "TAK Integration", - "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#tak-identity", - - "relUrl": "/sk-rSK/user/tak.html#tak-identity" - },"5246": { - "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" - },"5247": { - "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#usage-with-atak", - - "relUrl": "/sk-rSK/user/tak.html#usage-with-atak" - },"5248": { - "doc": "TAK Integration", - "title": "Troubleshooting", - "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5249": { - "doc": "TAK Integration", - "title": "Security Considerations", - "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#security-considerations", - - "relUrl": "/sk-rSK/user/tak.html#security-considerations" - },"5250": { - "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#related-topics", - - "relUrl": "/sk-rSK/user/tak.html#related-topics" - },"5251": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html", "relUrl": "/pl-rPL/user/tak.html" - },"5252": { + },"5232": { "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" - },"5253": { + },"5233": { "doc": "TAK Integration", "title": "Setup", "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Konfiguracja . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Opis | . | Włączony | Activate TAK interop | . | Tryb | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" - },"5254": { + },"5234": { "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" - },"5255": { + },"5235": { "doc": "TAK Integration", "title": "TAK Identity", "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#tak-identity", "relUrl": "/pl-rPL/user/tak.html#tak-identity" - },"5256": { + },"5236": { "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" - },"5257": { + },"5237": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#usage-with-atak", "relUrl": "/pl-rPL/user/tak.html#usage-with-atak" - },"5258": { + },"5238": { "doc": "TAK Integration", "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" - },"5259": { + },"5239": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#security-considerations", "relUrl": "/pl-rPL/user/tak.html#security-considerations" - },"5260": { + },"5240": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#related-topics", "relUrl": "/pl-rPL/user/tak.html#related-topics" - },"5261": { + },"5241": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html", + "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html", - "relUrl": "/zh-rTW/user/tak.html" - },"5262": { + "relUrl": "/nl-rNL/user/tak.html" + },"5242": { "doc": "TAK Integration", - "title": "概觀", + "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/zh-rTW/user/tak.html#%E6%A6%82%E8%A7%80", + "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#overview", - "relUrl": "/zh-rTW/user/tak.html#概觀" - },"5263": { + "relUrl": "/nl-rNL/user/tak.html#overview" + },"5243": { "doc": "TAK Integration", - "title": "設定", - "content": "先決條件 . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . 設定 . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | 設定 | 描述說明 | . | 已啟用 | Activate TAK interop | . | 模式 | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Beschrijving | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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": "/zh-rTW/user/tak.html#設定" - },"5264": { + "relUrl": "/nl-rNL/user/tak.html#setup" + },"5244": { "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", + "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": "/zh-rTW/user/tak.html#tak-roles" - },"5265": { + "relUrl": "/nl-rNL/user/tak.html#tak-roles" + },"5245": { "doc": "TAK Integration", "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that appears on TAK maps: . | 設定 | 描述說明 | . | 隊伍顏色 | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | 隊員角色 | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#tak-identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#tak-identity", - "relUrl": "/zh-rTW/user/tak.html#tak-identity" - },"5266": { + "relUrl": "/nl-rNL/user/tak.html#tak-identity" + },"5246": { "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", + "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": "/zh-rTW/user/tak.html#wire-format-v1--v2" - },"5267": { + "relUrl": "/nl-rNL/user/tak.html#wire-format-v1--v2" + },"5247": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#usage-with-atak", + "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#usage-with-atak", - "relUrl": "/zh-rTW/user/tak.html#usage-with-atak" - },"5268": { + "relUrl": "/nl-rNL/user/tak.html#usage-with-atak" + },"5248": { "doc": "TAK Integration", - "title": "故障排除", + "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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", + "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#troubleshooting", - "relUrl": "/zh-rTW/user/tak.html#故障排除" - },"5269": { + "relUrl": "/nl-rNL/user/tak.html#troubleshooting" + },"5249": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#security-considerations", + "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#security-considerations", - "relUrl": "/zh-rTW/user/tak.html#security-considerations" - },"5270": { + "relUrl": "/nl-rNL/user/tak.html#security-considerations" + },"5250": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#related-topics", + "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#related-topics", - "relUrl": "/zh-rTW/user/tak.html#related-topics" + "relUrl": "/nl-rNL/user/tak.html#related-topics" + },"5251": { + "doc": "TAK Integration", + "title": "TAK Integration", + "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html", + + "relUrl": "/sv-rSE/user/tak.html" + },"5252": { + "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" + },"5253": { + "doc": "TAK Integration", + "title": "Setup", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Konfiguration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Beskrivning | . | Aktiverad | Activate TAK interop | . | Typ | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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" + },"5254": { + "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" + },"5255": { + "doc": "TAK Integration", + "title": "TAK Identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#tak-identity", + + "relUrl": "/sv-rSE/user/tak.html#tak-identity" + },"5256": { + "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" + },"5257": { + "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#usage-with-atak", + + "relUrl": "/sv-rSE/user/tak.html#usage-with-atak" + },"5258": { + "doc": "TAK Integration", + "title": "Felsökning", + "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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" + },"5259": { + "doc": "TAK Integration", + "title": "Security Considerations", + "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#security-considerations", + + "relUrl": "/sv-rSE/user/tak.html#security-considerations" + },"5260": { + "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#related-topics", + + "relUrl": "/sv-rSE/user/tak.html#related-topics" + },"5261": { + "doc": "TAK 連携", + "title": "TAK 連携", + "content": "Meshtastic は Team Awareness Kit（TAK）エコシステムと連携し、Meshtastic のメッシュデバイスと、ATAK や WinTAK などの TAK アプリケーションとの相互運用を可能にします。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html", + + "relUrl": "/ja-rJP/user/tak.html" + },"5262": { + "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#概要" + },"5263": { + "doc": "TAK 連携", + "title": "セットアップ", + "content": "前提条件 . | ATAK（Android Team Awareness Kit）または WinTAK がインストールされていること | Meshtastic ATAK プラグインがインストールされていること | Meshtastic 無線機で TAK モジュールが有効になっていること | . 設定 . | 「設定 → モジュール設定 → TAK」に移動します。 | TAK モジュールを有効にします。 | TAK のチーム／グループ設定を構成します： | . | 設定項目 | 説明 | . | 有効 | TAK 相互運用を有効化 | . | モード | TAK 互換の出力モード | . ATAK プラグインのセットアップ . | プラグインリポジトリから Meshtastic ATAK プラグインをインストールします。 | ATAK を開き、Meshtastic プラグインを有効にします。 | プラグインは、ATAK とメッシュネットワークの間でメッセージを橋渡しします。 | . ローカル TAK サーバー . アプリはローカル TAK サーバーを実行することもでき、同じデバイス上の ATAK／iTAK が、リモートの TAK サーバーなしで直接接続できます。 サーバーは localhost のみ（127.0.0.1:8089）にバインドし、相互証明書認証（mTLS）による TLS を使用するため、ネットワーク上の他のデバイスからは到達できません。 「設定 → モジュール設定 → TAK → TAK サーバー」を開きます： . | ローカル TAK サーバーを有効化：同じデバイスからの ATAK／iTAK 接続用に、ポート 8089 でループバック専用の mTLS サーバーを起動します。 | 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#セットアップ" + },"5264": { + "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-の役割" + },"5265": { + "doc": "TAK 連携", + "title": "TAK のアイデンティティ", + "content": "TAK の役割を使用すると、ノードは TAK のマップに表示されるアイデンティティ情報をブロードキャストします： . | 設定項目 | 説明 | . | チームカラー | TAK のマップ上でのチームの色（例：ブルー、レッド、シアン、グリーン） | . | メンバーロール | 運用上の役割（チームメンバー、チームリード、HQ、メディック、RTO など） | . これらの設定は、TAK モジュールが有効なときに「設定 → モジュール設定 → TAK」に表示されます。 TAK のコールサインは別個の設定ではありません。Meshtastic のノード名から自動的に導かれます。 . 💡 ヒント： チーム／役割の色は、TAK の標準的な所属色です。 一貫したチーム割り当てを使うよう、TAK チームと調整してください。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html#tak-%E3%81%AE%E3%82%A2%E3%82%A4%E3%83%87%E3%83%B3%E3%83%86%E3%82%A3%E3%83%86%E3%82%A3", + + "relUrl": "/ja-rJP/user/tak.html#tak-のアイデンティティ" + },"5266": { + "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" + },"5267": { + "doc": "TAK 連携", + "title": "ATAK での使用", + "content": "設定が完了すると： . | Meshtastic のノードが、コールサインのラベル付きで ATAK のマップにマーカーとして表示されます | チャットメッセージを、メッシュと TAK ネットワークの間で橋渡しできます | 位置の更新が、Meshtastic と TAK の間で双方向に流れます | TAK Tracker のノードは自動的に PLI をブロードキャストします。ATAK 側の設定なしで、その位置が ATAK のマップに表示されます | . ⚠️ 注意： TAK 連携には、特定のノードの役割とモジュールの設定が必要です。 標準のクライアントノードは、自動的には TAK の運用に参加しません。 . ", + "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-での使用" + },"5268": { + "doc": "TAK 連携", + "title": "トラブルシューティング", + "content": "| 問題 | 原因 | 解決策 | . | ノードが ATAK のマップに表示されない | TAK モジュールが無効、または役割が正しくない | TAK モジュールが有効で、ノードの役割が TAK または TAK Tracker になっているか確認する | . | 位置の更新が古い | GPS 測位が失われた、または間隔が長すぎる | GPS の状態を確認し、位置情報設定で位置のブロードキャスト間隔を短くする | . | ATAK プラグインが「切断」と表示する | BLE 接続が失われた、またはプラグインがクラッシュした | Meshtastic アプリで Bluetooth を再接続し、その後 ATAK プラグインを再起動する | . | 図形、マーカー、ルートが橋渡しされない | 送信側のノードがレガシーな 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#トラブルシューティング" + },"5269": { + "doc": "TAK 連携", + "title": "セキュリティに関する注意", + "content": ". | TAK データは、あなたの位置とコールサインの情報を共有します | 機密性の高い環境で TAK を使用する場合は、チャンネルの暗号化を設定してください | TAK モジュールは、他の Meshtastic メッセージと同じチャンネル暗号化に従います | . ", + "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#セキュリティに関する注意" + },"5270": { + "doc": "TAK 連携", + "title": "関連トピック", + "content": ". | 設定：モジュールと管理：TAK モジュールの設定 | ノード：ノードリストの TAK と TAK Tracker の役割 | マップとウェイポイント：マップ上のノードの位置 | ATAK プラグインガイド：meshtastic.org にある詳細な ATAK セットアップ | . ", + "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#関連トピック" },"5271": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html", + "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html", - "relUrl": "/cs-rCZ/user/tak.html" + "relUrl": "/hu-rHU/user/tak.html" },"5272": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#overview", - "relUrl": "/cs-rCZ/user/tak.html#overview" + "relUrl": "/hu-rHU/user/tak.html#overview" },"5273": { "doc": "TAK Integration", "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Nastavení . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Nastavení | Popis | . | Povoleno | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Leírás | . | Engedélyezve | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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": "/cs-rCZ/user/tak.html#setup" + "relUrl": "/hu-rHU/user/tak.html#setup" },"5274": { "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", + "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": "/cs-rCZ/user/tak.html#tak-roles" + "relUrl": "/hu-rHU/user/tak.html#tak-roles" },"5275": { "doc": "TAK Integration", "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#tak-identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#tak-identity", - "relUrl": "/cs-rCZ/user/tak.html#tak-identity" + "relUrl": "/hu-rHU/user/tak.html#tak-identity" },"5276": { "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", + "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#wire-format-v1--v2", - "relUrl": "/cs-rCZ/user/tak.html#wire-format-v1--v2" + "relUrl": "/hu-rHU/user/tak.html#wire-format-v1--v2" },"5277": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#usage-with-atak", + "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#usage-with-atak", - "relUrl": "/cs-rCZ/user/tak.html#usage-with-atak" + "relUrl": "/hu-rHU/user/tak.html#usage-with-atak" },"5278": { "doc": "TAK Integration", "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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", + "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#troubleshooting", - "relUrl": "/cs-rCZ/user/tak.html#troubleshooting" + "relUrl": "/hu-rHU/user/tak.html#troubleshooting" },"5279": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#security-considerations", + "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#security-considerations", - "relUrl": "/cs-rCZ/user/tak.html#security-considerations" + "relUrl": "/hu-rHU/user/tak.html#security-considerations" },"5280": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#related-topics", + "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#related-topics", - "relUrl": "/cs-rCZ/user/tak.html#related-topics" + "relUrl": "/hu-rHU/user/tak.html#related-topics" },"5281": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html", + "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html", - "relUrl": "/fr-rFR/user/tak.html" + "relUrl": "/ht-rHT/user/tak.html" },"5282": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#overview", - "relUrl": "/fr-rFR/user/tak.html#overview" + "relUrl": "/ht-rHT/user/tak.html#overview" },"5283": { "doc": "TAK Integration", "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Description | . | Activé | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Deskripsyon | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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": "/fr-rFR/user/tak.html#setup" + "relUrl": "/ht-rHT/user/tak.html#setup" },"5284": { "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", + "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": "/fr-rFR/user/tak.html#tak-roles" + "relUrl": "/ht-rHT/user/tak.html#tak-roles" },"5285": { "doc": "TAK Integration", "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that appears on TAK maps: . | Setting | Description | . | Couleur de l’équipe | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Rôle Membre | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#tak-identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#tak-identity", - "relUrl": "/fr-rFR/user/tak.html#tak-identity" + "relUrl": "/ht-rHT/user/tak.html#tak-identity" },"5286": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#wire-format-v1--v2", - "relUrl": "/fr-rFR/user/tak.html#wire-format-v1--v2" + "relUrl": "/ht-rHT/user/tak.html#wire-format-v1--v2" },"5287": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#usage-with-atak", + "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#usage-with-atak", - "relUrl": "/fr-rFR/user/tak.html#usage-with-atak" + "relUrl": "/ht-rHT/user/tak.html#usage-with-atak" },"5288": { "doc": "TAK Integration", "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#troubleshooting", - "relUrl": "/fr-rFR/user/tak.html#troubleshooting" + "relUrl": "/ht-rHT/user/tak.html#troubleshooting" },"5289": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#security-considerations", + "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#security-considerations", - "relUrl": "/fr-rFR/user/tak.html#security-considerations" + "relUrl": "/ht-rHT/user/tak.html#security-considerations" },"5290": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#related-topics", + "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#related-topics", - "relUrl": "/fr-rFR/user/tak.html#related-topics" + "relUrl": "/ht-rHT/user/tak.html#related-topics" },"5291": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html", + "url": "/Meshtastic-Android/main/gl-rES/user/tak.html", - "relUrl": "/zh-rCN/user/tak.html" + "relUrl": "/gl-rES/user/tak.html" },"5292": { "doc": "TAK Integration", - "title": "总览", + "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/zh-rCN/user/tak.html#%E6%80%BB%E8%A7%88", + "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#overview", - "relUrl": "/zh-rCN/user/tak.html#总览" + "relUrl": "/gl-rES/user/tak.html#overview" },"5293": { "doc": "TAK Integration", "title": "Setup", - "content": "前置条件 . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | 说明 | . | Enabled | Activate TAK interop | . | 模式 | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Descrición | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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": "/zh-rCN/user/tak.html#setup" + "relUrl": "/gl-rES/user/tak.html#setup" },"5294": { "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", + "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": "/zh-rCN/user/tak.html#tak-roles" + "relUrl": "/gl-rES/user/tak.html#tak-roles" },"5295": { "doc": "TAK Integration", "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that appears on TAK maps: . | Setting | 说明 | . | 队伍颜色 | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | 成员角色 | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#tak-identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#tak-identity", - "relUrl": "/zh-rCN/user/tak.html#tak-identity" + "relUrl": "/gl-rES/user/tak.html#tak-identity" },"5296": { "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", + "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": "/zh-rCN/user/tak.html#wire-format-v1--v2" + "relUrl": "/gl-rES/user/tak.html#wire-format-v1--v2" },"5297": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#usage-with-atak", + "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#usage-with-atak", - "relUrl": "/zh-rCN/user/tak.html#usage-with-atak" + "relUrl": "/gl-rES/user/tak.html#usage-with-atak" },"5298": { "doc": "TAK Integration", - "title": "问题排查", + "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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", + "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#troubleshooting", - "relUrl": "/zh-rCN/user/tak.html#问题排查" + "relUrl": "/gl-rES/user/tak.html#troubleshooting" },"5299": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#security-considerations", + "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#security-considerations", - "relUrl": "/zh-rCN/user/tak.html#security-considerations" + "relUrl": "/gl-rES/user/tak.html#security-considerations" },"5300": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#related-topics", + "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#related-topics", - "relUrl": "/zh-rCN/user/tak.html#related-topics" + "relUrl": "/gl-rES/user/tak.html#related-topics" },"5301": { "doc": "TAK Integration", "title": "TAK Integration", "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/srp/user/tak.html", + "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html", - "relUrl": "/srp/user/tak.html" + "relUrl": "/tr-rTR/user/tak.html" },"5302": { "doc": "TAK Integration", - "title": "Overview", + "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/srp/user/tak.html#overview", + "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#genel-bak%C4%B1%C5%9F", - "relUrl": "/srp/user/tak.html#overview" + "relUrl": "/tr-rTR/user/tak.html#genel-bakış" },"5303": { "doc": "TAK Integration", "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Опис | . | Омогућено | Activate TAK interop | . | Мод | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Yapılandırma . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Açıklaması | . | Açık | Activate TAK interop | . | Mod | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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": "/srp/user/tak.html#setup" + "relUrl": "/tr-rTR/user/tak.html#setup" },"5304": { "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", + "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": "/srp/user/tak.html#tak-roles" + "relUrl": "/tr-rTR/user/tak.html#tak-roles" },"5305": { "doc": "TAK Integration", "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/srp/user/tak.html#tak-identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#tak-identity", - "relUrl": "/srp/user/tak.html#tak-identity" + "relUrl": "/tr-rTR/user/tak.html#tak-identity" },"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/srp/user/tak.html#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": "/srp/user/tak.html#wire-format-v1--v2" + "relUrl": "/tr-rTR/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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/srp/user/tak.html#usage-with-atak", + "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#usage-with-atak", - "relUrl": "/srp/user/tak.html#usage-with-atak" + "relUrl": "/tr-rTR/user/tak.html#usage-with-atak" },"5308": { "doc": "TAK Integration", "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#troubleshooting", - "relUrl": "/srp/user/tak.html#troubleshooting" + "relUrl": "/tr-rTR/user/tak.html#troubleshooting" },"5309": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/srp/user/tak.html#security-considerations", + "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#security-considerations", - "relUrl": "/srp/user/tak.html#security-considerations" + "relUrl": "/tr-rTR/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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/srp/user/tak.html#related-topics", + "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#related-topics", - "relUrl": "/srp/user/tak.html#related-topics" + "relUrl": "/tr-rTR/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 mesh devices and TAK applications like ATAK and WinTAK. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html", + "url": "/Meshtastic-Android/main/es-rES/user/tak.html", - "relUrl": "/sq-rAL/user/tak.html" + "relUrl": "/es-rES/user/tak.html" },"5312": { "doc": "TAK Integration", - "title": "Overview", + "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/sq-rAL/user/tak.html#overview", + "url": "/Meshtastic-Android/main/es-rES/user/tak.html#visi%C3%B3n-general", - "relUrl": "/sq-rAL/user/tak.html#overview" + "relUrl": "/es-rES/user/tak.html#visión-general" },"5313": { "doc": "TAK Integration", "title": "Setup", - "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuration . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Përshkrimi | . | Enabled | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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", + "content": "Prerequisites . | ATAK (Android Team Awareness Kit) or WinTAK installed | Meshtastic ATAK Plugin installed | TAK module enabled on your Meshtastic radio | . Configuración . | Navigate to Settings → Module Config → TAK. | Enable the TAK module. | Configure the TAK team/group settings: | . | Setting | Descripción | . | Habilitado | Activate TAK interop | . | Mode | TAK-compatible output mode | . ATAK Plugin Setup . | Install the Meshtastic ATAK Plugin from the plugin repository. | Open ATAK and enable the Meshtastic plugin. | The plugin bridges messages between ATAK and your mesh network. | . Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same device 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 → Module Config → TAK → TAK Server: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same device. | 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": "/sq-rAL/user/tak.html#setup" + "relUrl": "/es-rES/user/tak.html#setup" },"5314": { "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", + "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": "/sq-rAL/user/tak.html#tak-roles" + "relUrl": "/es-rES/user/tak.html#tak-roles" },"5315": { "doc": "TAK Integration", "title": "TAK Identity", - "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#tak-identity", + "content": "When using TAK roles, your node broadcasts identity information that 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 (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . These settings appear in Settings → Module Config → TAK when the TAK module is enabled. 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. ", + "url": "/Meshtastic-Android/main/es-rES/user/tak.html#tak-identity", - "relUrl": "/sq-rAL/user/tak.html#tak-identity" + "relUrl": "/es-rES/user/tak.html#tak-identity" },"5316": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/tak.html#wire-format-v1--v2", - "relUrl": "/sq-rAL/user/tak.html#wire-format-v1--v2" + "relUrl": "/es-rES/user/tak.html#wire-format-v1--v2" },"5317": { "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 and module configuration. Standard client nodes don’t automatically participate in TAK operations. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#usage-with-atak", + "url": "/Meshtastic-Android/main/es-rES/user/tak.html#usage-with-atak", - "relUrl": "/sq-rAL/user/tak.html#usage-with-atak" + "relUrl": "/es-rES/user/tak.html#usage-with-atak" },"5318": { "doc": "TAK Integration", "title": "Troubleshooting", "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK plugin shows “disconnected” | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin | . | 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", + "url": "/Meshtastic-Android/main/es-rES/user/tak.html#troubleshooting", - "relUrl": "/sq-rAL/user/tak.html#troubleshooting" + "relUrl": "/es-rES/user/tak.html#troubleshooting" },"5319": { "doc": "TAK Integration", "title": "Security Considerations", "content": ". | TAK data shares your position and callsign information | Ensure your channel encryption is configured when using TAK in sensitive environments | The TAK module respects the same channel encryption as other Meshtastic messages | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#security-considerations", + "url": "/Meshtastic-Android/main/es-rES/user/tak.html#security-considerations", - "relUrl": "/sq-rAL/user/tak.html#security-considerations" + "relUrl": "/es-rES/user/tak.html#security-considerations" },"5320": { "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 | ATAK plugin guide — detailed ATAK setup on meshtastic.org | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#related-topics", + "url": "/Meshtastic-Android/main/es-rES/user/tak.html#related-topics", - "relUrl": "/sq-rAL/user/tak.html#related-topics" + "relUrl": "/es-rES/user/tak.html#related-topics" },"5321": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/is-rIS/user/telemetry-and-sensors.html#telemetry--sensors" - },"5322": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#overview", - - "relUrl": "/is-rIS/user/telemetry-and-sensors.html#overview" - },"5323": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Lýsing | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/is-rIS/user/telemetry-and-sensors.html#device-telemetry" - },"5324": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperature | Humidity | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/is-rIS/user/telemetry-and-sensors.html#environment-sensors" - },"5325": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Lýsing | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/is-rIS/user/telemetry-and-sensors.html#power-metrics" - },"5326": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/is-rIS/user/telemetry-and-sensors.html#configuring-telemetry" - },"5327": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Lýsing | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/is-rIS/user/telemetry-and-sensors.html#air-quality-metrics" - },"5328": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/is-rIS/user/telemetry-and-sensors.html#viewing-telemetry" - },"5329": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/is-rIS/user/telemetry-and-sensors.html#troubleshooting" - },"5330": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/is-rIS/user/telemetry-and-sensors.html#related-topics" - },"5331": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html", - - "relUrl": "/is-rIS/user/telemetry-and-sensors.html" - },"5332": { - "doc": "テレメトリとセンサー", - "title": "テレメトリとセンサー", - "content": "Meshtastic のノードは、メッシュネットワーク全体でセンサーデータを収集・共有できます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html", - - "relUrl": "/ja-rJP/user/telemetry-and-sensors.html" - },"5333": { - "doc": "テレメトリとセンサー", - "title": "概要", - "content": "テレメトリを使うと、センサーを搭載したノードが、環境・電力・デバイスの状態の情報をブロードキャストできます。 このデータはノードの詳細画面で確認でき、時系列で記録することもできます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E6%A6%82%E8%A6%81", - - "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#概要" - },"5334": { - "doc": "テレメトリとセンサー", - "title": "デバイステレメトリ", - "content": "すべての Meshtastic ノードは、基本的なデバイステレメトリを報告します： . | メトリクス | 説明 | 標準的な範囲 | . | バッテリー残量 | 充電の割合 | 0–100% | . | 電圧 | バッテリー電圧 | 3.0–4.2V (LiPo) | . | チャンネル全体の利用率 | ローカルで使用された電波利用時間の割合 | 0–100% | . | 送信の電波利用率 | このノードが使用した電波利用時間の割合 | 0–100% | . | 連続稼働時間 | 前回の起動からの経過秒数 | 可変 | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E3%83%87%E3%83%90%E3%82%A4%E3%82%B9%E3%83%86%E3%83%AC%E3%83%A1%E3%83%88%E3%83%AA", - - "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#デバイステレメトリ" - },"5335": { - "doc": "テレメトリとセンサー", - "title": "環境センサー", - "content": "対応する環境センサー： . 温度と湿度 . | センサー | 温度 | 湿度 | 気圧 | 備考 | . | BME280 | ✓ | ✓ | ✓ | おすすめのオールインワン | . | BME680 | ✓ | ✓ | ✓ | ガス抵抗／IAQ を追加 | . | SHT31 | ✓ | ✓ | — | 高精度 | . | MCP9808 | ✓ | — | — | 高精度な温度 | . | LPS22 | — | — | ✓ | 気圧のみ | . 大気質 . | センサー | メトリクス | 備考 | . | BME680 | ガス抵抗／IAQ | 揮発性有機化合物 | . | PMSA003I | PM1.0, PM2.5, PM10 | 粒子状物質 | . | SEN55 | PM、NOx、VOC、温度、湿度 | マルチセンサー | . 光と UV . | センサー | メトリクス | . | OPT3001 | 周囲の明るさ（ルクス） | . | VEML7700 | 周囲の明るさ（ルクス） | . | LTR390 | UV 指数 | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E7%92%B0%E5%A2%83%E3%82%BB%E3%83%B3%E3%82%B5%E3%83%BC", - - "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#環境センサー" - },"5336": { - "doc": "テレメトリとセンサー", - "title": "電力メトリクス", - "content": "INA シリーズの電力センサーを搭載したノードは、次を報告できます： . | メトリクス | 説明 | . | バス電圧 | 供給レールの電圧 | . | 電流 | 消費電流（mA） | . | 電力 | 計算された電力（mW） | . リモートノードの太陽光充電やバッテリーの状態を監視するのに便利です。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.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/telemetry-and-sensors.html#電力メトリクス" - },"5337": { - "doc": "テレメトリとセンサー", - "title": "テレメトリを設定する", - "content": ". | 「設定 → モジュール設定 → テレメトリ」に移動します。 | 報告間隔を設定します： . | デバイスメトリクスの間隔：デバイスメトリクスをブロードキャストする頻度 | 環境メトリクスの間隔：センサーデータをブロードキャストする頻度 | . | 必要に応じて、特定のセンサーの種類を有効にします。 | . 推奨の間隔 . | 用途 | デバイス（秒） | 環境（秒） | . | 都市部のメッシュ（多数のノード） | 3600 | 3600 | . | 地方のメッシュ（少数のノード） | 900 | 900 | . | 気象観測所 | 900 | 300 | . | バッテリー節約 | 7200 | 7200 | . ⚠️ 注意： 間隔を短くすると、メッシュ全体で電波利用時間の消費とバッテリーの消耗が増えます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E3%83%86%E3%83%AC%E3%83%A1%E3%83%88%E3%83%AA%E3%82%92%E8%A8%AD%E5%AE%9A%E3%81%99%E3%82%8B", - - "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#テレメトリを設定する" - },"5338": { - "doc": "テレメトリとセンサー", - "title": "大気質メトリクス", - "content": "粒子状物質センサーまたは CO₂ センサーを搭載したノードは、大気質データを報告します： . | メトリクス | 単位 | 説明 | . | PM1.0 | µg/m³ | 超微小粒子状物質 | . | PM2.5 | µg/m³ | 微小粒子状物質 | . | PM10 | µg/m³ | 粗大粒子状物質 | . | CO₂ | ppm | 二酸化炭素の濃度 | . SCD4x などの CO₂ センサーは、自身の温度と湿度も報告し、上記の測定値とともに表示されます。 アプリは、PM2.5 の履歴から EPA NowCast AQI の値も算出します。 . CO₂ の測定値は、深刻度に応じて色分けされます（良好 → 空気がこもる → 悪い → 危険 → 退避）。 正確な ppm の区分、色、AQI の詳細については、ノードメトリクス：大気質 を参照してください。 . 大気質データは、ノードの詳細画面で情報カードとして表示したり、時系列でグラフ化したり、CSV にエクスポートしたりできます。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.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/telemetry-and-sensors.html#大気質メトリクス" - },"5339": { - "doc": "テレメトリとセンサー", - "title": "テレメトリを表示する", - "content": ". | 「ノード」に移動して、ノードを選択します。 | 詳細画面にテレメトリのセクションが表示されます： . | デバイスメトリクス（常に利用可能） | 環境メトリクス（センサーがある場合） | 電力メトリクス（INA センサーがある場合） | 大気質メトリクス（PM／CO₂ センサーがある場合） | . | 履歴グラフで、時系列の傾向を確認できます。 | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E3%83%86%E3%83%AC%E3%83%A1%E3%83%88%E3%83%AA%E3%82%92%E8%A1%A8%E7%A4%BA%E3%81%99%E3%82%8B", - - "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#テレメトリを表示する" - },"5340": { - "doc": "テレメトリとセンサー", - "title": "トラブルシューティング", - "content": ". | 環境データが表示されない？ リモートノードに物理センサーが接続されている必要があります（例：I2C の BME280）。 デバイステレメトリ（バッテリー、連続稼働時間）は常に利用できますが、環境メトリクスにはハードウェアが必要です。 | 測定値が古い？ 報告間隔を確認してください。非常に長い間隔（7200 秒以上）では、データの更新頻度が低くなります。 リモートノードがまだオンラインであるかも確認してください。 | I2C バスでセンサーが競合している？ 一部のセンサーは I2C アドレスを共有しています。 同じバスに複数のセンサーがある場合は、無線機のシリアルデバッグ出力でアドレスの衝突がないか確認してください。 | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.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/telemetry-and-sensors.html#トラブルシューティング" - },"5341": { - "doc": "テレメトリとセンサー", - "title": "関連トピック", - "content": ". | ノードメトリクス：ノードの詳細画面でテレメトリデータを表示 | 設定：モジュールと管理：テレメトリモジュールの設定 | 単位とロケール：温度と気圧の表示単位 | . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF", - - "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#関連トピック" - },"5342": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/ca-rES/user/telemetry-and-sensors.html#telemetry--sensors" - },"5343": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#overview", - - "relUrl": "/ca-rES/user/telemetry-and-sensors.html#overview" - },"5344": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Descripció | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/ca-rES/user/telemetry-and-sensors.html#device-telemetry" - },"5345": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperature | Humidity | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/ca-rES/user/telemetry-and-sensors.html#environment-sensors" - },"5346": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Descripció | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/ca-rES/user/telemetry-and-sensors.html#power-metrics" - },"5347": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/ca-rES/user/telemetry-and-sensors.html#configuring-telemetry" - },"5348": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Descripció | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/ca-rES/user/telemetry-and-sensors.html#air-quality-metrics" - },"5349": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/ca-rES/user/telemetry-and-sensors.html#viewing-telemetry" - },"5350": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/ca-rES/user/telemetry-and-sensors.html#troubleshooting" - },"5351": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/ca-rES/user/telemetry-and-sensors.html#related-topics" - },"5352": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html", - - "relUrl": "/ca-rES/user/telemetry-and-sensors.html" - },"5353": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#telemetry--sensors" - },"5354": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#overview", - - "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#overview" - },"5355": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Метрика | Опис | Typical Range | . | Ниво батерије | Charge percentage | 0–100% | . | Напон | Battery voltage | 3.0–4.2V (LiPo) | . | Искоришћеност канала | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Време рада | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#device-telemetry" - },"5356": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Сензор | Температура | Влажност | Pressure | Белешке | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Сензор | Метрика | Белешке | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Сензор | Метрика | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#environment-sensors" - },"5357": { - "doc": "Telemetry & Sensors", - "title": "Мерни подаци о снази", - "content": "Nodes with INA-series power sensors can report: . | Метрика | Опис | . | Bus Voltage | Supply rail voltage | . | Струја | Power consumption (mA) | . | Снага | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.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/telemetry-and-sensors.html#мерни-подаци-о-снази" - },"5358": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#configuring-telemetry" - },"5359": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Метрика | Unit | Опис | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#air-quality-metrics" - },"5360": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#viewing-telemetry" - },"5361": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#troubleshooting" - },"5362": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#related-topics" - },"5363": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html", - - "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html" - },"5364": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#telemetry--sensors" - },"5365": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#overview", - - "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#overview" - },"5366": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | 설명 | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | 전압 | Battery voltage | 3.0–4.2V (LiPo) | . | 채널 사용 | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | 업타임 | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#device-telemetry" - },"5367": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | 온도 | 습도 | 기압 | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#environment-sensors" - },"5368": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | 설명 | . | Bus Voltage | Supply rail voltage | . | 전류 | Power consumption (mA) | . | 전원 | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#power-metrics" - },"5369": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#configuring-telemetry" - },"5370": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | 설명 | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#air-quality-metrics" - },"5371": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#viewing-telemetry" - },"5372": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#troubleshooting" - },"5373": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#related-topics" - },"5374": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html", - - "relUrl": "/ko-rKR/user/telemetry-and-sensors.html" - },"5375": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#telemetry--sensors" - },"5376": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#overview", - - "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#overview" - },"5377": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Descriere | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Tensiune | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Timp de functionare | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#device-telemetry" - },"5378": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Senzor | Temperature | Humidity | Presiune | Notițe | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Senzor | Metric | Notițe | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Senzor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#environment-sensors" - },"5379": { - "doc": "Telemetry & Sensors", - "title": "Valori putere", - "content": "Nodes with INA-series power sensors can report: . | Metric | Descriere | . | Bus Voltage | Supply rail voltage | . | Actual | Power consumption (mA) | . | Alimentare | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#valori-putere", - - "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#valori-putere" - },"5380": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#configuring-telemetry" - },"5381": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Descriere | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#air-quality-metrics" - },"5382": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#viewing-telemetry" - },"5383": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#troubleshooting" - },"5384": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#related-topics" - },"5385": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html", - - "relUrl": "/ro-rRO/user/telemetry-and-sensors.html" - },"5386": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#telemetry--sensors" - },"5387": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#overview", - - "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#overview" - },"5388": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Cur síos | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Úsáid cainéil | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#device-telemetry" - },"5389": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Teocht | Laige | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#environment-sensors" - },"5390": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Cur síos | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#power-metrics" - },"5391": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#configuring-telemetry" - },"5392": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Cur síos | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#air-quality-metrics" - },"5393": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#viewing-telemetry" - },"5394": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#troubleshooting" - },"5395": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#related-topics" - },"5396": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html", - - "relUrl": "/ga-rIE/user/telemetry-and-sensors.html" - },"5397": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#telemetry--sensors" - },"5398": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#overview", - - "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#overview" - },"5399": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | תיאור | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#device-telemetry" - },"5400": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperature | Humidity | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#environment-sensors" - },"5401": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | תיאור | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#power-metrics" - },"5402": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#configuring-telemetry" - },"5403": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | תיאור | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#air-quality-metrics" - },"5404": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#viewing-telemetry" - },"5405": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#troubleshooting" - },"5406": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#related-topics" - },"5407": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html", - - "relUrl": "/iw-rIL/user/telemetry-and-sensors.html" - },"5408": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#telemetry--sensors" - },"5409": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#overview", - - "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#overview" - },"5410": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Beskrivning | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Spänning | Battery voltage | 3.0–4.2V (LiPo) | . | Kanalutnyttjande | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Upptid | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#device-telemetry" - },"5411": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatur | Luftfuktighet | Tryck | Anteckningar | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Anteckningar | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#environment-sensors" - },"5412": { - "doc": "Telemetry & Sensors", - "title": "Strömdata", - "content": "Nodes with INA-series power sensors can report: . | Metric | Beskrivning | . | Bus Voltage | Supply rail voltage | . | Ström | Power consumption (mA) | . | Ström | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#str%C3%B6mdata", - - "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#strömdata" - },"5413": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#configuring-telemetry" - },"5414": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Beskrivning | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#air-quality-metrics" - },"5415": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#viewing-telemetry" - },"5416": { - "doc": "Telemetry & Sensors", - "title": "Felsökning", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#fels%C3%B6kning", - - "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#felsökning" - },"5417": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#related-topics" - },"5418": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html", - - "relUrl": "/sv-rSE/user/telemetry-and-sensors.html" - },"5419": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#telemetry--sensors" - },"5420": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#overview", - - "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#overview" - },"5421": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Deskripsyon | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Itilizasyon Kanal | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#device-telemetry" - },"5422": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Tanperati | Imidite | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#environment-sensors" - },"5423": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Deskripsyon | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#power-metrics" - },"5424": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#configuring-telemetry" - },"5425": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Deskripsyon | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#air-quality-metrics" - },"5426": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#viewing-telemetry" - },"5427": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#troubleshooting" - },"5428": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#related-topics" - },"5429": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html", - - "relUrl": "/ht-rHT/user/telemetry-and-sensors.html" - },"5430": { - "doc": "Telemetria ja anturit", - "title": "Telemetria ja anturit", - "content": "Meshtastic-radiot voivat kerätä ja jakaa anturitietoja koko verkon laajuisesti. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html", - - "relUrl": "/fi-rFI/user/telemetry-and-sensors.html" - },"5431": { - "doc": "Telemetria ja anturit", - "title": "Yleiskatsaus", - "content": "Telemetria mahdollistaa antureilla varustettujen radioiden ympäristö-, virta- ja laitteen kuntotietojen lähettämisen verkkoon. Nämä tiedot näkyvät radion tietonäytössä ja niitä voidaan tallentaa sekä seurata ajan kuluessa. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#yleiskatsaus", - - "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#yleiskatsaus" - },"5432": { - "doc": "Telemetria ja anturit", - "title": "Laitteen telemetriatiedot", - "content": "Kaikki Meshtastic-radiot raportoivat peruslaitetelemetrian: . | Metrijärjestelmä | Kuvaus | Tyypillinen vaihteluväli | . | Akun varaustaso | Varausprosentti | 0–100% | . | Jännite | Akun jännite | 3.0–4.2V (LiPo) | . | Kanavan Käyttö | Paikallisesti käytetyn käyttöasteen prosenttiosuus | 0–100% | . | Lähetysajan käyttöaste (TX) | Tämän radion käyttämän lähetysajan prosenttiosuus | 0–100% | . | Käyttöaika | Sekuntia viimeisestä käynnistyksestä | Vaihtelee | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#laitteen-telemetriatiedot", - - "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#laitteen-telemetriatiedot" - },"5433": { - "doc": "Telemetria ja anturit", - "title": "Ympäristöanturit", - "content": "Tuetut ympäristöanturit: . Lämpötila ja kosteus . | Sensor | Lämpötila | Kosteus | Ilmanpaine | Viestit | . | BME280 | ✓ | ✓ | ✓ | Suositeltu all-in-one-anturi | . | BME680 | ✓ | ✓ | ✓ | Lisää kaasuvastus ja IAQ-mittaukset | . | SHT31 | ✓ | ✓ | — | Korkea tarkkuus | . | MCP9808 | ✓ | — | — | Tarkka lämpötilamittaus | . | LPS22 | — | — | ✓ | Vain ilmanpaine | . Ilmanlaatu . | Sensor | Metrijärjestelmä | Viestit | . | BME680 | Kaasuvastus ja IAQ | Haihtuvat orgaaniset yhdisteet | . | PMSA003I | PM1.0, PM2.5, PM10 | Hiukkaset | . | SEN55 | PM, NOx, VOC, lämpötila, kosteus | Monianturi | . Valo ja UV . | Sensor | Metrijärjestelmä | . | OPT3001 | Ympäristön valoisuus (lux) | . | VEML7700 | Ympäristön valoisuus (lux) | . | LTR390 | UV-indeksi | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#ymp%C3%A4rist%C3%B6anturit", - - "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#ympäristöanturit" - },"5434": { - "doc": "Telemetria ja anturit", - "title": "Virranhallinnan arvot", - "content": "INA-sarjan virta-antureilla varustetut radiot voivat raportoida: . | Metrijärjestelmä | Kuvaus | . | Väyläjännite | Syöttöjännitteen | . | Virta | Virrankulutuksen (mA) | . | Virta | Lasketun tehon (mW) | . Hyödyllinen aurinkolatauksen tai etäradioiden akun kunnon seurantaan. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#virranhallinnan-arvot", - - "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#virranhallinnan-arvot" - },"5435": { - "doc": "Telemetria ja anturit", - "title": "Telemetrian määrittäminen", - "content": ". | Siirry kohtaan Asetukset → Moduuliasetukset → Telemetria | Määritä raportointivälit: . | Laitemittarien väli — kuinka usein laitteen mittarit lähetetään verkkoon | Ympäristömittarien väli — kuinka usein anturitiedot lähetetään verkkoon | . | Ota tarvittavat anturityypit käyttöön. | . Suositellut raportointivälit . | Käyttötarkoitus | Laite (s) | Ympäristö (s) | . | Kaupunkiverkko (paljon radioita) | 3600 | 3600 | . | Maaseutuverkko (vähän radioita) | 900 | 900 | . | Sääasema | 900 | 300 | . | Akun säästäminen | 7200 | 7200 | . ⚠️ Huomautus: Lyhyemmät välit lisäävät käyttöastetta ja akun kulutusta koko verkossa. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#telemetrian-m%C3%A4%C3%A4ritt%C3%A4minen", - - "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#telemetrian-määrittäminen" - },"5436": { - "doc": "Telemetria ja anturit", - "title": "Ilmanlaatumittarit", - "content": "Hiukkas- tai CO₂-antureilla varustetut radiot raportoivat ilmanlaatutietoja: . | Metrijärjestelmä | Yksikkö | Kuvaus | . | PM1.0 | µg/m³ | Erittäin pienet hiukkaset | . | PM2.5 | µg/m³ | Pienhiukkaset | . | PM10 | µg/m³ | Karkeat hiukkaset | . | CO₂ | ppm | Hiilidioksidipitoisuus | . Myös CO₂ anturit, kuten SCD4x, ilmoittavat oman lämpötilansa ja ilmankosteutensa, jotka näytetään edellä olevien mittausten yhteydessä. PM2.5-historiasta sovellus laskee lisäksi EPA NowCast AQI -arvon. CO₂-arvo on värikoodattu vakavuuden mukaan (Hyvä → Tunkkainen → Huono → Epäturvallinen → Evakuoi). Katso Radion mittarit — Ilmanlaatu, josta löytyvät tarkat ppm-arvot, värit ja AQI-luokituksen tiedot. Ilmanlaatutiedot voidaan näyttää tietokortteina radion tietonäytössä, esittää kaavioina ajan kuluessa ja viedä CSV-tiedostoon. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#ilmanlaatumittarit", - - "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#ilmanlaatumittarit" - },"5437": { - "doc": "Telemetria ja anturit", - "title": "Telemetrian tarkastelu", - "content": ". | Siirry kohtaan Radiot ja valitse radio. | Telemetriaosiot näkyvät radion tietonäytössä: . | Laitemittarit (aina käytettävissä) | Ympäristömittarit (jos antureita on saatavilla) | Virtamittarit (jos INA-anturi on käytettävissä) | Ilmanlaatumittarit (jos PM-/CO₂-anturi on käytettävissä) | . | Historiakaaviot näyttävät mittaustietojen kehittymisen ajan kuluessa. | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#telemetrian-tarkastelu", - - "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#telemetrian-tarkastelu" - },"5438": { - "doc": "Telemetria ja anturit", - "title": "Vianetsintä", - "content": ". | Ympäristötiedot eivät näy? Etäradio tarvitsee fyysisen anturin (esim. BME280 I²C-väylässä). Laitetelemetria (akun varaustaso, käyttöaika) on aina käytettävissä, mutta ympäristömittarit edellyttävät laitteistoa. | Vanhentuneita lukemia? Tarkista raportointiväli — erittäin pitkät välit (7200 s tai enemmän) tarkoittavat, että tiedot päivittyvät harvoin. Varmista myös, että etäradio on edelleen verkossa. | Anturiristiriita I²C-väylässä? Jotkin anturit käyttävät samoja I²C-osoitteita. Jos samalla väylällä on useita antureita, tarkista osoiteristiriidat radion sarjaportin virheenkorjaustulosteesta. | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#vianetsint%C3%A4", - - "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#vianetsintä" - },"5439": { - "doc": "Telemetria ja anturit", - "title": "Aiheeseen liittyvät aiheet", - "content": ". | Radion mittarit — tarkastele telemetriatietoja radion tietonäytössä | Asetukset — Moduulit ja ylläpito — telemetriamoduulin määritys | Yksiköt ja aluekohtaiset asetukset — lämpötilan ja ilmanpaineen näyttöyksiköt | . ", - "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#aiheeseen-liittyv%C3%A4t-aiheet", - - "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#aiheeseen-liittyvät-aiheet" - },"5440": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/gl-rES/user/telemetry-and-sensors.html#telemetry--sensors" - },"5441": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#overview", - - "relUrl": "/gl-rES/user/telemetry-and-sensors.html#overview" - },"5442": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Descrición | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/gl-rES/user/telemetry-and-sensors.html#device-telemetry" - },"5443": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperature | Humidity | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/gl-rES/user/telemetry-and-sensors.html#environment-sensors" - },"5444": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Descrición | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/gl-rES/user/telemetry-and-sensors.html#power-metrics" - },"5445": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/gl-rES/user/telemetry-and-sensors.html#configuring-telemetry" - },"5446": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Descrición | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/gl-rES/user/telemetry-and-sensors.html#air-quality-metrics" - },"5447": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/gl-rES/user/telemetry-and-sensors.html#viewing-telemetry" - },"5448": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/gl-rES/user/telemetry-and-sensors.html#troubleshooting" - },"5449": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/gl-rES/user/telemetry-and-sensors.html#related-topics" - },"5450": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html", - - "relUrl": "/gl-rES/user/telemetry-and-sensors.html" - },"5451": { - "doc": "Телеметрія і сенсори", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#telemetry--sensors" - },"5452": { - "doc": "Телеметрія і сенсори", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#overview", - - "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#overview" - },"5453": { - "doc": "Телеметрія і сенсори", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Опис | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Напруга | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Час роботи | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#device-telemetry" - },"5454": { - "doc": "Телеметрія і сенсори", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Датчик | Температура | Вологість | Атмосферний тиск | Нотатки | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Датчик | Metric | Нотатки | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Датчик | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#environment-sensors" - },"5455": { - "doc": "Телеметрія і сенсори", - "title": "Показники живлення", - "content": "Nodes with INA-series power sensors can report: . | Metric | Опис | . | Bus Voltage | Supply rail voltage | . | Поточний | Power consumption (mA) | . | Живлення | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.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/telemetry-and-sensors.html#показники-живлення" - },"5456": { - "doc": "Телеметрія і сенсори", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#configuring-telemetry" - },"5457": { - "doc": "Телеметрія і сенсори", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Опис | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#air-quality-metrics" - },"5458": { - "doc": "Телеметрія і сенсори", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#viewing-telemetry" - },"5459": { - "doc": "Телеметрія і сенсори", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#troubleshooting" - },"5460": { - "doc": "Телеметрія і сенсори", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#related-topics" - },"5461": { - "doc": "Телеметрія і сенсори", - "title": "Телеметрія і сенсори", - "content": " ", - "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html", - - "relUrl": "/uk-rUA/user/telemetry-and-sensors.html" - },"5462": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", "url": "/Meshtastic-Android/main/de-rDE/user/telemetry-and-sensors.html#telemetry--sensors", "relUrl": "/de-rDE/user/telemetry-and-sensors.html#telemetry--sensors" - },"5463": { + },"5322": { "doc": "Telemetry & Sensors", "title": "Übersicht", "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", "url": "/Meshtastic-Android/main/de-rDE/user/telemetry-and-sensors.html#%C3%BCbersicht", "relUrl": "/de-rDE/user/telemetry-and-sensors.html#übersicht" - },"5464": { + },"5323": { "doc": "Telemetry & Sensors", "title": "Gerätetelemetrie", "content": "All Meshtastic nodes report basic device telemetry: . | Metrisch | Beschreibung | Typical Range | . | Batterie Ladung | Charge percentage | 0–100% | . | Spannung | Battery voltage | 3.0–4.2V (LiPo) | . | Kanalbelegung | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Laufzeit | Seconds since last boot | Varies | . ", "url": "/Meshtastic-Android/main/de-rDE/user/telemetry-and-sensors.html#ger%C3%A4tetelemetrie", "relUrl": "/de-rDE/user/telemetry-and-sensors.html#gerätetelemetrie" - },"5465": { + },"5324": { "doc": "Telemetry & Sensors", "title": "Environment Sensors", "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatur | Luftfeuchtigkeit | Druck | Knoten | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metrisch | Knoten | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metrisch | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", "url": "/Meshtastic-Android/main/de-rDE/user/telemetry-and-sensors.html#environment-sensors", "relUrl": "/de-rDE/user/telemetry-and-sensors.html#environment-sensors" - },"5466": { + },"5325": { "doc": "Telemetry & Sensors", "title": "Energiedaten", "content": "Nodes with INA-series power sensors can report: . | Metrisch | Beschreibung | . | Bus Voltage | Supply rail voltage | . | Stromstärke | Power consumption (mA) | . | Leistung | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", "url": "/Meshtastic-Android/main/de-rDE/user/telemetry-and-sensors.html#energiedaten", "relUrl": "/de-rDE/user/telemetry-and-sensors.html#energiedaten" - },"5467": { + },"5326": { "doc": "Telemetry & Sensors", "title": "Configuring Telemetry", "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", "url": "/Meshtastic-Android/main/de-rDE/user/telemetry-and-sensors.html#configuring-telemetry", "relUrl": "/de-rDE/user/telemetry-and-sensors.html#configuring-telemetry" - },"5468": { + },"5327": { "doc": "Telemetry & Sensors", "title": "Air Quality Metrics", "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metrisch | Einheit | Beschreibung | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", "url": "/Meshtastic-Android/main/de-rDE/user/telemetry-and-sensors.html#air-quality-metrics", "relUrl": "/de-rDE/user/telemetry-and-sensors.html#air-quality-metrics" - },"5469": { + },"5328": { "doc": "Telemetry & Sensors", "title": "Viewing Telemetry", "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", "url": "/Meshtastic-Android/main/de-rDE/user/telemetry-and-sensors.html#viewing-telemetry", "relUrl": "/de-rDE/user/telemetry-and-sensors.html#viewing-telemetry" - },"5470": { + },"5329": { "doc": "Telemetry & Sensors", "title": "Fehlerbehebung", "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", "url": "/Meshtastic-Android/main/de-rDE/user/telemetry-and-sensors.html#fehlerbehebung", "relUrl": "/de-rDE/user/telemetry-and-sensors.html#fehlerbehebung" - },"5471": { + },"5330": { "doc": "Telemetry & Sensors", "title": "Related Topics", "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", "url": "/Meshtastic-Android/main/de-rDE/user/telemetry-and-sensors.html#related-topics", "relUrl": "/de-rDE/user/telemetry-and-sensors.html#related-topics" - },"5472": { + },"5331": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": " ", "url": "/Meshtastic-Android/main/de-rDE/user/telemetry-and-sensors.html", "relUrl": "/de-rDE/user/telemetry-and-sensors.html" - },"5473": { + },"5332": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#telemetry--sensors", + "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#telemetry--sensors", - "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#telemetry--sensors" - },"5474": { + "relUrl": "/ca-rES/user/telemetry-and-sensors.html#telemetry--sensors" + },"5333": { "doc": "Telemetry & Sensors", "title": "Overview", "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#overview", + "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#overview", - "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#overview" - },"5475": { + "relUrl": "/ca-rES/user/telemetry-and-sensors.html#overview" + },"5334": { "doc": "Telemetry & Sensors", "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Opis | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#device-telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Descripció | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#device-telemetry", - "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#device-telemetry" - },"5476": { + "relUrl": "/ca-rES/user/telemetry-and-sensors.html#device-telemetry" + },"5335": { "doc": "Telemetry & Sensors", "title": "Environment Sensors", "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperature | Humidity | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#environment-sensors", + "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#environment-sensors", - "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#environment-sensors" - },"5477": { + "relUrl": "/ca-rES/user/telemetry-and-sensors.html#environment-sensors" + },"5336": { "doc": "Telemetry & Sensors", "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Opis | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#power-metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Descripció | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#power-metrics", - "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#power-metrics" - },"5478": { + "relUrl": "/ca-rES/user/telemetry-and-sensors.html#power-metrics" + },"5337": { "doc": "Telemetry & Sensors", "title": "Configuring Telemetry", "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#configuring-telemetry", + "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#configuring-telemetry", - "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#configuring-telemetry" - },"5479": { + "relUrl": "/ca-rES/user/telemetry-and-sensors.html#configuring-telemetry" + },"5338": { "doc": "Telemetry & Sensors", "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Opis | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#air-quality-metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Descripció | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#air-quality-metrics", - "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#air-quality-metrics" - },"5480": { + "relUrl": "/ca-rES/user/telemetry-and-sensors.html#air-quality-metrics" + },"5339": { "doc": "Telemetry & Sensors", "title": "Viewing Telemetry", "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#viewing-telemetry", + "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#viewing-telemetry", - "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#viewing-telemetry" - },"5481": { + "relUrl": "/ca-rES/user/telemetry-and-sensors.html#viewing-telemetry" + },"5340": { "doc": "Telemetry & Sensors", "title": "Troubleshooting", "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#troubleshooting", + "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#troubleshooting", - "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#troubleshooting" - },"5482": { + "relUrl": "/ca-rES/user/telemetry-and-sensors.html#troubleshooting" + },"5341": { "doc": "Telemetry & Sensors", "title": "Related Topics", "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#related-topics", + "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html#related-topics", - "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#related-topics" - },"5483": { + "relUrl": "/ca-rES/user/telemetry-and-sensors.html#related-topics" + },"5342": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": " ", - "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html", + "url": "/Meshtastic-Android/main/ca-rES/user/telemetry-and-sensors.html", - "relUrl": "/hr-rHR/user/telemetry-and-sensors.html" - },"5484": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#telemetry--sensors" - },"5485": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#overview", - - "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#overview" - },"5486": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Aprašymas | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Kanalo panaudojimas | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#device-telemetry" - },"5487": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatūra | Drėgmė | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#environment-sensors" - },"5488": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Aprašymas | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#power-metrics" - },"5489": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#configuring-telemetry" - },"5490": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Aprašymas | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#air-quality-metrics" - },"5491": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#viewing-telemetry" - },"5492": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#troubleshooting" - },"5493": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#related-topics" - },"5494": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html", - - "relUrl": "/lt-rLT/user/telemetry-and-sensors.html" - },"5495": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/en/user/telemetry-and-sensors.html#telemetry--sensors" - },"5496": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#overview", - - "relUrl": "/en/user/telemetry-and-sensors.html#overview" - },"5497": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Description | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/en/user/telemetry-and-sensors.html#device-telemetry" - },"5498": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperature | Humidity | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/en/user/telemetry-and-sensors.html#environment-sensors" - },"5499": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Description | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/en/user/telemetry-and-sensors.html#power-metrics" - },"5500": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/en/user/telemetry-and-sensors.html#configuring-telemetry" - },"5501": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Description | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/en/user/telemetry-and-sensors.html#air-quality-metrics" - },"5502": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/en/user/telemetry-and-sensors.html#viewing-telemetry" - },"5503": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/en/user/telemetry-and-sensors.html#troubleshooting" - },"5504": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/en/user/telemetry-and-sensors.html#related-topics" - },"5505": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html", - - "relUrl": "/en/user/telemetry-and-sensors.html" - },"5506": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#telemetry--sensors" - },"5507": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#overview", - - "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#overview" - },"5508": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Leírás | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Feszültség | Battery voltage | 3.0–4.2V (LiPo) | . | Csatornahasználat | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Működési idő | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#device-telemetry" - },"5509": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Szenzor | Hőmérséklet | Páratartalom | Nyomás | Jegyzetek | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Szenzor | Metric | Jegyzetek | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Szenzor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#environment-sensors" - },"5510": { - "doc": "Telemetry & Sensors", - "title": "Tápellátási metrikák", - "content": "Nodes with INA-series power sensors can report: . | Metric | Leírás | . | Bus Voltage | Supply rail voltage | . | Áramerősség | Power consumption (mA) | . | Energia | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#t%C3%A1pell%C3%A1t%C3%A1si-metrik%C3%A1k", - - "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#tápellátási-metrikák" - },"5511": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#configuring-telemetry" - },"5512": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Leírás | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#air-quality-metrics" - },"5513": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#viewing-telemetry" - },"5514": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#troubleshooting" - },"5515": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#related-topics" - },"5516": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html", - - "relUrl": "/hu-rHU/user/telemetry-and-sensors.html" - },"5517": { - "doc": "Телеметрия & Сензори", - "title": "Телеметрия & Сензори", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#%D1%82%D0%B5%D0%BB%D0%B5%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D1%8F--%D1%81%D0%B5%D0%BD%D0%B7%D0%BE%D1%80%D0%B8", - - "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#телеметрия--сензори" - },"5518": { - "doc": "Телеметрия & Сензори", - "title": "Преглед", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#%D0%BF%D1%80%D0%B5%D0%B3%D0%BB%D0%B5%D0%B4", - - "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#преглед" - },"5519": { - "doc": "Телеметрия & Сензори", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Метрични | Описание | Типичен диапазон | . | Ниво на батерията | Charge percentage | 0–100% | . | Напрежение | Напрежение на батерията | 3.0–4.2V (LiPo) | . | Използване на канала | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Време на работа | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#device-telemetry" - },"5520": { - "doc": "Телеметрия & Сензори", - "title": "Сензори за околна среда", - "content": "Поддържани сензори за околна среда: . Температура & Влажност . | Сензор | Температура | Влажност | Налягане | Бележки | . | BME280 | ✓ | ✓ | ✓ | Препоръчително многофункционално устройство | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | Висока точност | . | MCP9808 | ✓ | — | — | Прецизна температура | . | LPS22 | — | — | ✓ | Само налягане | . Качество на въздуха . | Сензор | Метрични | Бележки | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Светлина & UV . | Сензор | Метрични | . | OPT3001 | Околна светлина (lux) | . | VEML7700 | Околна светлина (lux) | . | LTR390 | UV индекс | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#%D1%81%D0%B5%D0%BD%D0%B7%D0%BE%D1%80%D0%B8-%D0%B7%D0%B0-%D0%BE%D0%BA%D0%BE%D0%BB%D0%BD%D0%B0-%D1%81%D1%80%D0%B5%D0%B4%D0%B0", - - "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#сензори-за-околна-среда" - },"5521": { - "doc": "Телеметрия & Сензори", - "title": "Показатели на мощност", - "content": "Nodes with INA-series power sensors can report: . | Метрични | Описание | . | Bus Voltage | Supply rail voltage | . | Текущ | Power consumption (mA) | . | Захранване | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.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/telemetry-and-sensors.html#показатели-на-мощност" - },"5522": { - "doc": "Телеметрия & Сензори", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Метеорологична станция | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#configuring-telemetry" - },"5523": { - "doc": "Телеметрия & Сензори", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Метрични | Unit | Описание | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#air-quality-metrics" - },"5524": { - "doc": "Телеметрия & Сензори", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#viewing-telemetry" - },"5525": { - "doc": "Телеметрия & Сензори", - "title": "Отстраняване на неизправности", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.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/telemetry-and-sensors.html#отстраняване-на-неизправности" - },"5526": { - "doc": "Телеметрия & Сензори", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#related-topics" - },"5527": { - "doc": "Телеметрия & Сензори", - "title": "Телеметрия & Сензори", - "content": " ", - "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html", - - "relUrl": "/bg-rBG/user/telemetry-and-sensors.html" - },"5528": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#telemetry--sensors" - },"5529": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#overview", - - "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#overview" - },"5530": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Opis | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Uporaba kanala | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#device-telemetry" - },"5531": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatura | Vlaga | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#environment-sensors" - },"5532": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Opis | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#power-metrics" - },"5533": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#configuring-telemetry" - },"5534": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Opis | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#air-quality-metrics" - },"5535": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#viewing-telemetry" - },"5536": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#troubleshooting" - },"5537": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#related-topics" - },"5538": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html", - - "relUrl": "/sl-rSI/user/telemetry-and-sensors.html" - },"5539": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#telemetry--sensors" - },"5540": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#overview", - - "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#overview" - },"5541": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Descrição | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltagem | Battery voltage | 3.0–4.2V (LiPo) | . | Utilização do canal | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Tempo ativo | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#device-telemetry" - },"5542": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatura | Humidade | Pressão | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#environment-sensors" - },"5543": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Descrição | . | Bus Voltage | Supply rail voltage | . | Atual | Power consumption (mA) | . | Energia | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#power-metrics" - },"5544": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#configuring-telemetry" - },"5545": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Descrição | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#air-quality-metrics" - },"5546": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#viewing-telemetry" - },"5547": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#troubleshooting" - },"5548": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#related-topics" - },"5549": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html", - - "relUrl": "/pt-rPT/user/telemetry-and-sensors.html" - },"5550": { + "relUrl": "/ca-rES/user/telemetry-and-sensors.html" + },"5343": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", "url": "/Meshtastic-Android/main/be-rBY/user/telemetry-and-sensors.html#telemetry--sensors", "relUrl": "/be-rBY/user/telemetry-and-sensors.html#telemetry--sensors" - },"5551": { + },"5344": { "doc": "Telemetry & Sensors", "title": "Абзор", "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", "url": "/Meshtastic-Android/main/be-rBY/user/telemetry-and-sensors.html#%D0%B0%D0%B1%D0%B7%D0%BE%D1%80", "relUrl": "/be-rBY/user/telemetry-and-sensors.html#абзор" - },"5552": { + },"5345": { "doc": "Telemetry & Sensors", "title": "Device Telemetry", "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Апісанне | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", "url": "/Meshtastic-Android/main/be-rBY/user/telemetry-and-sensors.html#device-telemetry", "relUrl": "/be-rBY/user/telemetry-and-sensors.html#device-telemetry" - },"5553": { + },"5346": { "doc": "Telemetry & Sensors", "title": "Environment Sensors", "content": "Supported environmental sensors: . Temperature & Humidity . | SENSOR | Тэмпература | Вільготнасць | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | SENSOR | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | SENSOR | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", "url": "/Meshtastic-Android/main/be-rBY/user/telemetry-and-sensors.html#environment-sensors", "relUrl": "/be-rBY/user/telemetry-and-sensors.html#environment-sensors" - },"5554": { + },"5347": { "doc": "Telemetry & Sensors", "title": "Power Metrics", "content": "Nodes with INA-series power sensors can report: . | Metric | Апісанне | . | Bus Voltage | Supply rail voltage | . | 3 | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", "url": "/Meshtastic-Android/main/be-rBY/user/telemetry-and-sensors.html#power-metrics", "relUrl": "/be-rBY/user/telemetry-and-sensors.html#power-metrics" - },"5555": { + },"5348": { "doc": "Telemetry & Sensors", "title": "Configuring Telemetry", "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", "url": "/Meshtastic-Android/main/be-rBY/user/telemetry-and-sensors.html#configuring-telemetry", "relUrl": "/be-rBY/user/telemetry-and-sensors.html#configuring-telemetry" - },"5556": { + },"5349": { "doc": "Telemetry & Sensors", "title": "Air Quality Metrics", "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Апісанне | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", "url": "/Meshtastic-Android/main/be-rBY/user/telemetry-and-sensors.html#air-quality-metrics", "relUrl": "/be-rBY/user/telemetry-and-sensors.html#air-quality-metrics" - },"5557": { + },"5350": { "doc": "Telemetry & Sensors", "title": "Viewing Telemetry", "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", "url": "/Meshtastic-Android/main/be-rBY/user/telemetry-and-sensors.html#viewing-telemetry", "relUrl": "/be-rBY/user/telemetry-and-sensors.html#viewing-telemetry" - },"5558": { + },"5351": { "doc": "Telemetry & Sensors", "title": "Troubleshooting", "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", "url": "/Meshtastic-Android/main/be-rBY/user/telemetry-and-sensors.html#troubleshooting", "relUrl": "/be-rBY/user/telemetry-and-sensors.html#troubleshooting" - },"5559": { + },"5352": { "doc": "Telemetry & Sensors", "title": "Related Topics", "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", "url": "/Meshtastic-Android/main/be-rBY/user/telemetry-and-sensors.html#related-topics", "relUrl": "/be-rBY/user/telemetry-and-sensors.html#related-topics" - },"5560": { + },"5353": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": " ", "url": "/Meshtastic-Android/main/be-rBY/user/telemetry-and-sensors.html", "relUrl": "/be-rBY/user/telemetry-and-sensors.html" - },"5561": { - "doc": "Telemetry & Sensors", + },"5354": { + "doc": "Телеметрія і сенсори", "title": "Telemetry & Sensors", "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#telemetry--sensors", + "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#telemetry--sensors", - "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#telemetry--sensors" - },"5562": { - "doc": "Telemetry & Sensors", + "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#telemetry--sensors" + },"5355": { + "doc": "Телеметрія і сенсори", "title": "Overview", "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#overview", + "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#overview", - "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#overview" - },"5563": { - "doc": "Telemetry & Sensors", + "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#overview" + },"5356": { + "doc": "Телеметрія і сенсори", "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Descrição | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltagem | Battery voltage | 3.0–4.2V (LiPo) | . | Utilização do Canal | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#device-telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Опис | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Напруга | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Час роботи | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#device-telemetry", - "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#device-telemetry" - },"5564": { - "doc": "Telemetry & Sensors", + "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#device-telemetry" + },"5357": { + "doc": "Телеметрія і сенсори", "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatura | Umidade | Pressão | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#environment-sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Датчик | Температура | Вологість | Атмосферний тиск | Нотатки | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Датчик | Metric | Нотатки | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Датчик | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#environment-sensors", - "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#environment-sensors" - },"5565": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Descrição | . | Bus Voltage | Supply rail voltage | . | Atual | Power consumption (mA) | . | Energia | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#power-metrics", + "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#environment-sensors" + },"5358": { + "doc": "Телеметрія і сенсори", + "title": "Показники живлення", + "content": "Nodes with INA-series power sensors can report: . | Metric | Опис | . | Bus Voltage | Supply rail voltage | . | Поточний | Power consumption (mA) | . | Живлення | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.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": "/pt-rBR/user/telemetry-and-sensors.html#power-metrics" - },"5566": { - "doc": "Telemetry & Sensors", + "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#показники-живлення" + },"5359": { + "doc": "Телеметрія і сенсори", "title": "Configuring Telemetry", "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#configuring-telemetry", + "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#configuring-telemetry", - "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#configuring-telemetry" - },"5567": { - "doc": "Telemetry & Sensors", + "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#configuring-telemetry" + },"5360": { + "doc": "Телеметрія і сенсори", "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Descrição | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#air-quality-metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Опис | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#air-quality-metrics", - "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#air-quality-metrics" - },"5568": { - "doc": "Telemetry & Sensors", + "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#air-quality-metrics" + },"5361": { + "doc": "Телеметрія і сенсори", "title": "Viewing Telemetry", "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#viewing-telemetry", + "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#viewing-telemetry", - "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#viewing-telemetry" - },"5569": { - "doc": "Telemetry & Sensors", + "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#viewing-telemetry" + },"5362": { + "doc": "Телеметрія і сенсори", "title": "Troubleshooting", "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#troubleshooting", + "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#troubleshooting", - "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#troubleshooting" - },"5570": { - "doc": "Telemetry & Sensors", + "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#troubleshooting" + },"5363": { + "doc": "Телеметрія і сенсори", "title": "Related Topics", "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#related-topics", + "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html#related-topics", - "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#related-topics" - },"5571": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", + "relUrl": "/uk-rUA/user/telemetry-and-sensors.html#related-topics" + },"5364": { + "doc": "Телеметрія і сенсори", + "title": "Телеметрія і сенсори", "content": " ", - "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html", + "url": "/Meshtastic-Android/main/uk-rUA/user/telemetry-and-sensors.html", - "relUrl": "/pt-rBR/user/telemetry-and-sensors.html" - },"5572": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/el-rGR/user/telemetry-and-sensors.html#telemetry--sensors" - },"5573": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#overview", - - "relUrl": "/el-rGR/user/telemetry-and-sensors.html#overview" - },"5574": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Περιγραφή | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Τάση | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/el-rGR/user/telemetry-and-sensors.html#device-telemetry" - },"5575": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Θερμοκρασία | Υγρασία | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/el-rGR/user/telemetry-and-sensors.html#environment-sensors" - },"5576": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Περιγραφή | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/el-rGR/user/telemetry-and-sensors.html#power-metrics" - },"5577": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/el-rGR/user/telemetry-and-sensors.html#configuring-telemetry" - },"5578": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Περιγραφή | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/el-rGR/user/telemetry-and-sensors.html#air-quality-metrics" - },"5579": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/el-rGR/user/telemetry-and-sensors.html#viewing-telemetry" - },"5580": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/el-rGR/user/telemetry-and-sensors.html#troubleshooting" - },"5581": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/el-rGR/user/telemetry-and-sensors.html#related-topics" - },"5582": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html", - - "relUrl": "/el-rGR/user/telemetry-and-sensors.html" - },"5583": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/es-rES/user/telemetry-and-sensors.html#telemetry--sensors" - },"5584": { - "doc": "Telemetry & Sensors", - "title": "Visión general", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#visi%C3%B3n-general", - - "relUrl": "/es-rES/user/telemetry-and-sensors.html#visión-general" - },"5585": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Métrico | Descripción | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Tensión | Battery voltage | 3.0–4.2V (LiPo) | . | Utilización del canal | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Tiempo encendido | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/es-rES/user/telemetry-and-sensors.html#device-telemetry" - },"5586": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatura: | Humedad | Presión | Notas | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Métrico | Notas | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Métrico | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/es-rES/user/telemetry-and-sensors.html#environment-sensors" - },"5587": { - "doc": "Telemetry & Sensors", - "title": "Métricas de Energía", - "content": "Nodes with INA-series power sensors can report: . | Métrico | Descripción | . | Bus Voltage | Supply rail voltage | . | Intensidad | Power consumption (mA) | . | Consumo | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#m%C3%A9tricas-de-energ%C3%ADa", - - "relUrl": "/es-rES/user/telemetry-and-sensors.html#métricas-de-energía" - },"5588": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/es-rES/user/telemetry-and-sensors.html#configuring-telemetry" - },"5589": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Métrico | Unit | Descripción | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/es-rES/user/telemetry-and-sensors.html#air-quality-metrics" - },"5590": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/es-rES/user/telemetry-and-sensors.html#viewing-telemetry" - },"5591": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/es-rES/user/telemetry-and-sensors.html#troubleshooting" - },"5592": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/es-rES/user/telemetry-and-sensors.html#related-topics" - },"5593": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html", - - "relUrl": "/es-rES/user/telemetry-and-sensors.html" - },"5594": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#telemetry--sensors" - },"5595": { - "doc": "Telemetry & Sensors", - "title": "Genel Bakış", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#genel-bak%C4%B1%C5%9F", - - "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#genel-bakış" - },"5596": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Açıklaması | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltaj | Battery voltage | 3.0–4.2V (LiPo) | . | Kanal Kullanımı | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Çalışma Süresi | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#device-telemetry" - },"5597": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Sıcaklık | Nem | Basınç | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#environment-sensors" - },"5598": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Açıklaması | . | Bus Voltage | Supply rail voltage | . | Akım | Power consumption (mA) | . | Güç | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#power-metrics" - },"5599": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#configuring-telemetry" - },"5600": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Açıklaması | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#air-quality-metrics" - },"5601": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#viewing-telemetry" - },"5602": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#troubleshooting" - },"5603": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#related-topics" - },"5604": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html", - - "relUrl": "/tr-rTR/user/telemetry-and-sensors.html" - },"5605": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/no-rNO/user/telemetry-and-sensors.html#telemetry--sensors" - },"5606": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#overview", - - "relUrl": "/no-rNO/user/telemetry-and-sensors.html#overview" - },"5607": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Beskrivelse | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Kanalutnyttelse | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/no-rNO/user/telemetry-and-sensors.html#device-telemetry" - },"5608": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatur | Luftfuktighet | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/no-rNO/user/telemetry-and-sensors.html#environment-sensors" - },"5609": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Beskrivelse | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/no-rNO/user/telemetry-and-sensors.html#power-metrics" - },"5610": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/no-rNO/user/telemetry-and-sensors.html#configuring-telemetry" - },"5611": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Beskrivelse | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/no-rNO/user/telemetry-and-sensors.html#air-quality-metrics" - },"5612": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/no-rNO/user/telemetry-and-sensors.html#viewing-telemetry" - },"5613": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/no-rNO/user/telemetry-and-sensors.html#troubleshooting" - },"5614": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/no-rNO/user/telemetry-and-sensors.html#related-topics" - },"5615": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html", - - "relUrl": "/no-rNO/user/telemetry-and-sensors.html" - },"5616": { - "doc": "Телеметрия и датчики", - "title": "Телеметрия и датчики", - "content": "Ноды Meshtastic могут собирать и передавать данные датчиков по всей mesh-сети. ", - "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html", - - "relUrl": "/ru-rRU/user/telemetry-and-sensors.html" - },"5617": { - "doc": "Телеметрия и датчики", - "title": "Обзор", - "content": "Телеметрия позволяет нодам, оснащённым датчиками, передавать информацию об окружающей среде, питании и состоянии устройства. Эти данные отображаются на экране сведений о ноде и могут регистрироваться с течением времени. ", - "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html#%D0%BE%D0%B1%D0%B7%D0%BE%D1%80", - - "relUrl": "/ru-rRU/user/telemetry-and-sensors.html#обзор" - },"5618": { - "doc": "Телеметрия и датчики", - "title": "Телеметрия устройства", - "content": "Все ноды Meshtastic передают базовую телеметрию устройства: . | Метрика | Описание | Типичный диапазон | . | Уровень заряда | Процент заряда | 0–100% | . | Напряжение | Напряжение батареи | 3.0–4.2V (LiPo) | . | Использование канала | % использованного локально эфирного времени | 0–100% | . | Использование эфира (TX) | % эфирного времени, использованного этой нодой | 0–100% | . | Аптайм | Секунд с последней загрузки | Варьируется | . ", - "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html#%D1%82%D0%B5%D0%BB%D0%B5%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D1%8F-%D1%83%D1%81%D1%82%D1%80%D0%BE%D0%B9%D1%81%D1%82%D0%B2%D0%B0", - - "relUrl": "/ru-rRU/user/telemetry-and-sensors.html#телеметрия-устройства" - },"5619": { - "doc": "Телеметрия и датчики", - "title": "Датчики окружающей среды", - "content": "Поддерживаемые датчики окружающей среды: . Температура и влажность . | Sensor | Температура | Влажность | Давление | Заметки | . | BME280 | ✓ | ✓ | ✓ | Рекомендуемый “всё в одном” | . | BME680 | ✓ | ✓ | ✓ | Добавляет сопротивление газа/IAQ | . | SHT31 | ✓ | ✓ | — | Высокая точность | . | MCP9808 | ✓ | — | — | Прецизионная температура | . | LPS22 | — | — | ✓ | Только давление | . Качество воздуха . | Sensor | Метрика | Заметки | . | BME680 | Сопротивление газа / IAQ | Летучие органические соединения | . | PMSA003I | PM1.0, PM2.5, PM10 | Взвешенные частицы | . | SEN55 | PM, NOx, VOC, температура, влажность | Мультисенсор | . Освещённость и УФ . | Sensor | Метрика | . | OPT3001 | Окружающая освещённость (люкс) | . | VEML7700 | Окружающая освещённость (люкс) | . | LTR390 | УФ-индекс | . ", - "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html#%D0%B4%D0%B0%D1%82%D1%87%D0%B8%D0%BA%D0%B8-%D0%BE%D0%BA%D1%80%D1%83%D0%B6%D0%B0%D1%8E%D1%89%D0%B5%D0%B9-%D1%81%D1%80%D0%B5%D0%B4%D1%8B", - - "relUrl": "/ru-rRU/user/telemetry-and-sensors.html#датчики-окружающей-среды" - },"5620": { - "doc": "Телеметрия и датчики", - "title": "Метрики питания", - "content": "Ноды с датчиками питания серии INA могут сообщать: . | Метрика | Описание | . | Напряжение шины | Напряжение линии питания | . | Ток | Потребляемый ток (мА) | . | Питание | Расчётная мощность (мВт) | . Полезно для мониторинга солнечной зарядки или состояния батареи на удалённых нодах. ", - "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.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/telemetry-and-sensors.html#метрики-питания" - },"5621": { - "doc": "Телеметрия и датчики", - "title": "Настройка телеметрии", - "content": ". | Перейдите в Настройки → Конфигурация модулей → Телеметрия. | Установите интервалы передачи: . | Интервал метрик устройства — как часто передавать метрики устройства | Интервал метрик окружающей среды — как часто передавать данные датчиков | . | Включайте нужные типы датчиков по необходимости. | . Рекомендуемые интервалы . | Сценарий использования | Устройство (сек.) | Окружающая среда (сек.) | . | Городская mesh-сеть (много нод) | 3600 | 3600 | . | Сельская mesh-сеть (мало нод) | 900 | 900 | . | Метеостанция | 900 | 300 | . | Экономия заряда батареи | 7200 | 7200 | . ⚠️ Примечание: Более короткие интервалы увеличивают использование эфирного времени и расход батареи во всей mesh-сети. ", - "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html#%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B0-%D1%82%D0%B5%D0%BB%D0%B5%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%B8", - - "relUrl": "/ru-rRU/user/telemetry-and-sensors.html#настройка-телеметрии" - },"5622": { - "doc": "Телеметрия и датчики", - "title": "Метрики качества воздуха", - "content": "Ноды с датчиками взвешенных частиц или CO₂ передают данные о качестве воздуха: . | Метрическая | Единица | Описание | . | PM1.0 | мкг/м³ | Ультрамелкие взвешенные частицы | . | PM2.5 | мкг/м³ | Мелкие взвешенные частицы | . | PM10 | мкг/м³ | Крупные взвешенные частицы | . | CO₂ | ppm | Концентрация углекислого газа | . Датчики CO₂, такие как SCD4x, также сообщают собственную температуру и влажность, которые отображаются вместе с указанными выше показаниями. На основе истории PM2.5 приложение дополнительно вычисляет значение AQI EPA по методу NowCast. Показания CO₂ окрашены по уровню опасности (Хорошо → Душно → Плохо → Опасно → Эвакуация). Точные диапазоны ppm, цвета и подробности AQI см. в разделе Метрики нод — Качество воздуха. Данные о качестве воздуха можно просматривать в виде информационных карточек на экране сведений о ноде, строить графики за период и экспортировать в CSV. ", - "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.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/telemetry-and-sensors.html#метрики-качества-воздуха" - },"5623": { - "doc": "Телеметрия и датчики", - "title": "Просмотр телеметрии", - "content": ". | Перейдите в Ноды и выберите ноду. | Разделы телеметрии отображаются на экране сведений: . | Метрики устройства (доступны всегда) | Метрики окружающей среды (при наличии датчиков) | Метрики питания (при наличии датчика INA) | Метрики качества воздуха (при наличии датчика PM/CO₂) | . | Исторические графики показывают тенденции с течением времени. | . ", - "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html#%D0%BF%D1%80%D0%BE%D1%81%D0%BC%D0%BE%D1%82%D1%80-%D1%82%D0%B5%D0%BB%D0%B5%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%B8", - - "relUrl": "/ru-rRU/user/telemetry-and-sensors.html#просмотр-телеметрии" - },"5624": { - "doc": "Телеметрия и датчики", - "title": "Устранение неполадок", - "content": ". | Нет данных об окружающей среде? К удалённой ноде должен быть физически подключён датчик (например, BME280 по I2C). Телеметрия устройства (заряд батареи, время работы) доступна всегда, но для метрик окружающей среды требуется оборудование. | Показания устарели? Проверьте интервал передачи — очень большие интервалы (7200 с и более) означают, что данные обновляются редко. Также убедитесь, что удалённая нода всё ещё в сети. | Конфликт датчиков на шине I2C? Некоторые датчики используют одинаковые адреса I2C. Если на одной шине несколько твоих датчиков, проверь последовательный отладочный вывод радио на предмет конфликтов адресов. | . ", - "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.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/telemetry-and-sensors.html#устранение-неполадок" - },"5625": { - "doc": "Телеметрия и датчики", - "title": "Связанные темы", - "content": ". | Метрики нод — просмотр данных телеметрии на экране сведений о ноде | Настройки — Модули и администрирование — конфигурация модуля телеметрии | Единицы измерения и регион — единицы отображения температуры и давления | . ", - "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.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/telemetry-and-sensors.html#связанные-темы" - },"5626": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#telemetry--sensors" - },"5627": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#overview", - - "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#overview" - },"5628": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Beschrijving | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Spanning | Battery voltage | 3.0–4.2V (LiPo) | . | Kanaalgebruik | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Tijd online | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#device-telemetry" - },"5629": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatuur | Vochtigheid | Druk | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#environment-sensors" - },"5630": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Beschrijving | . | Bus Voltage | Supply rail voltage | . | Huidige | Power consumption (mA) | . | Vermogen | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#power-metrics" - },"5631": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#configuring-telemetry" - },"5632": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Beschrijving | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#air-quality-metrics" - },"5633": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#viewing-telemetry" - },"5634": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#troubleshooting" - },"5635": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#related-topics" - },"5636": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html", - - "relUrl": "/nl-rNL/user/telemetry-and-sensors.html" - },"5637": { - "doc": "Telemeetria & Sensorid", - "title": "Telemetria & sensorid", - "content": "Meshtastic sõlmed saavad koguda ja jagada andurite andmeid kärgvõrgu kaudu. ", - "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#telemetria--sensorid", - - "relUrl": "/et-rEE/user/telemetry-and-sensors.html#telemetria--sensorid" - },"5638": { - "doc": "Telemeetria & Sensorid", - "title": "Ülevaade", - "content": "Telemeetria võimaldab anduritega varustatud sõlmedel levitada keskkonna-, energiatarbimise ja seadme terviseteavet. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#%C3%BClevaade", - - "relUrl": "/et-rEE/user/telemetry-and-sensors.html#ülevaade" - },"5639": { - "doc": "Telemeetria & Sensorid", - "title": "Device Telemetry", - "content": "Kõik Meshtastic sõlmed edastavad seadme põhitelemeetriat: . | Meetriline | Kirjeldus | Tüüpiline ulatus | . | Aku tase | Charge percentage | 0–100% | . | Vool | Aku pinge | 3,0–4,2V (LiPo) | . | Kanali kasutus | Kohalikult kasutatud eetriaja % | 0–100% | . | Eetri kasutus TX | Selle sõlme poolt kasutatud eetriaja % | 0–100% | . | Töötamise aeg | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/et-rEE/user/telemetry-and-sensors.html#device-telemetry" - },"5640": { - "doc": "Telemeetria & Sensorid", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Andur | Temperatuur | Niiskus | Õhurõhk | Sõnumid | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Andur | Meetriline | Sõnumid | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1,0, PM2,5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Valgus & UV . | Andur | Meetriline | . | OPT3001 | Ambient valgus (lux) | . | VEML7700 | Ambient valgus (lux) | . | LTR390 | UV indeks | . ", - "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/et-rEE/user/telemetry-and-sensors.html#environment-sensors" - },"5641": { - "doc": "Telemeetria & Sensorid", - "title": "Võimsusnäitajad", - "content": "Nodes with INA-series power sensors can report: . | Meetriline | Kirjeldus | . | Bus Voltage | Supply rail voltage | . | Pinge | Power consumption (mA) | . | Toide | Calculated power (mW) | . Kasulik päikesepaneelide laadimise või aku seisundi jälgimiseks kaugsõlmedes. ", - "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#v%C3%B5imsusn%C3%A4itajad", - - "relUrl": "/et-rEE/user/telemetry-and-sensors.html#võimsusnäitajad" - },"5642": { - "doc": "Telemeetria & Sensorid", - "title": "Configuring Telemetry", - "content": ". | Mine menüüsse Seaded → Mooduli konfiguratsioon → Telemeetria. | Set reporting intervals: . | Seadme mõõdikute intervall – kui tihti seadme mõõdikuid levitada | Keskkonnamõõdikute intervall – kui tihti anduriandmeid levitada | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Aku säilitus | 7200 | 7200 | . ⚠️ Märkus: Lühemad intervallid suurendavad saate kasutusaega ja aku tühjenemist. ", - "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/et-rEE/user/telemetry-and-sensors.html#configuring-telemetry" - },"5643": { - "doc": "Telemeetria & Sensorid", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Meetriline | Unit | Kirjeldus | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Süsinikdioksiidi kontsentratsioon | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. CO₂ näit on värvikoodiga märgitud vastavalt raskusastmele (Hea → Umbne → Halb → Ohtlik → Evakueeruda). Täpsete ppm-vahemike, värvide ja õhukvaliteedi indeksite üksikasjade saamiseks vaata Sõlme mõõdikud — õhukvaliteet. Õhukvaliteedi andmeid saab vaadata infokaartidena sõlme detailvaates, aja jooksul graafikule lisada ja CSV-vormingusse salvestada. ", - "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/et-rEE/user/telemetry-and-sensors.html#air-quality-metrics" - },"5644": { - "doc": "Telemeetria & Sensorid", - "title": "Viewing Telemetry", - "content": ". | Mine Seadmed ja vali seade. | Telemeetria jaotised kuvatakse detailvaates: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Ajaloolised graafikud näitavad aja jooksul trende. | . ", - "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/et-rEE/user/telemetry-and-sensors.html#viewing-telemetry" - },"5645": { - "doc": "Telemeetria & Sensorid", - "title": "Troubleshooting", - "content": ". | Keskkonnaandmeid ei kuvata? Kaugühenduse jaoks on vaja ühendada füüsiline andur (nt BME280 I2C-l). Seadme telemeetria (aku, tööaeg) on ​​alati saadaval, kuid keskkonnamõõdikute jaoks on vaja riistvara. | Vananenud näidud? Kontrolli aruandlusintervalli – väga pikad intervallid (7200+ sekundit) tähendavad harva andmete uuendamist. Samuti veendu, et kaugsõlm on endiselt võrgus. | Sensor conflict on I2C bus? Some sensors share I2C addresses. Kui samal siinil on mitu andurit, kontrolli raadio jadapordi arendajaväljundis aadresside kokkupõrkeid. | . ", - "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/et-rEE/user/telemetry-and-sensors.html#troubleshooting" - },"5646": { - "doc": "Telemeetria & Sensorid", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Seaded — Moodulid ja administreerimine — telemeetriamooduli konfiguratsioon | Ühikud ja lokaat — temperatuuri ja rõhu kuvamise ühikud | . ", - "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/et-rEE/user/telemetry-and-sensors.html#related-topics" - },"5647": { - "doc": "Telemeetria & Sensorid", - "title": "Telemeetria & Sensorid", - "content": " ", - "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html", - - "relUrl": "/et-rEE/user/telemetry-and-sensors.html" - },"5648": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/it-rIT/user/telemetry-and-sensors.html#telemetry--sensors" - },"5649": { - "doc": "Telemetry & Sensors", - "title": "Panoramica", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#panoramica", - - "relUrl": "/it-rIT/user/telemetry-and-sensors.html#panoramica" - },"5650": { - "doc": "Telemetry & Sensors", - "title": "Telemetria dispositivo", - "content": "All Meshtastic nodes report basic device telemetry: . | Metrico | Descrizione | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Tensione | Battery voltage | 3.0–4.2V (LiPo) | . | Utilizzo Canale | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Tempo di attività | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#telemetria-dispositivo", - - "relUrl": "/it-rIT/user/telemetry-and-sensors.html#telemetria-dispositivo" - },"5651": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensore | Temperatura | Umidità | Pressione | Note | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensore | Metrico | Note | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensore | Metrico | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/it-rIT/user/telemetry-and-sensors.html#environment-sensors" - },"5652": { - "doc": "Telemetry & Sensors", - "title": "Metriche Alimentazione", - "content": "Nodes with INA-series power sensors can report: . | Metrico | Descrizione | . | Bus Voltage | Supply rail voltage | . | Attuale | Power consumption (mA) | . | Alimentazione | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#metriche-alimentazione", - - "relUrl": "/it-rIT/user/telemetry-and-sensors.html#metriche-alimentazione" - },"5653": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/it-rIT/user/telemetry-and-sensors.html#configuring-telemetry" - },"5654": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metrico | Unit | Descrizione | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/it-rIT/user/telemetry-and-sensors.html#air-quality-metrics" - },"5655": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/it-rIT/user/telemetry-and-sensors.html#viewing-telemetry" - },"5656": { - "doc": "Telemetry & Sensors", - "title": "Risoluzione problemi", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#risoluzione-problemi", - - "relUrl": "/it-rIT/user/telemetry-and-sensors.html#risoluzione-problemi" - },"5657": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/it-rIT/user/telemetry-and-sensors.html#related-topics" - },"5658": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html", - - "relUrl": "/it-rIT/user/telemetry-and-sensors.html" - },"5659": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#telemetry--sensors" - },"5660": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#overview", - - "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#overview" - },"5661": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | الوصف | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | شدة التيار | Battery voltage | 3.0–4.2V (LiPo) | . | استخدام القناة | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#device-telemetry" - },"5662": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | الحرارة | الرطوبة | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#environment-sensors" - },"5663": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | الوصف | . | Bus Voltage | Supply rail voltage | . | الحالي | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#power-metrics" - },"5664": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#configuring-telemetry" - },"5665": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | الوصف | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#air-quality-metrics" - },"5666": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#viewing-telemetry" - },"5667": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#troubleshooting" - },"5668": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#related-topics" - },"5669": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html", - - "relUrl": "/ar-rSA/user/telemetry-and-sensors.html" - },"5670": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#telemetry--sensors" - },"5671": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#overview", - - "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#overview" - },"5672": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Popis | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Napätie | Battery voltage | 3.0–4.2V (LiPo) | . | Využitie kanálu | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Doba prevádzky | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#device-telemetry" - },"5673": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Senzor | Teplota | Vlhkosť | Tlak | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Senzor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Senzor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#environment-sensors" - },"5674": { - "doc": "Telemetry & Sensors", - "title": "Power Metrics", - "content": "Nodes with INA-series power sensors can report: . | Metric | Popis | . | Bus Voltage | Supply rail voltage | . | Prúd | Power consumption (mA) | . | Napájanie | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#power-metrics", - - "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#power-metrics" - },"5675": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#configuring-telemetry" - },"5676": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Popis | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#air-quality-metrics" - },"5677": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#viewing-telemetry" - },"5678": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#troubleshooting" - },"5679": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#related-topics" - },"5680": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html", - - "relUrl": "/sk-rSK/user/telemetry-and-sensors.html" - },"5681": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#telemetry--sensors" - },"5682": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#overview", - - "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#overview" - },"5683": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Opis | Typical Range | . | Poziom naładowania baterii | Charge percentage | 0–100% | . | Napięcie | Battery voltage | 3.0–4.2V (LiPo) | . | Wykorzystanie kanału | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Czas pracy | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#device-telemetry" - },"5684": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Czujnik | Temperatura | Wilgotność | Ciśnienie | Notatki | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Czujnik | Metric | Notatki | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Czujnik | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#environment-sensors" - },"5685": { - "doc": "Telemetry & Sensors", - "title": "Metryki zasilania", - "content": "Nodes with INA-series power sensors can report: . | Metric | Opis | . | Bus Voltage | Supply rail voltage | . | Natężenie | Power consumption (mA) | . | Zasilanie | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#metryki-zasilania", - - "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#metryki-zasilania" - },"5686": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#configuring-telemetry" - },"5687": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Opis | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#air-quality-metrics" - },"5688": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#viewing-telemetry" - },"5689": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#troubleshooting" - },"5690": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#related-topics" - },"5691": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html", - - "relUrl": "/pl-rPL/user/telemetry-and-sensors.html" - },"5692": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#telemetry--sensors" - },"5693": { - "doc": "Telemetry & Sensors", - "title": "概觀", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#%E6%A6%82%E8%A7%80", - - "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#概觀" - },"5694": { - "doc": "Telemetry & Sensors", - "title": "裝置遙測", - "content": "All Meshtastic nodes report basic device telemetry: . | 公制（公里/公尺） | 描述說明 | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | 電壓 | Battery voltage | 3.0–4.2V (LiPo) | . | 頻道使用量 | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | 運行時間 | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#%E8%A3%9D%E7%BD%AE%E9%81%99%E6%B8%AC", - - "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#裝置遙測" - },"5695": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | 感測器 | 溫度 | 濕度 | 氣壓 | 備註 | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | 感測器 | 公制（公里/公尺） | 備註 | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | 感測器 | 公制（公里/公尺） | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#environment-sensors" - },"5696": { - "doc": "Telemetry & Sensors", - "title": "電源計量資料", - "content": "Nodes with INA-series power sensors can report: . | 公制（公里/公尺） | 描述說明 | . | Bus Voltage | Supply rail voltage | . | 目前 | Power consumption (mA) | . | 電力 | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#%E9%9B%BB%E6%BA%90%E8%A8%88%E9%87%8F%E8%B3%87%E6%96%99", - - "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#電源計量資料" - },"5697": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#configuring-telemetry" - },"5698": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | 公制（公里/公尺） | 單位 | 描述說明 | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#air-quality-metrics" - },"5699": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#viewing-telemetry" - },"5700": { - "doc": "Telemetry & Sensors", - "title": "故障排除", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#%E6%95%85%E9%9A%9C%E6%8E%92%E9%99%A4", - - "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#故障排除" - },"5701": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#related-topics" - },"5702": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html", - - "relUrl": "/zh-rTW/user/telemetry-and-sensors.html" - },"5703": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#telemetry--sensors" - },"5704": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#overview", - - "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#overview" - },"5705": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metrický | Popis | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Napětí | Battery voltage | 3.0–4.2V (LiPo) | . | Využití kanálu | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Doba provozu | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#device-telemetry" - },"5706": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Senzor | Teplota | Vlhkost | Tlak | Poznámka | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Senzor | Metrický | Poznámka | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Senzor | Metrický | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#environment-sensors" - },"5707": { - "doc": "Telemetry & Sensors", - "title": "Metriky napájení", - "content": "Nodes with INA-series power sensors can report: . | Metrický | Popis | . | Bus Voltage | Supply rail voltage | . | Proud | Power consumption (mA) | . | Napájení | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#metriky-nap%C3%A1jen%C3%AD", - - "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#metriky-napájení" - },"5708": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#configuring-telemetry" - },"5709": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metrický | Unit | Popis | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#air-quality-metrics" - },"5710": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#viewing-telemetry" - },"5711": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#troubleshooting" - },"5712": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#related-topics" - },"5713": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html", - - "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html" - },"5714": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#telemetry--sensors", - - "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#telemetry--sensors" - },"5715": { - "doc": "Telemetry & Sensors", - "title": "Overview", - "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#overview", - - "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#overview" - },"5716": { - "doc": "Telemetry & Sensors", - "title": "Device Telemetry", - "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Description | Typical Range | . | Niveau de batterie | Charge percentage | 0–100% | . | Tension | Battery voltage | 3.0–4.2V (LiPo) | . | Utilisation du canal | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Durée de fonctionnement | Seconds since last boot | Varies | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#device-telemetry", - - "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#device-telemetry" - },"5717": { - "doc": "Telemetry & Sensors", - "title": "Environment Sensors", - "content": "Supported environmental sensors: . Temperature & Humidity . | Capteur | Température | Humidité | Pression | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Capteur | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Capteur | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#environment-sensors", - - "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#environment-sensors" - },"5718": { - "doc": "Telemetry & Sensors", - "title": "Métriques d’alimentation", - "content": "Nodes with INA-series power sensors can report: . | Metric | Description | . | Bus Voltage | Supply rail voltage | . | Actif | Power consumption (mA) | . | Alimentation | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#m%C3%A9triques-dalimentation", - - "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#métriques-dalimentation" - },"5719": { - "doc": "Telemetry & Sensors", - "title": "Configuring Telemetry", - "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#configuring-telemetry", - - "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#configuring-telemetry" - },"5720": { - "doc": "Telemetry & Sensors", - "title": "Air Quality Metrics", - "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Description | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#air-quality-metrics", - - "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#air-quality-metrics" - },"5721": { - "doc": "Telemetry & Sensors", - "title": "Viewing Telemetry", - "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#viewing-telemetry", - - "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#viewing-telemetry" - },"5722": { - "doc": "Telemetry & Sensors", - "title": "Troubleshooting", - "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#troubleshooting", - - "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#troubleshooting" - },"5723": { - "doc": "Telemetry & Sensors", - "title": "Related Topics", - "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#related-topics", - - "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#related-topics" - },"5724": { - "doc": "Telemetry & Sensors", - "title": "Telemetry & Sensors", - "content": " ", - "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html", - - "relUrl": "/fr-rFR/user/telemetry-and-sensors.html" - },"5725": { + "relUrl": "/uk-rUA/user/telemetry-and-sensors.html" + },"5365": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", "url": "/Meshtastic-Android/main/zh-rCN/user/telemetry-and-sensors.html#telemetry--sensors", "relUrl": "/zh-rCN/user/telemetry-and-sensors.html#telemetry--sensors" - },"5726": { + },"5366": { "doc": "Telemetry & Sensors", "title": "总览", "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", "url": "/Meshtastic-Android/main/zh-rCN/user/telemetry-and-sensors.html#%E6%80%BB%E8%A7%88", "relUrl": "/zh-rCN/user/telemetry-and-sensors.html#总览" - },"5727": { + },"5367": { "doc": "Telemetry & Sensors", "title": "Device Telemetry", "content": "All Meshtastic nodes report basic device telemetry: . | 公制 | 说明 | Typical Range | . | 电池电量 | Charge percentage | 0–100% | . | 电压 | Battery voltage | 3.0–4.2V (LiPo) | . | 频道利用率 | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | 正常运行时间 | Seconds since last boot | Varies | . ", "url": "/Meshtastic-Android/main/zh-rCN/user/telemetry-and-sensors.html#device-telemetry", "relUrl": "/zh-rCN/user/telemetry-and-sensors.html#device-telemetry" - },"5728": { + },"5368": { "doc": "Telemetry & Sensors", "title": "Environment Sensors", "content": "Supported environmental sensors: . Temperature & Humidity . | 传感器 | 温度 | 湿度 | 气压 | 注 | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | 传感器 | 公制 | 注 | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | 传感器 | 公制 | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", "url": "/Meshtastic-Android/main/zh-rCN/user/telemetry-and-sensors.html#environment-sensors", "relUrl": "/zh-rCN/user/telemetry-and-sensors.html#environment-sensors" - },"5729": { + },"5369": { "doc": "Telemetry & Sensors", "title": "电源计量", "content": "Nodes with INA-series power sensors can report: . | 公制 | 说明 | . | Bus Voltage | Supply rail voltage | . | 电流 | Power consumption (mA) | . | 电源 | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", "url": "/Meshtastic-Android/main/zh-rCN/user/telemetry-and-sensors.html#%E7%94%B5%E6%BA%90%E8%AE%A1%E9%87%8F", "relUrl": "/zh-rCN/user/telemetry-and-sensors.html#电源计量" - },"5730": { + },"5370": { "doc": "Telemetry & Sensors", "title": "Configuring Telemetry", "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", "url": "/Meshtastic-Android/main/zh-rCN/user/telemetry-and-sensors.html#configuring-telemetry", "relUrl": "/zh-rCN/user/telemetry-and-sensors.html#configuring-telemetry" - },"5731": { + },"5371": { "doc": "Telemetry & Sensors", "title": "Air Quality Metrics", "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | 公制 | Unit | 说明 | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", "url": "/Meshtastic-Android/main/zh-rCN/user/telemetry-and-sensors.html#air-quality-metrics", "relUrl": "/zh-rCN/user/telemetry-and-sensors.html#air-quality-metrics" - },"5732": { + },"5372": { "doc": "Telemetry & Sensors", "title": "Viewing Telemetry", "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", "url": "/Meshtastic-Android/main/zh-rCN/user/telemetry-and-sensors.html#viewing-telemetry", "relUrl": "/zh-rCN/user/telemetry-and-sensors.html#viewing-telemetry" - },"5733": { + },"5373": { "doc": "Telemetry & Sensors", "title": "问题排查", "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", "url": "/Meshtastic-Android/main/zh-rCN/user/telemetry-and-sensors.html#%E9%97%AE%E9%A2%98%E6%8E%92%E6%9F%A5", "relUrl": "/zh-rCN/user/telemetry-and-sensors.html#问题排查" - },"5734": { + },"5374": { "doc": "Telemetry & Sensors", "title": "Related Topics", "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", "url": "/Meshtastic-Android/main/zh-rCN/user/telemetry-and-sensors.html#related-topics", "relUrl": "/zh-rCN/user/telemetry-and-sensors.html#related-topics" - },"5735": { + },"5375": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": " ", "url": "/Meshtastic-Android/main/zh-rCN/user/telemetry-and-sensors.html", "relUrl": "/zh-rCN/user/telemetry-and-sensors.html" - },"5736": { + },"5376": { + "doc": "Телеметрия & Сензори", + "title": "Телеметрия & Сензори", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#%D1%82%D0%B5%D0%BB%D0%B5%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D1%8F--%D1%81%D0%B5%D0%BD%D0%B7%D0%BE%D1%80%D0%B8", + + "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#телеметрия--сензори" + },"5377": { + "doc": "Телеметрия & Сензори", + "title": "Преглед", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#%D0%BF%D1%80%D0%B5%D0%B3%D0%BB%D0%B5%D0%B4", + + "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#преглед" + },"5378": { + "doc": "Телеметрия & Сензори", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Метрични | Описание | Типичен диапазон | . | Ниво на батерията | Charge percentage | 0–100% | . | Напрежение | Напрежение на батерията | 3.0–4.2V (LiPo) | . | Използване на канала | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Време на работа | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#device-telemetry" + },"5379": { + "doc": "Телеметрия & Сензори", + "title": "Сензори за околна среда", + "content": "Поддържани сензори за околна среда: . Температура & Влажност . | Сензор | Температура | Влажност | Налягане | Бележки | . | BME280 | ✓ | ✓ | ✓ | Препоръчително многофункционално устройство | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | Висока точност | . | MCP9808 | ✓ | — | — | Прецизна температура | . | LPS22 | — | — | ✓ | Само налягане | . Качество на въздуха . | Сензор | Метрични | Бележки | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Светлина & UV . | Сензор | Метрични | . | OPT3001 | Околна светлина (lux) | . | VEML7700 | Околна светлина (lux) | . | LTR390 | UV индекс | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#%D1%81%D0%B5%D0%BD%D0%B7%D0%BE%D1%80%D0%B8-%D0%B7%D0%B0-%D0%BE%D0%BA%D0%BE%D0%BB%D0%BD%D0%B0-%D1%81%D1%80%D0%B5%D0%B4%D0%B0", + + "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#сензори-за-околна-среда" + },"5380": { + "doc": "Телеметрия & Сензори", + "title": "Показатели на мощност", + "content": "Nodes with INA-series power sensors can report: . | Метрични | Описание | . | Bus Voltage | Supply rail voltage | . | Текущ | Power consumption (mA) | . | Захранване | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.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/telemetry-and-sensors.html#показатели-на-мощност" + },"5381": { + "doc": "Телеметрия & Сензори", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Метеорологична станция | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#configuring-telemetry" + },"5382": { + "doc": "Телеметрия & Сензори", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Метрични | Unit | Описание | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#air-quality-metrics" + },"5383": { + "doc": "Телеметрия & Сензори", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#viewing-telemetry" + },"5384": { + "doc": "Телеметрия & Сензори", + "title": "Отстраняване на неизправности", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.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/telemetry-and-sensors.html#отстраняване-на-неизправности" + },"5385": { + "doc": "Телеметрия & Сензори", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/bg-rBG/user/telemetry-and-sensors.html#related-topics" + },"5386": { + "doc": "Телеметрия & Сензори", + "title": "Телеметрия & Сензори", + "content": " ", + "url": "/Meshtastic-Android/main/bg-rBG/user/telemetry-and-sensors.html", + + "relUrl": "/bg-rBG/user/telemetry-and-sensors.html" + },"5387": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#telemetry--sensors" + },"5388": { + "doc": "Telemetry & Sensors", + "title": "概觀", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#%E6%A6%82%E8%A7%80", + + "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#概觀" + },"5389": { + "doc": "Telemetry & Sensors", + "title": "裝置遙測", + "content": "All Meshtastic nodes report basic device telemetry: . | 公制（公里/公尺） | 描述說明 | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | 電壓 | Battery voltage | 3.0–4.2V (LiPo) | . | 頻道使用量 | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | 運行時間 | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#%E8%A3%9D%E7%BD%AE%E9%81%99%E6%B8%AC", + + "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#裝置遙測" + },"5390": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | 感測器 | 溫度 | 濕度 | 氣壓 | 備註 | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | 感測器 | 公制（公里/公尺） | 備註 | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | 感測器 | 公制（公里/公尺） | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#environment-sensors" + },"5391": { + "doc": "Telemetry & Sensors", + "title": "電源計量資料", + "content": "Nodes with INA-series power sensors can report: . | 公制（公里/公尺） | 描述說明 | . | Bus Voltage | Supply rail voltage | . | 目前 | Power consumption (mA) | . | 電力 | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#%E9%9B%BB%E6%BA%90%E8%A8%88%E9%87%8F%E8%B3%87%E6%96%99", + + "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#電源計量資料" + },"5392": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#configuring-telemetry" + },"5393": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | 公制（公里/公尺） | 單位 | 描述說明 | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#air-quality-metrics" + },"5394": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#viewing-telemetry" + },"5395": { + "doc": "Telemetry & Sensors", + "title": "故障排除", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#%E6%95%85%E9%9A%9C%E6%8E%92%E9%99%A4", + + "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#故障排除" + },"5396": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/zh-rTW/user/telemetry-and-sensors.html#related-topics" + },"5397": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/zh-rTW/user/telemetry-and-sensors.html", + + "relUrl": "/zh-rTW/user/telemetry-and-sensors.html" + },"5398": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#telemetry--sensors" + },"5399": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#overview", + + "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#overview" + },"5400": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Метрика | Опис | Typical Range | . | Ниво батерије | Charge percentage | 0–100% | . | Напон | Battery voltage | 3.0–4.2V (LiPo) | . | Искоришћеност канала | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Време рада | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#device-telemetry" + },"5401": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Сензор | Температура | Влажност | Pressure | Белешке | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Сензор | Метрика | Белешке | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Сензор | Метрика | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#environment-sensors" + },"5402": { + "doc": "Telemetry & Sensors", + "title": "Мерни подаци о снази", + "content": "Nodes with INA-series power sensors can report: . | Метрика | Опис | . | Bus Voltage | Supply rail voltage | . | Струја | Power consumption (mA) | . | Снага | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.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/telemetry-and-sensors.html#мерни-подаци-о-снази" + },"5403": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#configuring-telemetry" + },"5404": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Метрика | Unit | Опис | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#air-quality-metrics" + },"5405": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#viewing-telemetry" + },"5406": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#troubleshooting" + },"5407": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html#related-topics" + },"5408": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/telemetry-and-sensors.html", + + "relUrl": "/sr-rLatn/user/telemetry-and-sensors.html" + },"5409": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#telemetry--sensors" + },"5410": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#overview", + + "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#overview" + },"5411": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metrický | Popis | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Napětí | Battery voltage | 3.0–4.2V (LiPo) | . | Využití kanálu | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Doba provozu | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#device-telemetry" + },"5412": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Senzor | Teplota | Vlhkost | Tlak | Poznámka | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Senzor | Metrický | Poznámka | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Senzor | Metrický | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#environment-sensors" + },"5413": { + "doc": "Telemetry & Sensors", + "title": "Metriky napájení", + "content": "Nodes with INA-series power sensors can report: . | Metrický | Popis | . | Bus Voltage | Supply rail voltage | . | Proud | Power consumption (mA) | . | Napájení | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#metriky-nap%C3%A1jen%C3%AD", + + "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#metriky-napájení" + },"5414": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#configuring-telemetry" + },"5415": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metrický | Unit | Popis | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#air-quality-metrics" + },"5416": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#viewing-telemetry" + },"5417": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#troubleshooting" + },"5418": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html#related-topics" + },"5419": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/telemetry-and-sensors.html", + + "relUrl": "/cs-rCZ/user/telemetry-and-sensors.html" + },"5420": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/en/user/telemetry-and-sensors.html#telemetry--sensors" + },"5421": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#overview", + + "relUrl": "/en/user/telemetry-and-sensors.html#overview" + },"5422": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Description | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/en/user/telemetry-and-sensors.html#device-telemetry" + },"5423": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperature | Humidity | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/en/user/telemetry-and-sensors.html#environment-sensors" + },"5424": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Description | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/en/user/telemetry-and-sensors.html#power-metrics" + },"5425": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/en/user/telemetry-and-sensors.html#configuring-telemetry" + },"5426": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Description | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/en/user/telemetry-and-sensors.html#air-quality-metrics" + },"5427": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/en/user/telemetry-and-sensors.html#viewing-telemetry" + },"5428": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/en/user/telemetry-and-sensors.html#troubleshooting" + },"5429": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/en/user/telemetry-and-sensors.html#related-topics" + },"5430": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/en/user/telemetry-and-sensors.html", + + "relUrl": "/en/user/telemetry-and-sensors.html" + },"5431": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#telemetry--sensors" + },"5432": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#overview", + + "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#overview" + },"5433": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Opis | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Uporaba kanala | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#device-telemetry" + },"5434": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatura | Vlaga | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#environment-sensors" + },"5435": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Opis | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#power-metrics" + },"5436": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#configuring-telemetry" + },"5437": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Opis | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#air-quality-metrics" + },"5438": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#viewing-telemetry" + },"5439": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#troubleshooting" + },"5440": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/sl-rSI/user/telemetry-and-sensors.html#related-topics" + },"5441": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/sl-rSI/user/telemetry-and-sensors.html", + + "relUrl": "/sl-rSI/user/telemetry-and-sensors.html" + },"5442": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/it-rIT/user/telemetry-and-sensors.html#telemetry--sensors" + },"5443": { + "doc": "Telemetry & Sensors", + "title": "Panoramica", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#panoramica", + + "relUrl": "/it-rIT/user/telemetry-and-sensors.html#panoramica" + },"5444": { + "doc": "Telemetry & Sensors", + "title": "Telemetria dispositivo", + "content": "All Meshtastic nodes report basic device telemetry: . | Metrico | Descrizione | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Tensione | Battery voltage | 3.0–4.2V (LiPo) | . | Utilizzo Canale | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Tempo di attività | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#telemetria-dispositivo", + + "relUrl": "/it-rIT/user/telemetry-and-sensors.html#telemetria-dispositivo" + },"5445": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensore | Temperatura | Umidità | Pressione | Note | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensore | Metrico | Note | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensore | Metrico | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/it-rIT/user/telemetry-and-sensors.html#environment-sensors" + },"5446": { + "doc": "Telemetry & Sensors", + "title": "Metriche Alimentazione", + "content": "Nodes with INA-series power sensors can report: . | Metrico | Descrizione | . | Bus Voltage | Supply rail voltage | . | Attuale | Power consumption (mA) | . | Alimentazione | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#metriche-alimentazione", + + "relUrl": "/it-rIT/user/telemetry-and-sensors.html#metriche-alimentazione" + },"5447": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/it-rIT/user/telemetry-and-sensors.html#configuring-telemetry" + },"5448": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metrico | Unit | Descrizione | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/it-rIT/user/telemetry-and-sensors.html#air-quality-metrics" + },"5449": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/it-rIT/user/telemetry-and-sensors.html#viewing-telemetry" + },"5450": { + "doc": "Telemetry & Sensors", + "title": "Risoluzione problemi", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#risoluzione-problemi", + + "relUrl": "/it-rIT/user/telemetry-and-sensors.html#risoluzione-problemi" + },"5451": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/it-rIT/user/telemetry-and-sensors.html#related-topics" + },"5452": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/it-rIT/user/telemetry-and-sensors.html", + + "relUrl": "/it-rIT/user/telemetry-and-sensors.html" + },"5453": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#telemetry--sensors" + },"5454": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#overview", + + "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#overview" + },"5455": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Descrição | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltagem | Battery voltage | 3.0–4.2V (LiPo) | . | Utilização do Canal | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#device-telemetry" + },"5456": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatura | Umidade | Pressão | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#environment-sensors" + },"5457": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Descrição | . | Bus Voltage | Supply rail voltage | . | Atual | Power consumption (mA) | . | Energia | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#power-metrics" + },"5458": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#configuring-telemetry" + },"5459": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Descrição | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#air-quality-metrics" + },"5460": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#viewing-telemetry" + },"5461": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#troubleshooting" + },"5462": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/pt-rBR/user/telemetry-and-sensors.html#related-topics" + },"5463": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/pt-rBR/user/telemetry-and-sensors.html", + + "relUrl": "/pt-rBR/user/telemetry-and-sensors.html" + },"5464": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/is-rIS/user/telemetry-and-sensors.html#telemetry--sensors" + },"5465": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#overview", + + "relUrl": "/is-rIS/user/telemetry-and-sensors.html#overview" + },"5466": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Lýsing | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/is-rIS/user/telemetry-and-sensors.html#device-telemetry" + },"5467": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperature | Humidity | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/is-rIS/user/telemetry-and-sensors.html#environment-sensors" + },"5468": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Lýsing | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/is-rIS/user/telemetry-and-sensors.html#power-metrics" + },"5469": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/is-rIS/user/telemetry-and-sensors.html#configuring-telemetry" + },"5470": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Lýsing | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/is-rIS/user/telemetry-and-sensors.html#air-quality-metrics" + },"5471": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/is-rIS/user/telemetry-and-sensors.html#viewing-telemetry" + },"5472": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/is-rIS/user/telemetry-and-sensors.html#troubleshooting" + },"5473": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/is-rIS/user/telemetry-and-sensors.html#related-topics" + },"5474": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/is-rIS/user/telemetry-and-sensors.html", + + "relUrl": "/is-rIS/user/telemetry-and-sensors.html" + },"5475": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#telemetry--sensors" + },"5476": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#overview", + + "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#overview" + },"5477": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Description | Typical Range | . | Niveau de batterie | Charge percentage | 0–100% | . | Tension | Battery voltage | 3.0–4.2V (LiPo) | . | Utilisation du canal | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Durée de fonctionnement | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#device-telemetry" + },"5478": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Capteur | Température | Humidité | Pression | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Capteur | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Capteur | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#environment-sensors" + },"5479": { + "doc": "Telemetry & Sensors", + "title": "Métriques d’alimentation", + "content": "Nodes with INA-series power sensors can report: . | Metric | Description | . | Bus Voltage | Supply rail voltage | . | Actif | Power consumption (mA) | . | Alimentation | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#m%C3%A9triques-dalimentation", + + "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#métriques-dalimentation" + },"5480": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#configuring-telemetry" + },"5481": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Description | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#air-quality-metrics" + },"5482": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#viewing-telemetry" + },"5483": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#troubleshooting" + },"5484": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/fr-rFR/user/telemetry-and-sensors.html#related-topics" + },"5485": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/fr-rFR/user/telemetry-and-sensors.html", + + "relUrl": "/fr-rFR/user/telemetry-and-sensors.html" + },"5486": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", "url": "/Meshtastic-Android/main/srp/user/telemetry-and-sensors.html#telemetry--sensors", "relUrl": "/srp/user/telemetry-and-sensors.html#telemetry--sensors" - },"5737": { + },"5487": { "doc": "Telemetry & Sensors", "title": "Overview", "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", "url": "/Meshtastic-Android/main/srp/user/telemetry-and-sensors.html#overview", "relUrl": "/srp/user/telemetry-and-sensors.html#overview" - },"5738": { + },"5488": { "doc": "Telemetry & Sensors", "title": "Device Telemetry", "content": "All Meshtastic nodes report basic device telemetry: . | Метрика | Опис | Typical Range | . | Ниво батерије | Charge percentage | 0–100% | . | Напон | Battery voltage | 3.0–4.2V (LiPo) | . | Искоришћеност канала | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Време рада | Seconds since last boot | Varies | . ", "url": "/Meshtastic-Android/main/srp/user/telemetry-and-sensors.html#device-telemetry", "relUrl": "/srp/user/telemetry-and-sensors.html#device-telemetry" - },"5739": { + },"5489": { "doc": "Telemetry & Sensors", "title": "Environment Sensors", "content": "Supported environmental sensors: . Temperature & Humidity . | Сензор | Температура | Влажност | Pressure | Белешке | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Сензор | Метрика | Белешке | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Сензор | Метрика | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", "url": "/Meshtastic-Android/main/srp/user/telemetry-and-sensors.html#environment-sensors", "relUrl": "/srp/user/telemetry-and-sensors.html#environment-sensors" - },"5740": { + },"5490": { "doc": "Telemetry & Sensors", "title": "Мерни подаци о снази", "content": "Nodes with INA-series power sensors can report: . | Метрика | Опис | . | Bus Voltage | Supply rail voltage | . | Струја | Power consumption (mA) | . | Снага | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", "url": "/Meshtastic-Android/main/srp/user/telemetry-and-sensors.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/telemetry-and-sensors.html#мерни-подаци-о-снази" - },"5741": { + },"5491": { "doc": "Telemetry & Sensors", "title": "Configuring Telemetry", "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", "url": "/Meshtastic-Android/main/srp/user/telemetry-and-sensors.html#configuring-telemetry", "relUrl": "/srp/user/telemetry-and-sensors.html#configuring-telemetry" - },"5742": { + },"5492": { "doc": "Telemetry & Sensors", "title": "Air Quality Metrics", "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Метрика | Unit | Опис | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", "url": "/Meshtastic-Android/main/srp/user/telemetry-and-sensors.html#air-quality-metrics", "relUrl": "/srp/user/telemetry-and-sensors.html#air-quality-metrics" - },"5743": { + },"5493": { "doc": "Telemetry & Sensors", "title": "Viewing Telemetry", "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", "url": "/Meshtastic-Android/main/srp/user/telemetry-and-sensors.html#viewing-telemetry", "relUrl": "/srp/user/telemetry-and-sensors.html#viewing-telemetry" - },"5744": { + },"5494": { "doc": "Telemetry & Sensors", "title": "Troubleshooting", "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", "url": "/Meshtastic-Android/main/srp/user/telemetry-and-sensors.html#troubleshooting", "relUrl": "/srp/user/telemetry-and-sensors.html#troubleshooting" - },"5745": { + },"5495": { "doc": "Telemetry & Sensors", "title": "Related Topics", "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", "url": "/Meshtastic-Android/main/srp/user/telemetry-and-sensors.html#related-topics", "relUrl": "/srp/user/telemetry-and-sensors.html#related-topics" - },"5746": { + },"5496": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": " ", "url": "/Meshtastic-Android/main/srp/user/telemetry-and-sensors.html", "relUrl": "/srp/user/telemetry-and-sensors.html" - },"5747": { + },"5497": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#telemetry--sensors" + },"5498": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#overview", + + "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#overview" + },"5499": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Popis | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Napätie | Battery voltage | 3.0–4.2V (LiPo) | . | Využitie kanálu | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Doba prevádzky | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#device-telemetry" + },"5500": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Senzor | Teplota | Vlhkosť | Tlak | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Senzor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Senzor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#environment-sensors" + },"5501": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Popis | . | Bus Voltage | Supply rail voltage | . | Prúd | Power consumption (mA) | . | Napájanie | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#power-metrics" + },"5502": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#configuring-telemetry" + },"5503": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Popis | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#air-quality-metrics" + },"5504": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#viewing-telemetry" + },"5505": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#troubleshooting" + },"5506": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/sk-rSK/user/telemetry-and-sensors.html#related-topics" + },"5507": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/sk-rSK/user/telemetry-and-sensors.html", + + "relUrl": "/sk-rSK/user/telemetry-and-sensors.html" + },"5508": { + "doc": "Telemetria ja anturit", + "title": "Telemetria ja anturit", + "content": "Meshtastic-radiot voivat kerätä ja jakaa anturitietoja koko verkon laajuisesti. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html", + + "relUrl": "/fi-rFI/user/telemetry-and-sensors.html" + },"5509": { + "doc": "Telemetria ja anturit", + "title": "Yleiskatsaus", + "content": "Telemetria mahdollistaa antureilla varustettujen radioiden ympäristö-, virta- ja laitteen kuntotietojen lähettämisen verkkoon. Nämä tiedot näkyvät radion tietonäytössä ja niitä voidaan tallentaa sekä seurata ajan kuluessa. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#yleiskatsaus", + + "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#yleiskatsaus" + },"5510": { + "doc": "Telemetria ja anturit", + "title": "Laitteen telemetriatiedot", + "content": "Kaikki Meshtastic-radiot raportoivat peruslaitetelemetrian: . | Metrijärjestelmä | Kuvaus | Tyypillinen vaihteluväli | . | Akun varaustaso | Varausprosentti | 0–100% | . | Jännite | Akun jännite | 3.0–4.2V (LiPo) | . | Kanavan Käyttö | Paikallisesti käytetyn käyttöasteen prosenttiosuus | 0–100% | . | Lähetysajan käyttöaste (TX) | Tämän radion käyttämän lähetysajan prosenttiosuus | 0–100% | . | Käyttöaika | Sekuntia viimeisestä käynnistyksestä | Vaihtelee | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#laitteen-telemetriatiedot", + + "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#laitteen-telemetriatiedot" + },"5511": { + "doc": "Telemetria ja anturit", + "title": "Ympäristöanturit", + "content": "Tuetut ympäristöanturit: . Lämpötila ja kosteus . | Sensor | Lämpötila | Kosteus | Ilmanpaine | Viestit | . | BME280 | ✓ | ✓ | ✓ | Suositeltu all-in-one-anturi | . | BME680 | ✓ | ✓ | ✓ | Lisää kaasuvastus ja IAQ-mittaukset | . | SHT31 | ✓ | ✓ | — | Korkea tarkkuus | . | MCP9808 | ✓ | — | — | Tarkka lämpötilamittaus | . | LPS22 | — | — | ✓ | Vain ilmanpaine | . Ilmanlaatu . | Sensor | Metrijärjestelmä | Viestit | . | BME680 | Kaasuvastus ja IAQ | Haihtuvat orgaaniset yhdisteet | . | PMSA003I | PM1.0, PM2.5, PM10 | Hiukkaset | . | SEN55 | PM, NOx, VOC, lämpötila, kosteus | Monianturi | . Valo ja UV . | Sensor | Metrijärjestelmä | . | OPT3001 | Ympäristön valoisuus (lux) | . | VEML7700 | Ympäristön valoisuus (lux) | . | LTR390 | UV-indeksi | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#ymp%C3%A4rist%C3%B6anturit", + + "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#ympäristöanturit" + },"5512": { + "doc": "Telemetria ja anturit", + "title": "Virranhallinnan arvot", + "content": "INA-sarjan virta-antureilla varustetut radiot voivat raportoida: . | Metrijärjestelmä | Kuvaus | . | Väyläjännite | Syöttöjännitteen | . | Virta | Virrankulutuksen (mA) | . | Virta | Lasketun tehon (mW) | . Hyödyllinen aurinkolatauksen tai etäradioiden akun kunnon seurantaan. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#virranhallinnan-arvot", + + "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#virranhallinnan-arvot" + },"5513": { + "doc": "Telemetria ja anturit", + "title": "Telemetrian määrittäminen", + "content": ". | Siirry kohtaan Asetukset → Moduuliasetukset → Telemetria | Määritä raportointivälit: . | Laitemittarien väli — kuinka usein laitteen mittarit lähetetään verkkoon | Ympäristömittarien väli — kuinka usein anturitiedot lähetetään verkkoon | . | Ota tarvittavat anturityypit käyttöön. | . Suositellut raportointivälit . | Käyttötarkoitus | Laite (s) | Ympäristö (s) | . | Kaupunkiverkko (paljon radioita) | 3600 | 3600 | . | Maaseutuverkko (vähän radioita) | 900 | 900 | . | Sääasema | 900 | 300 | . | Akun säästäminen | 7200 | 7200 | . ⚠️ Huomautus: Lyhyemmät välit lisäävät käyttöastetta ja akun kulutusta koko verkossa. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#telemetrian-m%C3%A4%C3%A4ritt%C3%A4minen", + + "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#telemetrian-määrittäminen" + },"5514": { + "doc": "Telemetria ja anturit", + "title": "Ilmanlaatumittarit", + "content": "Hiukkas- tai CO₂-antureilla varustetut radiot raportoivat ilmanlaatutietoja: . | Metrijärjestelmä | Yksikkö | Kuvaus | . | PM1.0 | µg/m³ | Erittäin pienet hiukkaset | . | PM2.5 | µg/m³ | Pienhiukkaset | . | PM10 | µg/m³ | Karkeat hiukkaset | . | CO₂ | ppm | Hiilidioksidipitoisuus | . Myös CO₂ anturit, kuten SCD4x, ilmoittavat oman lämpötilansa ja ilmankosteutensa, jotka näytetään edellä olevien mittausten yhteydessä. PM2.5-historiasta sovellus laskee lisäksi EPA NowCast AQI -arvon. CO₂-arvo on värikoodattu vakavuuden mukaan (Hyvä → Tunkkainen → Huono → Epäturvallinen → Evakuoi). Katso Radion mittarit — Ilmanlaatu, josta löytyvät tarkat ppm-arvot, värit ja AQI-luokituksen tiedot. Ilmanlaatutiedot voidaan näyttää tietokortteina radion tietonäytössä, esittää kaavioina ajan kuluessa ja viedä CSV-tiedostoon. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#ilmanlaatumittarit", + + "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#ilmanlaatumittarit" + },"5515": { + "doc": "Telemetria ja anturit", + "title": "Telemetrian tarkastelu", + "content": ". | Siirry kohtaan Radiot ja valitse radio. | Telemetriaosiot näkyvät radion tietonäytössä: . | Laitemittarit (aina käytettävissä) | Ympäristömittarit (jos antureita on saatavilla) | Virtamittarit (jos INA-anturi on käytettävissä) | Ilmanlaatumittarit (jos PM-/CO₂-anturi on käytettävissä) | . | Historiakaaviot näyttävät mittaustietojen kehittymisen ajan kuluessa. | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#telemetrian-tarkastelu", + + "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#telemetrian-tarkastelu" + },"5516": { + "doc": "Telemetria ja anturit", + "title": "Vianetsintä", + "content": ". | Ympäristötiedot eivät näy? Etäradio tarvitsee fyysisen anturin (esim. BME280 I²C-väylässä). Laitetelemetria (akun varaustaso, käyttöaika) on aina käytettävissä, mutta ympäristömittarit edellyttävät laitteistoa. | Vanhentuneita lukemia? Tarkista raportointiväli — erittäin pitkät välit (7200 s tai enemmän) tarkoittavat, että tiedot päivittyvät harvoin. Varmista myös, että etäradio on edelleen verkossa. | Anturiristiriita I²C-väylässä? Jotkin anturit käyttävät samoja I²C-osoitteita. Jos samalla väylällä on useita antureita, tarkista osoiteristiriidat radion sarjaportin virheenkorjaustulosteesta. | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#vianetsint%C3%A4", + + "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#vianetsintä" + },"5517": { + "doc": "Telemetria ja anturit", + "title": "Aiheeseen liittyvät aiheet", + "content": ". | Radion mittarit — tarkastele telemetriatietoja radion tietonäytössä | Asetukset — Moduulit ja ylläpito — telemetriamoduulin määritys | Yksiköt ja aluekohtaiset asetukset — lämpötilan ja ilmanpaineen näyttöyksiköt | . ", + "url": "/Meshtastic-Android/main/fi-rFI/user/telemetry-and-sensors.html#aiheeseen-liittyv%C3%A4t-aiheet", + + "relUrl": "/fi-rFI/user/telemetry-and-sensors.html#aiheeseen-liittyvät-aiheet" + },"5518": { + "doc": "Телеметрия и датчики", + "title": "Телеметрия и датчики", + "content": "Ноды Meshtastic могут собирать и передавать данные датчиков по всей mesh-сети. ", + "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html", + + "relUrl": "/ru-rRU/user/telemetry-and-sensors.html" + },"5519": { + "doc": "Телеметрия и датчики", + "title": "Обзор", + "content": "Телеметрия позволяет нодам, оснащённым датчиками, передавать информацию об окружающей среде, питании и состоянии устройства. Эти данные отображаются на экране сведений о ноде и могут регистрироваться с течением времени. ", + "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html#%D0%BE%D0%B1%D0%B7%D0%BE%D1%80", + + "relUrl": "/ru-rRU/user/telemetry-and-sensors.html#обзор" + },"5520": { + "doc": "Телеметрия и датчики", + "title": "Телеметрия устройства", + "content": "Все ноды Meshtastic передают базовую телеметрию устройства: . | Метрика | Описание | Типичный диапазон | . | Уровень заряда | Процент заряда | 0–100% | . | Напряжение | Напряжение батареи | 3.0–4.2V (LiPo) | . | Использование канала | % использованного локально эфирного времени | 0–100% | . | Использование эфира (TX) | % эфирного времени, использованного этой нодой | 0–100% | . | Аптайм | Секунд с последней загрузки | Варьируется | . ", + "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html#%D1%82%D0%B5%D0%BB%D0%B5%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D1%8F-%D1%83%D1%81%D1%82%D1%80%D0%BE%D0%B9%D1%81%D1%82%D0%B2%D0%B0", + + "relUrl": "/ru-rRU/user/telemetry-and-sensors.html#телеметрия-устройства" + },"5521": { + "doc": "Телеметрия и датчики", + "title": "Датчики окружающей среды", + "content": "Поддерживаемые датчики окружающей среды: . Температура и влажность . | Sensor | Температура | Влажность | Давление | Заметки | . | BME280 | ✓ | ✓ | ✓ | Рекомендуемый “всё в одном” | . | BME680 | ✓ | ✓ | ✓ | Добавляет сопротивление газа/IAQ | . | SHT31 | ✓ | ✓ | — | Высокая точность | . | MCP9808 | ✓ | — | — | Прецизионная температура | . | LPS22 | — | — | ✓ | Только давление | . Качество воздуха . | Sensor | Метрика | Заметки | . | BME680 | Сопротивление газа / IAQ | Летучие органические соединения | . | PMSA003I | PM1.0, PM2.5, PM10 | Взвешенные частицы | . | SEN55 | PM, NOx, VOC, температура, влажность | Мультисенсор | . Освещённость и УФ . | Sensor | Метрика | . | OPT3001 | Окружающая освещённость (люкс) | . | VEML7700 | Окружающая освещённость (люкс) | . | LTR390 | УФ-индекс | . ", + "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html#%D0%B4%D0%B0%D1%82%D1%87%D0%B8%D0%BA%D0%B8-%D0%BE%D0%BA%D1%80%D1%83%D0%B6%D0%B0%D1%8E%D1%89%D0%B5%D0%B9-%D1%81%D1%80%D0%B5%D0%B4%D1%8B", + + "relUrl": "/ru-rRU/user/telemetry-and-sensors.html#датчики-окружающей-среды" + },"5522": { + "doc": "Телеметрия и датчики", + "title": "Метрики питания", + "content": "Ноды с датчиками питания серии INA могут сообщать: . | Метрика | Описание | . | Напряжение шины | Напряжение линии питания | . | Ток | Потребляемый ток (мА) | . | Питание | Расчётная мощность (мВт) | . Полезно для мониторинга солнечной зарядки или состояния батареи на удалённых нодах. ", + "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.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/telemetry-and-sensors.html#метрики-питания" + },"5523": { + "doc": "Телеметрия и датчики", + "title": "Настройка телеметрии", + "content": ". | Перейдите в Настройки → Конфигурация модулей → Телеметрия. | Установите интервалы передачи: . | Интервал метрик устройства — как часто передавать метрики устройства | Интервал метрик окружающей среды — как часто передавать данные датчиков | . | Включайте нужные типы датчиков по необходимости. | . Рекомендуемые интервалы . | Сценарий использования | Устройство (сек.) | Окружающая среда (сек.) | . | Городская mesh-сеть (много нод) | 3600 | 3600 | . | Сельская mesh-сеть (мало нод) | 900 | 900 | . | Метеостанция | 900 | 300 | . | Экономия заряда батареи | 7200 | 7200 | . ⚠️ Примечание: Более короткие интервалы увеличивают использование эфирного времени и расход батареи во всей mesh-сети. ", + "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html#%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B0-%D1%82%D0%B5%D0%BB%D0%B5%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%B8", + + "relUrl": "/ru-rRU/user/telemetry-and-sensors.html#настройка-телеметрии" + },"5524": { + "doc": "Телеметрия и датчики", + "title": "Метрики качества воздуха", + "content": "Ноды с датчиками взвешенных частиц или CO₂ передают данные о качестве воздуха: . | Метрическая | Единица | Описание | . | PM1.0 | мкг/м³ | Ультрамелкие взвешенные частицы | . | PM2.5 | мкг/м³ | Мелкие взвешенные частицы | . | PM10 | мкг/м³ | Крупные взвешенные частицы | . | CO₂ | ppm | Концентрация углекислого газа | . Датчики CO₂, такие как SCD4x, также сообщают собственную температуру и влажность, которые отображаются вместе с указанными выше показаниями. На основе истории PM2.5 приложение дополнительно вычисляет значение AQI EPA по методу NowCast. Показания CO₂ окрашены по уровню опасности (Хорошо → Душно → Плохо → Опасно → Эвакуация). Точные диапазоны ppm, цвета и подробности AQI см. в разделе Метрики нод — Качество воздуха. Данные о качестве воздуха можно просматривать в виде информационных карточек на экране сведений о ноде, строить графики за период и экспортировать в CSV. ", + "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.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/telemetry-and-sensors.html#метрики-качества-воздуха" + },"5525": { + "doc": "Телеметрия и датчики", + "title": "Просмотр телеметрии", + "content": ". | Перейдите в Ноды и выберите ноду. | Разделы телеметрии отображаются на экране сведений: . | Метрики устройства (доступны всегда) | Метрики окружающей среды (при наличии датчиков) | Метрики питания (при наличии датчика INA) | Метрики качества воздуха (при наличии датчика PM/CO₂) | . | Исторические графики показывают тенденции с течением времени. | . ", + "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.html#%D0%BF%D1%80%D0%BE%D1%81%D0%BC%D0%BE%D1%82%D1%80-%D1%82%D0%B5%D0%BB%D0%B5%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%B8", + + "relUrl": "/ru-rRU/user/telemetry-and-sensors.html#просмотр-телеметрии" + },"5526": { + "doc": "Телеметрия и датчики", + "title": "Устранение неполадок", + "content": ". | Нет данных об окружающей среде? К удалённой ноде должен быть физически подключён датчик (например, BME280 по I2C). Телеметрия устройства (заряд батареи, время работы) доступна всегда, но для метрик окружающей среды требуется оборудование. | Показания устарели? Проверьте интервал передачи — очень большие интервалы (7200 с и более) означают, что данные обновляются редко. Также убедитесь, что удалённая нода всё ещё в сети. | Конфликт датчиков на шине I2C? Некоторые датчики используют одинаковые адреса I2C. Если на одной шине несколько твоих датчиков, проверь последовательный отладочный вывод радио на предмет конфликтов адресов. | . ", + "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.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/telemetry-and-sensors.html#устранение-неполадок" + },"5527": { + "doc": "Телеметрия и датчики", + "title": "Связанные темы", + "content": ". | Метрики нод — просмотр данных телеметрии на экране сведений о ноде | Настройки — Модули и администрирование — конфигурация модуля телеметрии | Единицы измерения и регион — единицы отображения температуры и давления | . ", + "url": "/Meshtastic-Android/main/ru-rRU/user/telemetry-and-sensors.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/telemetry-and-sensors.html#связанные-темы" + },"5528": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#telemetry--sensors" + },"5529": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#overview", + + "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#overview" + },"5530": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | 설명 | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | 전압 | Battery voltage | 3.0–4.2V (LiPo) | . | 채널 사용 | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | 업타임 | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#device-telemetry" + },"5531": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | 온도 | 습도 | 기압 | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#environment-sensors" + },"5532": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | 설명 | . | Bus Voltage | Supply rail voltage | . | 전류 | Power consumption (mA) | . | 전원 | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#power-metrics" + },"5533": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#configuring-telemetry" + },"5534": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | 설명 | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#air-quality-metrics" + },"5535": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#viewing-telemetry" + },"5536": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#troubleshooting" + },"5537": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/ko-rKR/user/telemetry-and-sensors.html#related-topics" + },"5538": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/ko-rKR/user/telemetry-and-sensors.html", + + "relUrl": "/ko-rKR/user/telemetry-and-sensors.html" + },"5539": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#telemetry--sensors" + },"5540": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#overview", + + "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#overview" + },"5541": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Opis | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#device-telemetry" + },"5542": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperature | Humidity | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#environment-sensors" + },"5543": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Opis | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#power-metrics" + },"5544": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#configuring-telemetry" + },"5545": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Opis | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#air-quality-metrics" + },"5546": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#viewing-telemetry" + },"5547": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#troubleshooting" + },"5548": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/hr-rHR/user/telemetry-and-sensors.html#related-topics" + },"5549": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/hr-rHR/user/telemetry-and-sensors.html", + + "relUrl": "/hr-rHR/user/telemetry-and-sensors.html" + },"5550": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", "url": "/Meshtastic-Android/main/sq-rAL/user/telemetry-and-sensors.html#telemetry--sensors", "relUrl": "/sq-rAL/user/telemetry-and-sensors.html#telemetry--sensors" - },"5748": { + },"5551": { "doc": "Telemetry & Sensors", "title": "Overview", "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", "url": "/Meshtastic-Android/main/sq-rAL/user/telemetry-and-sensors.html#overview", "relUrl": "/sq-rAL/user/telemetry-and-sensors.html#overview" - },"5749": { + },"5552": { "doc": "Telemetry & Sensors", "title": "Device Telemetry", "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Përshkrimi | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Përdorimi i kanalit | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", "url": "/Meshtastic-Android/main/sq-rAL/user/telemetry-and-sensors.html#device-telemetry", "relUrl": "/sq-rAL/user/telemetry-and-sensors.html#device-telemetry" - },"5750": { + },"5553": { "doc": "Telemetry & Sensors", "title": "Environment Sensors", "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatura | Lagështia | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", "url": "/Meshtastic-Android/main/sq-rAL/user/telemetry-and-sensors.html#environment-sensors", "relUrl": "/sq-rAL/user/telemetry-and-sensors.html#environment-sensors" - },"5751": { + },"5554": { "doc": "Telemetry & Sensors", "title": "Power Metrics", "content": "Nodes with INA-series power sensors can report: . | Metric | Përshkrimi | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", "url": "/Meshtastic-Android/main/sq-rAL/user/telemetry-and-sensors.html#power-metrics", "relUrl": "/sq-rAL/user/telemetry-and-sensors.html#power-metrics" - },"5752": { + },"5555": { "doc": "Telemetry & Sensors", "title": "Configuring Telemetry", "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", "url": "/Meshtastic-Android/main/sq-rAL/user/telemetry-and-sensors.html#configuring-telemetry", "relUrl": "/sq-rAL/user/telemetry-and-sensors.html#configuring-telemetry" - },"5753": { + },"5556": { "doc": "Telemetry & Sensors", "title": "Air Quality Metrics", "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Përshkrimi | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", "url": "/Meshtastic-Android/main/sq-rAL/user/telemetry-and-sensors.html#air-quality-metrics", "relUrl": "/sq-rAL/user/telemetry-and-sensors.html#air-quality-metrics" - },"5754": { + },"5557": { "doc": "Telemetry & Sensors", "title": "Viewing Telemetry", "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", "url": "/Meshtastic-Android/main/sq-rAL/user/telemetry-and-sensors.html#viewing-telemetry", "relUrl": "/sq-rAL/user/telemetry-and-sensors.html#viewing-telemetry" - },"5755": { + },"5558": { "doc": "Telemetry & Sensors", "title": "Troubleshooting", "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", "url": "/Meshtastic-Android/main/sq-rAL/user/telemetry-and-sensors.html#troubleshooting", "relUrl": "/sq-rAL/user/telemetry-and-sensors.html#troubleshooting" - },"5756": { + },"5559": { "doc": "Telemetry & Sensors", "title": "Related Topics", "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", "url": "/Meshtastic-Android/main/sq-rAL/user/telemetry-and-sensors.html#related-topics", "relUrl": "/sq-rAL/user/telemetry-and-sensors.html#related-topics" - },"5757": { + },"5560": { "doc": "Telemetry & Sensors", "title": "Telemetry & Sensors", "content": " ", "url": "/Meshtastic-Android/main/sq-rAL/user/telemetry-and-sensors.html", "relUrl": "/sq-rAL/user/telemetry-and-sensors.html" + },"5561": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/no-rNO/user/telemetry-and-sensors.html#telemetry--sensors" + },"5562": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#overview", + + "relUrl": "/no-rNO/user/telemetry-and-sensors.html#overview" + },"5563": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Beskrivelse | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Kanalutnyttelse | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/no-rNO/user/telemetry-and-sensors.html#device-telemetry" + },"5564": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatur | Luftfuktighet | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/no-rNO/user/telemetry-and-sensors.html#environment-sensors" + },"5565": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Beskrivelse | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/no-rNO/user/telemetry-and-sensors.html#power-metrics" + },"5566": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/no-rNO/user/telemetry-and-sensors.html#configuring-telemetry" + },"5567": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Beskrivelse | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/no-rNO/user/telemetry-and-sensors.html#air-quality-metrics" + },"5568": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/no-rNO/user/telemetry-and-sensors.html#viewing-telemetry" + },"5569": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/no-rNO/user/telemetry-and-sensors.html#troubleshooting" + },"5570": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/no-rNO/user/telemetry-and-sensors.html#related-topics" + },"5571": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/no-rNO/user/telemetry-and-sensors.html", + + "relUrl": "/no-rNO/user/telemetry-and-sensors.html" + },"5572": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#telemetry--sensors" + },"5573": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#overview", + + "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#overview" + },"5574": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Aprašymas | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Kanalo panaudojimas | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#device-telemetry" + },"5575": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatūra | Drėgmė | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#environment-sensors" + },"5576": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Aprašymas | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#power-metrics" + },"5577": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#configuring-telemetry" + },"5578": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Aprašymas | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#air-quality-metrics" + },"5579": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#viewing-telemetry" + },"5580": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#troubleshooting" + },"5581": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/lt-rLT/user/telemetry-and-sensors.html#related-topics" + },"5582": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/lt-rLT/user/telemetry-and-sensors.html", + + "relUrl": "/lt-rLT/user/telemetry-and-sensors.html" + },"5583": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#telemetry--sensors" + },"5584": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#overview", + + "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#overview" + },"5585": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | الوصف | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | شدة التيار | Battery voltage | 3.0–4.2V (LiPo) | . | استخدام القناة | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#device-telemetry" + },"5586": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | الحرارة | الرطوبة | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#environment-sensors" + },"5587": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | الوصف | . | Bus Voltage | Supply rail voltage | . | الحالي | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#power-metrics" + },"5588": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#configuring-telemetry" + },"5589": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | الوصف | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#air-quality-metrics" + },"5590": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#viewing-telemetry" + },"5591": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#troubleshooting" + },"5592": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/ar-rSA/user/telemetry-and-sensors.html#related-topics" + },"5593": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/ar-rSA/user/telemetry-and-sensors.html", + + "relUrl": "/ar-rSA/user/telemetry-and-sensors.html" + },"5594": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#telemetry--sensors" + },"5595": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#overview", + + "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#overview" + },"5596": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Descrição | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltagem | Battery voltage | 3.0–4.2V (LiPo) | . | Utilização do canal | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Tempo ativo | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#device-telemetry" + },"5597": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatura | Humidade | Pressão | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#environment-sensors" + },"5598": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Descrição | . | Bus Voltage | Supply rail voltage | . | Atual | Power consumption (mA) | . | Energia | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#power-metrics" + },"5599": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#configuring-telemetry" + },"5600": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Descrição | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#air-quality-metrics" + },"5601": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#viewing-telemetry" + },"5602": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#troubleshooting" + },"5603": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/pt-rPT/user/telemetry-and-sensors.html#related-topics" + },"5604": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/pt-rPT/user/telemetry-and-sensors.html", + + "relUrl": "/pt-rPT/user/telemetry-and-sensors.html" + },"5605": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#telemetry--sensors" + },"5606": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#overview", + + "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#overview" + },"5607": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | תיאור | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#device-telemetry" + },"5608": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperature | Humidity | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#environment-sensors" + },"5609": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | תיאור | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#power-metrics" + },"5610": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#configuring-telemetry" + },"5611": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | תיאור | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#air-quality-metrics" + },"5612": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#viewing-telemetry" + },"5613": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#troubleshooting" + },"5614": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/iw-rIL/user/telemetry-and-sensors.html#related-topics" + },"5615": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/iw-rIL/user/telemetry-and-sensors.html", + + "relUrl": "/iw-rIL/user/telemetry-and-sensors.html" + },"5616": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/el-rGR/user/telemetry-and-sensors.html#telemetry--sensors" + },"5617": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#overview", + + "relUrl": "/el-rGR/user/telemetry-and-sensors.html#overview" + },"5618": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Περιγραφή | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Τάση | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/el-rGR/user/telemetry-and-sensors.html#device-telemetry" + },"5619": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Θερμοκρασία | Υγρασία | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/el-rGR/user/telemetry-and-sensors.html#environment-sensors" + },"5620": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Περιγραφή | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/el-rGR/user/telemetry-and-sensors.html#power-metrics" + },"5621": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/el-rGR/user/telemetry-and-sensors.html#configuring-telemetry" + },"5622": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Περιγραφή | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/el-rGR/user/telemetry-and-sensors.html#air-quality-metrics" + },"5623": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/el-rGR/user/telemetry-and-sensors.html#viewing-telemetry" + },"5624": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/el-rGR/user/telemetry-and-sensors.html#troubleshooting" + },"5625": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/el-rGR/user/telemetry-and-sensors.html#related-topics" + },"5626": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/el-rGR/user/telemetry-and-sensors.html", + + "relUrl": "/el-rGR/user/telemetry-and-sensors.html" + },"5627": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#telemetry--sensors" + },"5628": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#overview", + + "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#overview" + },"5629": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Descriere | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Tensiune | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Timp de functionare | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#device-telemetry" + },"5630": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Senzor | Temperature | Humidity | Presiune | Notițe | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Senzor | Metric | Notițe | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Senzor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#environment-sensors" + },"5631": { + "doc": "Telemetry & Sensors", + "title": "Valori putere", + "content": "Nodes with INA-series power sensors can report: . | Metric | Descriere | . | Bus Voltage | Supply rail voltage | . | Actual | Power consumption (mA) | . | Alimentare | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#valori-putere", + + "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#valori-putere" + },"5632": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#configuring-telemetry" + },"5633": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Descriere | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#air-quality-metrics" + },"5634": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#viewing-telemetry" + },"5635": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#troubleshooting" + },"5636": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/ro-rRO/user/telemetry-and-sensors.html#related-topics" + },"5637": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/ro-rRO/user/telemetry-and-sensors.html", + + "relUrl": "/ro-rRO/user/telemetry-and-sensors.html" + },"5638": { + "doc": "Telemeetria & Sensorid", + "title": "Telemetria & sensorid", + "content": "Meshtastic sõlmed saavad koguda ja jagada andurite andmeid kärgvõrgu kaudu. ", + "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#telemetria--sensorid", + + "relUrl": "/et-rEE/user/telemetry-and-sensors.html#telemetria--sensorid" + },"5639": { + "doc": "Telemeetria & Sensorid", + "title": "Ülevaade", + "content": "Telemeetria võimaldab anduritega varustatud sõlmedel levitada keskkonna-, energiatarbimise ja seadme terviseteavet. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#%C3%BClevaade", + + "relUrl": "/et-rEE/user/telemetry-and-sensors.html#ülevaade" + },"5640": { + "doc": "Telemeetria & Sensorid", + "title": "Device Telemetry", + "content": "Kõik Meshtastic sõlmed edastavad seadme põhitelemeetriat: . | Meetriline | Kirjeldus | Tüüpiline ulatus | . | Aku tase | Charge percentage | 0–100% | . | Vool | Aku pinge | 3,0–4,2V (LiPo) | . | Kanali kasutus | Kohalikult kasutatud eetriaja % | 0–100% | . | Eetri kasutus TX | Selle sõlme poolt kasutatud eetriaja % | 0–100% | . | Töötamise aeg | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/et-rEE/user/telemetry-and-sensors.html#device-telemetry" + },"5641": { + "doc": "Telemeetria & Sensorid", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Andur | Temperatuur | Niiskus | Õhurõhk | Sõnumid | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Andur | Meetriline | Sõnumid | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1,0, PM2,5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Valgus & UV . | Andur | Meetriline | . | OPT3001 | Ambient valgus (lux) | . | VEML7700 | Ambient valgus (lux) | . | LTR390 | UV indeks | . ", + "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/et-rEE/user/telemetry-and-sensors.html#environment-sensors" + },"5642": { + "doc": "Telemeetria & Sensorid", + "title": "Võimsusnäitajad", + "content": "Nodes with INA-series power sensors can report: . | Meetriline | Kirjeldus | . | Bus Voltage | Supply rail voltage | . | Pinge | Power consumption (mA) | . | Toide | Calculated power (mW) | . Kasulik päikesepaneelide laadimise või aku seisundi jälgimiseks kaugsõlmedes. ", + "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#v%C3%B5imsusn%C3%A4itajad", + + "relUrl": "/et-rEE/user/telemetry-and-sensors.html#võimsusnäitajad" + },"5643": { + "doc": "Telemeetria & Sensorid", + "title": "Configuring Telemetry", + "content": ". | Mine menüüsse Seaded → Mooduli konfiguratsioon → Telemeetria. | Set reporting intervals: . | Seadme mõõdikute intervall – kui tihti seadme mõõdikuid levitada | Keskkonnamõõdikute intervall – kui tihti anduriandmeid levitada | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Aku säilitus | 7200 | 7200 | . ⚠️ Märkus: Lühemad intervallid suurendavad saate kasutusaega ja aku tühjenemist. ", + "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/et-rEE/user/telemetry-and-sensors.html#configuring-telemetry" + },"5644": { + "doc": "Telemeetria & Sensorid", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Meetriline | Unit | Kirjeldus | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Süsinikdioksiidi kontsentratsioon | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. CO₂ näit on värvikoodiga märgitud vastavalt raskusastmele (Hea → Umbne → Halb → Ohtlik → Evakueeruda). Täpsete ppm-vahemike, värvide ja õhukvaliteedi indeksite üksikasjade saamiseks vaata Sõlme mõõdikud — õhukvaliteet. Õhukvaliteedi andmeid saab vaadata infokaartidena sõlme detailvaates, aja jooksul graafikule lisada ja CSV-vormingusse salvestada. ", + "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/et-rEE/user/telemetry-and-sensors.html#air-quality-metrics" + },"5645": { + "doc": "Telemeetria & Sensorid", + "title": "Viewing Telemetry", + "content": ". | Mine Seadmed ja vali seade. | Telemeetria jaotised kuvatakse detailvaates: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Ajaloolised graafikud näitavad aja jooksul trende. | . ", + "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/et-rEE/user/telemetry-and-sensors.html#viewing-telemetry" + },"5646": { + "doc": "Telemeetria & Sensorid", + "title": "Troubleshooting", + "content": ". | Keskkonnaandmeid ei kuvata? Kaugühenduse jaoks on vaja ühendada füüsiline andur (nt BME280 I2C-l). Seadme telemeetria (aku, tööaeg) on ​​alati saadaval, kuid keskkonnamõõdikute jaoks on vaja riistvara. | Vananenud näidud? Kontrolli aruandlusintervalli – väga pikad intervallid (7200+ sekundit) tähendavad harva andmete uuendamist. Samuti veendu, et kaugsõlm on endiselt võrgus. | Sensor conflict on I2C bus? Some sensors share I2C addresses. Kui samal siinil on mitu andurit, kontrolli raadio jadapordi arendajaväljundis aadresside kokkupõrkeid. | . ", + "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/et-rEE/user/telemetry-and-sensors.html#troubleshooting" + },"5647": { + "doc": "Telemeetria & Sensorid", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Seaded — Moodulid ja administreerimine — telemeetriamooduli konfiguratsioon | Ühikud ja lokaat — temperatuuri ja rõhu kuvamise ühikud | . ", + "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/et-rEE/user/telemetry-and-sensors.html#related-topics" + },"5648": { + "doc": "Telemeetria & Sensorid", + "title": "Telemeetria & Sensorid", + "content": " ", + "url": "/Meshtastic-Android/main/et-rEE/user/telemetry-and-sensors.html", + + "relUrl": "/et-rEE/user/telemetry-and-sensors.html" + },"5649": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#telemetry--sensors" + },"5650": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#overview", + + "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#overview" + },"5651": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Cur síos | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Úsáid cainéil | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#device-telemetry" + },"5652": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Teocht | Laige | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#environment-sensors" + },"5653": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Cur síos | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#power-metrics" + },"5654": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#configuring-telemetry" + },"5655": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Cur síos | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#air-quality-metrics" + },"5656": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#viewing-telemetry" + },"5657": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#troubleshooting" + },"5658": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/ga-rIE/user/telemetry-and-sensors.html#related-topics" + },"5659": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/ga-rIE/user/telemetry-and-sensors.html", + + "relUrl": "/ga-rIE/user/telemetry-and-sensors.html" + },"5660": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#telemetry--sensors" + },"5661": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#overview", + + "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#overview" + },"5662": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Opis | Typical Range | . | Poziom naładowania baterii | Charge percentage | 0–100% | . | Napięcie | Battery voltage | 3.0–4.2V (LiPo) | . | Wykorzystanie kanału | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Czas pracy | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#device-telemetry" + },"5663": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Czujnik | Temperatura | Wilgotność | Ciśnienie | Notatki | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Czujnik | Metric | Notatki | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Czujnik | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#environment-sensors" + },"5664": { + "doc": "Telemetry & Sensors", + "title": "Metryki zasilania", + "content": "Nodes with INA-series power sensors can report: . | Metric | Opis | . | Bus Voltage | Supply rail voltage | . | Natężenie | Power consumption (mA) | . | Zasilanie | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#metryki-zasilania", + + "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#metryki-zasilania" + },"5665": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#configuring-telemetry" + },"5666": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Opis | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#air-quality-metrics" + },"5667": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#viewing-telemetry" + },"5668": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#troubleshooting" + },"5669": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/pl-rPL/user/telemetry-and-sensors.html#related-topics" + },"5670": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/pl-rPL/user/telemetry-and-sensors.html", + + "relUrl": "/pl-rPL/user/telemetry-and-sensors.html" + },"5671": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#telemetry--sensors" + },"5672": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#overview", + + "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#overview" + },"5673": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Beschrijving | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Spanning | Battery voltage | 3.0–4.2V (LiPo) | . | Kanaalgebruik | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Tijd online | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#device-telemetry" + },"5674": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatuur | Vochtigheid | Druk | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#environment-sensors" + },"5675": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Beschrijving | . | Bus Voltage | Supply rail voltage | . | Huidige | Power consumption (mA) | . | Vermogen | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#power-metrics" + },"5676": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#configuring-telemetry" + },"5677": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Beschrijving | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#air-quality-metrics" + },"5678": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#viewing-telemetry" + },"5679": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#troubleshooting" + },"5680": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/nl-rNL/user/telemetry-and-sensors.html#related-topics" + },"5681": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/nl-rNL/user/telemetry-and-sensors.html", + + "relUrl": "/nl-rNL/user/telemetry-and-sensors.html" + },"5682": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#telemetry--sensors" + },"5683": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#overview", + + "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#overview" + },"5684": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Beskrivning | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Spänning | Battery voltage | 3.0–4.2V (LiPo) | . | Kanalutnyttjande | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Upptid | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#device-telemetry" + },"5685": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatur | Luftfuktighet | Tryck | Anteckningar | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Anteckningar | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#environment-sensors" + },"5686": { + "doc": "Telemetry & Sensors", + "title": "Strömdata", + "content": "Nodes with INA-series power sensors can report: . | Metric | Beskrivning | . | Bus Voltage | Supply rail voltage | . | Ström | Power consumption (mA) | . | Ström | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#str%C3%B6mdata", + + "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#strömdata" + },"5687": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#configuring-telemetry" + },"5688": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Beskrivning | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#air-quality-metrics" + },"5689": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#viewing-telemetry" + },"5690": { + "doc": "Telemetry & Sensors", + "title": "Felsökning", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#fels%C3%B6kning", + + "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#felsökning" + },"5691": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/sv-rSE/user/telemetry-and-sensors.html#related-topics" + },"5692": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/sv-rSE/user/telemetry-and-sensors.html", + + "relUrl": "/sv-rSE/user/telemetry-and-sensors.html" + },"5693": { + "doc": "テレメトリとセンサー", + "title": "テレメトリとセンサー", + "content": "Meshtastic のノードは、メッシュネットワーク全体でセンサーデータを収集・共有できます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html", + + "relUrl": "/ja-rJP/user/telemetry-and-sensors.html" + },"5694": { + "doc": "テレメトリとセンサー", + "title": "概要", + "content": "テレメトリを使うと、センサーを搭載したノードが、環境・電力・デバイスの状態の情報をブロードキャストできます。 このデータはノードの詳細画面で確認でき、時系列で記録することもできます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E6%A6%82%E8%A6%81", + + "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#概要" + },"5695": { + "doc": "テレメトリとセンサー", + "title": "デバイステレメトリ", + "content": "すべての Meshtastic ノードは、基本的なデバイステレメトリを報告します： . | メトリクス | 説明 | 標準的な範囲 | . | バッテリー残量 | 充電の割合 | 0–100% | . | 電圧 | バッテリー電圧 | 3.0–4.2V (LiPo) | . | チャンネル全体の利用率 | ローカルで使用された電波利用時間の割合 | 0–100% | . | 送信の電波利用率 | このノードが使用した電波利用時間の割合 | 0–100% | . | 連続稼働時間 | 前回の起動からの経過秒数 | 可変 | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E3%83%87%E3%83%90%E3%82%A4%E3%82%B9%E3%83%86%E3%83%AC%E3%83%A1%E3%83%88%E3%83%AA", + + "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#デバイステレメトリ" + },"5696": { + "doc": "テレメトリとセンサー", + "title": "環境センサー", + "content": "対応する環境センサー： . 温度と湿度 . | センサー | 温度 | 湿度 | 気圧 | 備考 | . | BME280 | ✓ | ✓ | ✓ | おすすめのオールインワン | . | BME680 | ✓ | ✓ | ✓ | ガス抵抗／IAQ を追加 | . | SHT31 | ✓ | ✓ | — | 高精度 | . | MCP9808 | ✓ | — | — | 高精度な温度 | . | LPS22 | — | — | ✓ | 気圧のみ | . 大気質 . | センサー | メトリクス | 備考 | . | BME680 | ガス抵抗／IAQ | 揮発性有機化合物 | . | PMSA003I | PM1.0, PM2.5, PM10 | 粒子状物質 | . | SEN55 | PM、NOx、VOC、温度、湿度 | マルチセンサー | . 光と UV . | センサー | メトリクス | . | OPT3001 | 周囲の明るさ（ルクス） | . | VEML7700 | 周囲の明るさ（ルクス） | . | LTR390 | UV 指数 | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E7%92%B0%E5%A2%83%E3%82%BB%E3%83%B3%E3%82%B5%E3%83%BC", + + "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#環境センサー" + },"5697": { + "doc": "テレメトリとセンサー", + "title": "電力メトリクス", + "content": "INA シリーズの電力センサーを搭載したノードは、次を報告できます： . | メトリクス | 説明 | . | バス電圧 | 供給レールの電圧 | . | 電流 | 消費電流（mA） | . | 電力 | 計算された電力（mW） | . リモートノードの太陽光充電やバッテリーの状態を監視するのに便利です。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.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/telemetry-and-sensors.html#電力メトリクス" + },"5698": { + "doc": "テレメトリとセンサー", + "title": "テレメトリを設定する", + "content": ". | 「設定 → モジュール設定 → テレメトリ」に移動します。 | 報告間隔を設定します： . | デバイスメトリクスの間隔：デバイスメトリクスをブロードキャストする頻度 | 環境メトリクスの間隔：センサーデータをブロードキャストする頻度 | . | 必要に応じて、特定のセンサーの種類を有効にします。 | . 推奨の間隔 . | 用途 | デバイス（秒） | 環境（秒） | . | 都市部のメッシュ（多数のノード） | 3600 | 3600 | . | 地方のメッシュ（少数のノード） | 900 | 900 | . | 気象観測所 | 900 | 300 | . | バッテリー節約 | 7200 | 7200 | . ⚠️ 注意： 間隔を短くすると、メッシュ全体で電波利用時間の消費とバッテリーの消耗が増えます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E3%83%86%E3%83%AC%E3%83%A1%E3%83%88%E3%83%AA%E3%82%92%E8%A8%AD%E5%AE%9A%E3%81%99%E3%82%8B", + + "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#テレメトリを設定する" + },"5699": { + "doc": "テレメトリとセンサー", + "title": "大気質メトリクス", + "content": "粒子状物質センサーまたは CO₂ センサーを搭載したノードは、大気質データを報告します： . | メトリクス | 単位 | 説明 | . | PM1.0 | µg/m³ | 超微小粒子状物質 | . | PM2.5 | µg/m³ | 微小粒子状物質 | . | PM10 | µg/m³ | 粗大粒子状物質 | . | CO₂ | ppm | 二酸化炭素の濃度 | . SCD4x などの CO₂ センサーは、自身の温度と湿度も報告し、上記の測定値とともに表示されます。 アプリは、PM2.5 の履歴から EPA NowCast AQI の値も算出します。 . CO₂ の測定値は、深刻度に応じて色分けされます（良好 → 空気がこもる → 悪い → 危険 → 退避）。 正確な ppm の区分、色、AQI の詳細については、ノードメトリクス：大気質 を参照してください。 . 大気質データは、ノードの詳細画面で情報カードとして表示したり、時系列でグラフ化したり、CSV にエクスポートしたりできます。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.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/telemetry-and-sensors.html#大気質メトリクス" + },"5700": { + "doc": "テレメトリとセンサー", + "title": "テレメトリを表示する", + "content": ". | 「ノード」に移動して、ノードを選択します。 | 詳細画面にテレメトリのセクションが表示されます： . | デバイスメトリクス（常に利用可能） | 環境メトリクス（センサーがある場合） | 電力メトリクス（INA センサーがある場合） | 大気質メトリクス（PM／CO₂ センサーがある場合） | . | 履歴グラフで、時系列の傾向を確認できます。 | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E3%83%86%E3%83%AC%E3%83%A1%E3%83%88%E3%83%AA%E3%82%92%E8%A1%A8%E7%A4%BA%E3%81%99%E3%82%8B", + + "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#テレメトリを表示する" + },"5701": { + "doc": "テレメトリとセンサー", + "title": "トラブルシューティング", + "content": ". | 環境データが表示されない？ リモートノードに物理センサーが接続されている必要があります（例：I2C の BME280）。 デバイステレメトリ（バッテリー、連続稼働時間）は常に利用できますが、環境メトリクスにはハードウェアが必要です。 | 測定値が古い？ 報告間隔を確認してください。非常に長い間隔（7200 秒以上）では、データの更新頻度が低くなります。 リモートノードがまだオンラインであるかも確認してください。 | I2C バスでセンサーが競合している？ 一部のセンサーは I2C アドレスを共有しています。 同じバスに複数のセンサーがある場合は、無線機のシリアルデバッグ出力でアドレスの衝突がないか確認してください。 | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.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/telemetry-and-sensors.html#トラブルシューティング" + },"5702": { + "doc": "テレメトリとセンサー", + "title": "関連トピック", + "content": ". | ノードメトリクス：ノードの詳細画面でテレメトリデータを表示 | 設定：モジュールと管理：テレメトリモジュールの設定 | 単位とロケール：温度と気圧の表示単位 | . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/telemetry-and-sensors.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF", + + "relUrl": "/ja-rJP/user/telemetry-and-sensors.html#関連トピック" + },"5703": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#telemetry--sensors" + },"5704": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#overview", + + "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#overview" + },"5705": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Leírás | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Feszültség | Battery voltage | 3.0–4.2V (LiPo) | . | Csatornahasználat | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Működési idő | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#device-telemetry" + },"5706": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Szenzor | Hőmérséklet | Páratartalom | Nyomás | Jegyzetek | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Szenzor | Metric | Jegyzetek | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Szenzor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#environment-sensors" + },"5707": { + "doc": "Telemetry & Sensors", + "title": "Tápellátási metrikák", + "content": "Nodes with INA-series power sensors can report: . | Metric | Leírás | . | Bus Voltage | Supply rail voltage | . | Áramerősség | Power consumption (mA) | . | Energia | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#t%C3%A1pell%C3%A1t%C3%A1si-metrik%C3%A1k", + + "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#tápellátási-metrikák" + },"5708": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#configuring-telemetry" + },"5709": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Leírás | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#air-quality-metrics" + },"5710": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#viewing-telemetry" + },"5711": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#troubleshooting" + },"5712": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/hu-rHU/user/telemetry-and-sensors.html#related-topics" + },"5713": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/hu-rHU/user/telemetry-and-sensors.html", + + "relUrl": "/hu-rHU/user/telemetry-and-sensors.html" + },"5714": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#telemetry--sensors" + },"5715": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#overview", + + "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#overview" + },"5716": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Deskripsyon | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Itilizasyon Kanal | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#device-telemetry" + },"5717": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Tanperati | Imidite | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#environment-sensors" + },"5718": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Deskripsyon | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#power-metrics" + },"5719": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#configuring-telemetry" + },"5720": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Deskripsyon | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#air-quality-metrics" + },"5721": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#viewing-telemetry" + },"5722": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#troubleshooting" + },"5723": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/ht-rHT/user/telemetry-and-sensors.html#related-topics" + },"5724": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/ht-rHT/user/telemetry-and-sensors.html", + + "relUrl": "/ht-rHT/user/telemetry-and-sensors.html" + },"5725": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/gl-rES/user/telemetry-and-sensors.html#telemetry--sensors" + },"5726": { + "doc": "Telemetry & Sensors", + "title": "Overview", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#overview", + + "relUrl": "/gl-rES/user/telemetry-and-sensors.html#overview" + },"5727": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Descrición | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltage | Battery voltage | 3.0–4.2V (LiPo) | . | Channel Utilization | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Uptime | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/gl-rES/user/telemetry-and-sensors.html#device-telemetry" + },"5728": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperature | Humidity | Pressure | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/gl-rES/user/telemetry-and-sensors.html#environment-sensors" + },"5729": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Descrición | . | Bus Voltage | Supply rail voltage | . | Current | Power consumption (mA) | . | Power | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/gl-rES/user/telemetry-and-sensors.html#power-metrics" + },"5730": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/gl-rES/user/telemetry-and-sensors.html#configuring-telemetry" + },"5731": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Descrición | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/gl-rES/user/telemetry-and-sensors.html#air-quality-metrics" + },"5732": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/gl-rES/user/telemetry-and-sensors.html#viewing-telemetry" + },"5733": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/gl-rES/user/telemetry-and-sensors.html#troubleshooting" + },"5734": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/gl-rES/user/telemetry-and-sensors.html#related-topics" + },"5735": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/gl-rES/user/telemetry-and-sensors.html", + + "relUrl": "/gl-rES/user/telemetry-and-sensors.html" + },"5736": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#telemetry--sensors" + },"5737": { + "doc": "Telemetry & Sensors", + "title": "Genel Bakış", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#genel-bak%C4%B1%C5%9F", + + "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#genel-bakış" + },"5738": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Metric | Açıklaması | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Voltaj | Battery voltage | 3.0–4.2V (LiPo) | . | Kanal Kullanımı | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Çalışma Süresi | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#device-telemetry" + },"5739": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Sıcaklık | Nem | Basınç | Notes | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Metric | Notes | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Metric | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#environment-sensors" + },"5740": { + "doc": "Telemetry & Sensors", + "title": "Power Metrics", + "content": "Nodes with INA-series power sensors can report: . | Metric | Açıklaması | . | Bus Voltage | Supply rail voltage | . | Akım | Power consumption (mA) | . | Güç | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#power-metrics", + + "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#power-metrics" + },"5741": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#configuring-telemetry" + },"5742": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Metric | Unit | Açıklaması | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#air-quality-metrics" + },"5743": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#viewing-telemetry" + },"5744": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#troubleshooting" + },"5745": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/tr-rTR/user/telemetry-and-sensors.html#related-topics" + },"5746": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/tr-rTR/user/telemetry-and-sensors.html", + + "relUrl": "/tr-rTR/user/telemetry-and-sensors.html" + },"5747": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": "Meshtastic nodes can collect and share sensor data across the mesh network. ", + "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#telemetry--sensors", + + "relUrl": "/es-rES/user/telemetry-and-sensors.html#telemetry--sensors" + },"5748": { + "doc": "Telemetry & Sensors", + "title": "Visión general", + "content": "Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time. ", + "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#visi%C3%B3n-general", + + "relUrl": "/es-rES/user/telemetry-and-sensors.html#visión-general" + },"5749": { + "doc": "Telemetry & Sensors", + "title": "Device Telemetry", + "content": "All Meshtastic nodes report basic device telemetry: . | Métrico | Descripción | Typical Range | . | Battery Level | Charge percentage | 0–100% | . | Tensión | Battery voltage | 3.0–4.2V (LiPo) | . | Utilización del canal | % of airtime used locally | 0–100% | . | Air Utilization TX | % of airtime used by this node | 0–100% | . | Tiempo encendido | Seconds since last boot | Varies | . ", + "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#device-telemetry", + + "relUrl": "/es-rES/user/telemetry-and-sensors.html#device-telemetry" + },"5750": { + "doc": "Telemetry & Sensors", + "title": "Environment Sensors", + "content": "Supported environmental sensors: . Temperature & Humidity . | Sensor | Temperatura: | Humedad | Presión | Notas | . | BME280 | ✓ | ✓ | ✓ | Recommended all-in-one | . | BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ | . | SHT31 | ✓ | ✓ | — | High accuracy | . | MCP9808 | ✓ | — | — | Precision temperature | . | LPS22 | — | — | ✓ | Pressure only | . Air Quality . | Sensor | Métrico | Notas | . | BME680 | Gas Resistance / IAQ | Volatile organic compounds | . | PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter | . | SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor | . Light & UV . | Sensor | Métrico | . | OPT3001 | Ambient light (lux) | . | VEML7700 | Ambient light (lux) | . | LTR390 | UV index | . ", + "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#environment-sensors", + + "relUrl": "/es-rES/user/telemetry-and-sensors.html#environment-sensors" + },"5751": { + "doc": "Telemetry & Sensors", + "title": "Métricas de Energía", + "content": "Nodes with INA-series power sensors can report: . | Métrico | Descripción | . | Bus Voltage | Supply rail voltage | . | Intensidad | Power consumption (mA) | . | Consumo | Calculated power (mW) | . Useful for monitoring solar charging or battery health on remote nodes. ", + "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#m%C3%A9tricas-de-energ%C3%ADa", + + "relUrl": "/es-rES/user/telemetry-and-sensors.html#métricas-de-energía" + },"5752": { + "doc": "Telemetry & Sensors", + "title": "Configuring Telemetry", + "content": ". | Navigate to Settings → Module Config → Telemetry. | Set reporting intervals: . | Device Metrics Interval — how often to broadcast device metrics | Environment Metrics Interval — how often to broadcast sensor data | . | Enable specific sensor types as needed. | . Recommended Intervals . | Use Case | Device (s) | Environment (s) | . | Urban mesh (many nodes) | 3600 | 3600 | . | Rural mesh (few nodes) | 900 | 900 | . | Weather station | 900 | 300 | . | Battery conservation | 7200 | 7200 | . ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh. ", + "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#configuring-telemetry", + + "relUrl": "/es-rES/user/telemetry-and-sensors.html#configuring-telemetry" + },"5753": { + "doc": "Telemetry & Sensors", + "title": "Air Quality Metrics", + "content": "Nodes with particulate matter or CO₂ sensors report air quality data: . | Métrico | Unit | Descripción | . | PM1.0 | µg/m³ | Ultrafine particulate matter | . | PM2.5 | µg/m³ | Fine particulate matter | . | PM10 | µg/m³ | Coarse particulate matter | . | CO₂ | ppm | Carbon dioxide concentration | . CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value. The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail. Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. ", + "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#air-quality-metrics", + + "relUrl": "/es-rES/user/telemetry-and-sensors.html#air-quality-metrics" + },"5754": { + "doc": "Telemetry & Sensors", + "title": "Viewing Telemetry", + "content": ". | Navigate to Nodes and select a node. | Telemetry sections show on the detail screen: . | Device Metrics (always available) | Environment Metrics (if sensors present) | Power Metrics (if INA sensor present) | Air Quality Metrics (if PM/CO₂ sensor present) | . | Historical graphs show trends over time. | . ", + "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#viewing-telemetry", + + "relUrl": "/es-rES/user/telemetry-and-sensors.html#viewing-telemetry" + },"5755": { + "doc": "Telemetry & Sensors", + "title": "Troubleshooting", + "content": ". | No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware. | Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online. | Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio’s serial debug output. | . ", + "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#troubleshooting", + + "relUrl": "/es-rES/user/telemetry-and-sensors.html#troubleshooting" + },"5756": { + "doc": "Telemetry & Sensors", + "title": "Related Topics", + "content": ". | Node Metrics — view telemetry data on the node detail screen | Settings — Modules & Admin — telemetry module configuration | Units & Locale — temperature and pressure display units | . ", + "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html#related-topics", + + "relUrl": "/es-rES/user/telemetry-and-sensors.html#related-topics" + },"5757": { + "doc": "Telemetry & Sensors", + "title": "Telemetry & Sensors", + "content": " ", + "url": "/Meshtastic-Android/main/es-rES/user/telemetry-and-sensors.html", + + "relUrl": "/es-rES/user/telemetry-and-sensors.html" },"5758": { "doc": "Test Builds & Obtainium", "title": "Test Builds & Obtainium", @@ -40410,1426 +40410,1426 @@ "relUrl": "/en/developer/testing.html#ci-integration" },"5773": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5774": { - "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/ | App Store 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" - },"5775": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#how-to-contribute", - - "relUrl": "/is-rIS/user/translate.html#how-to-contribute" - },"5776": { - "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" - },"5777": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#how-translations-are-organized", - - "relUrl": "/is-rIS/user/translate.html#how-translations-are-organized" - },"5778": { - "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 device 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" - },"5779": { - "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" - },"5780": { - "doc": "アプリを翻訳する", - "title": "アプリを翻訳する", - "content": "翻訳への貢献は、Meshtastic をより多くの人が使えるようにするのに役立ちます。 アプリは、ユーザーインターフェースとアプリ内ドキュメントの両方のコミュニティ翻訳を管理するために Crowdin を使用しています。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/translate.html", - - "relUrl": "/ja-rJP/user/translate.html" - },"5781": { - "doc": "アプリを翻訳する", - "title": "翻訳される対象", - "content": "| リソース | ソースの場所 | 備考 | . | UI 文字列 | core/resources/src/commonMain/composeResources/values/strings.xml | ボタン、ラベル、メッセージ、およびユーザーに表示されるすべてのテキスト | . | ユーザーガイドのページ | docs/en/user/*.md | 「ヘルプとドキュメント」に表示されるアプリ内ドキュメント | . | Fastlane メタデータ | fastlane/metadata/android/en-US/ | アプリストアの掲載タイトル、説明、変更履歴 | . ⚠️ 注意： 開発者ガイドのページは英語のみです。 コントリビューター向けの、コード中心のドキュメントは翻訳されません。 . ", - "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#翻訳される対象" - },"5782": { - "doc": "アプリを翻訳する", - "title": "貢献する方法", - "content": ". | Crowdin プロジェクトにアクセスします。 Meshtastic Android の Crowdin プロジェクト を開き、サインインするか、無料アカウントを作成します。 | 言語を選びます。 既存の言語を選択するか、GitHub の issue を作成して新しい言語をリクエストします。 | 文字列を翻訳します。 Crowdin では、左側に英語の原文、右側に自分の翻訳が表示されます。 各文字列を翻訳して保存します。 | コンテキストを確認します。 多くの文字列には、スクリーンショットやコンテキストのコメントが含まれています。これらを確認して、テキストがアプリのどこに表示されるかを把握してください。 | 送信します。 承認された翻訳は、次のリリースに自動的にマージされます。 | . 💡 ヒント： 翻訳は短くしてください。 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#貢献する方法" - },"5783": { - "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#新しい言語を追加する" - },"5784": { - "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/ ← ドイツ語（ドイツ） │ └── ... └── ... ロケールフォルダーは、Android のリソース規則 {lang}-r{REGION}（例：fr-rFR、de-rDE、ja-rJP）を使用し、アプリ文字列に使われる values-* ディレクトリと対応しています。 . アプリは、デバイスの言語と地域の設定に基づいて、正しいロケールを自動的に選択します。 . ", - "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#翻訳の構成" - },"5785": { - "doc": "アプリを翻訳する", - "title": "翻訳ガイドライン", - "content": ". | 「LoRa」「MQTT」「BLE」「TAK」「SNR」「RSSI」などの技術用語は翻訳しないでください。これらは共通です。 | プレースホルダーはそのまま保ちます。 %1$s や %d のような文字列は、実行時に値が埋め込まれます。 自分の言語の文法上必要な場合を除き、削除したり並び替えたりしないでください。 | トーンを合わせます。 アプリは、親しみやすく率直な語り口を使っています。 過度に堅い言葉は避けてください。 | 可能ならテストします。 デバイスの言語を切り替えてアプリを開き、翻訳が実際の文脈でどう見えるか確認してください。 | . ", - "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#翻訳ガイドライン" - },"5786": { - "doc": "アプリを翻訳する", - "title": "質問がありますか？", - "content": "特定の文字列のコンテキストについて質問がある場合や、始め方について助けが必要な場合は、Meshtastic GitHub Discussions のページでディスカッションを作成してください。 . 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#質問がありますか" - },"5787": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5788": { - "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/ | App Store 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" - },"5789": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#how-to-contribute", - - "relUrl": "/ca-rES/user/translate.html#how-to-contribute" - },"5790": { - "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" - },"5791": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#how-translations-are-organized", - - "relUrl": "/ca-rES/user/translate.html#how-translations-are-organized" - },"5792": { - "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 device 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" - },"5793": { - "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" - },"5794": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5795": { - "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/ | App Store 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" - },"5796": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html#how-to-contribute", - - "relUrl": "/sr-rLatn/user/translate.html#how-to-contribute" - },"5797": { - "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" - },"5798": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html#how-translations-are-organized", - - "relUrl": "/sr-rLatn/user/translate.html#how-translations-are-organized" - },"5799": { - "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 device 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" - },"5800": { - "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" - },"5801": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5802": { - "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/ | App Store 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" - },"5803": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html#how-to-contribute", - - "relUrl": "/ko-rKR/user/translate.html#how-to-contribute" - },"5804": { - "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" - },"5805": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html#how-translations-are-organized", - - "relUrl": "/ko-rKR/user/translate.html#how-translations-are-organized" - },"5806": { - "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 device 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" - },"5807": { - "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" - },"5808": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5809": { - "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/ | App Store 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" - },"5810": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#how-to-contribute", - - "relUrl": "/ro-rRO/user/translate.html#how-to-contribute" - },"5811": { - "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" - },"5812": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#how-translations-are-organized", - - "relUrl": "/ro-rRO/user/translate.html#how-translations-are-organized" - },"5813": { - "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 device 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" - },"5814": { - "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" - },"5815": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5816": { - "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/ | App Store 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" - },"5817": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#how-to-contribute", - - "relUrl": "/ga-rIE/user/translate.html#how-to-contribute" - },"5818": { - "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" - },"5819": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#how-translations-are-organized", - - "relUrl": "/ga-rIE/user/translate.html#how-translations-are-organized" - },"5820": { - "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 device 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" - },"5821": { - "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" - },"5822": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5823": { - "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/ | App Store 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" - },"5824": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html#how-to-contribute", - - "relUrl": "/iw-rIL/user/translate.html#how-to-contribute" - },"5825": { - "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" - },"5826": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html#how-translations-are-organized", - - "relUrl": "/iw-rIL/user/translate.html#how-translations-are-organized" - },"5827": { - "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 device 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" - },"5828": { - "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" - },"5829": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5830": { - "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/ | App Store 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" - },"5831": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html#how-to-contribute", - - "relUrl": "/sv-rSE/user/translate.html#how-to-contribute" - },"5832": { - "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" - },"5833": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html#how-translations-are-organized", - - "relUrl": "/sv-rSE/user/translate.html#how-translations-are-organized" - },"5834": { - "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 device 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" - },"5835": { - "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" - },"5836": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5837": { - "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/ | App Store 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" - },"5838": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#how-to-contribute", - - "relUrl": "/ht-rHT/user/translate.html#how-to-contribute" - },"5839": { - "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" - },"5840": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#how-translations-are-organized", - - "relUrl": "/ht-rHT/user/translate.html#how-translations-are-organized" - },"5841": { - "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 device 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" - },"5842": { - "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" - },"5843": { - "doc": "Käännä sovellus", - "title": "Käännä sovellus", - "content": "Käännöksiin osallistuminen auttaa tekemään Meshtasticista saavutettavamman laajemmalle yleisölle. 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" - },"5844": { - "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/ | Sovelluskaupan listauksen otsikko, kuvaus ja muutoslokit | . ⚠️ Huomautus: Kehittäjän oppaan 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" - },"5845": { - "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. | Lähetä. Hyväksytyt käännökset yhdistetään automaattisesti seuraavaan julkaisuun. | . 💡 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" - },"5846": { - "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" - },"5847": { - "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) │ └── ... └── ... Aluekansiot käyttävät Androidin resurssikäytäntöä {kieli}-r{ALUE} (esim. fr-rFR, de-rDE, ja-rJP), joka vastaa sovelluksen merkkijonoissa käytettyjä values-*-hakemistoja. Sovellus valitsee automaattisesti oikean kielialueen laitteen Kieli & alue -asetusten perusteella. ", - "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" - },"5848": { - "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 jos mahdollista. Vaihda laitteesi kieli ja avaa sovellus nähdäksesi käännökset kontekstissa. | . ", - "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" - },"5849": { - "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ää" - },"5850": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5851": { - "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/ | App Store 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" - },"5852": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#how-to-contribute", - - "relUrl": "/gl-rES/user/translate.html#how-to-contribute" - },"5853": { - "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" - },"5854": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#how-translations-are-organized", - - "relUrl": "/gl-rES/user/translate.html#how-translations-are-organized" - },"5855": { - "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 device 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" - },"5856": { - "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" - },"5857": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5858": { - "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/ | App Store 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" - },"5859": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html#how-to-contribute", - - "relUrl": "/uk-rUA/user/translate.html#how-to-contribute" - },"5860": { - "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" - },"5861": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html#how-translations-are-organized", - - "relUrl": "/uk-rUA/user/translate.html#how-translations-are-organized" - },"5862": { - "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 device 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" - },"5863": { - "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" - },"5864": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5865": { + },"5774": { "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/ | App Store 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" - },"5866": { + },"5775": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", "url": "/Meshtastic-Android/main/de-rDE/user/translate.html#wie-man-beitragen-kann", "relUrl": "/de-rDE/user/translate.html#wie-man-beitragen-kann" - },"5867": { + },"5776": { "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" - },"5868": { + },"5777": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", "url": "/Meshtastic-Android/main/de-rDE/user/translate.html#how-translations-are-organized", "relUrl": "/de-rDE/user/translate.html#how-translations-are-organized" - },"5869": { + },"5778": { "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 device 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" - },"5870": { + },"5779": { "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. Vielen Dank, dass Sie dabei geholfen haben, die Reichweite von Meshtastic zu vergrößern! . ", "url": "/Meshtastic-Android/main/de-rDE/user/translate.html#questions", "relUrl": "/de-rDE/user/translate.html#questions" - },"5871": { + },"5780": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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", + "url": "/Meshtastic-Android/main/ca-rES/user/translate.html", - "relUrl": "/hr-rHR/user/translate.html" - },"5872": { + "relUrl": "/ca-rES/user/translate.html" + },"5781": { "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/ | App Store 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", + "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#what-gets-translated", - "relUrl": "/hr-rHR/user/translate.html#what-gets-translated" - },"5873": { + "relUrl": "/ca-rES/user/translate.html#what-gets-translated" + },"5782": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#how-to-contribute", + "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#how-to-contribute", - "relUrl": "/hr-rHR/user/translate.html#how-to-contribute" - },"5874": { + "relUrl": "/ca-rES/user/translate.html#how-to-contribute" + },"5783": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#adding-a-new-language", - "relUrl": "/hr-rHR/user/translate.html#adding-a-new-language" - },"5875": { + "relUrl": "/ca-rES/user/translate.html#adding-a-new-language" + },"5784": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#how-translations-are-organized", + "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#how-translations-are-organized", - "relUrl": "/hr-rHR/user/translate.html#how-translations-are-organized" - },"5876": { + "relUrl": "/ca-rES/user/translate.html#how-translations-are-organized" + },"5785": { "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 device language and open the app to see how translations look in context. | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#translation-guidelines", + "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#translation-guidelines", - "relUrl": "/hr-rHR/user/translate.html#translation-guidelines" - },"5877": { + "relUrl": "/ca-rES/user/translate.html#translation-guidelines" + },"5786": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#questions", - "relUrl": "/hr-rHR/user/translate.html#questions" - },"5878": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5879": { - "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/ | App Store 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" - },"5880": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html#how-to-contribute", - - "relUrl": "/lt-rLT/user/translate.html#how-to-contribute" - },"5881": { - "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" - },"5882": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html#how-translations-are-organized", - - "relUrl": "/lt-rLT/user/translate.html#how-translations-are-organized" - },"5883": { - "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 device 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" - },"5884": { - "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" - },"5885": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5886": { - "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/ | App Store 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" - },"5887": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/en/user/translate.html#how-to-contribute", - - "relUrl": "/en/user/translate.html#how-to-contribute" - },"5888": { - "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" - },"5889": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/en/user/translate.html#how-translations-are-organized", - - "relUrl": "/en/user/translate.html#how-translations-are-organized" - },"5890": { - "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 device 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" - },"5891": { - "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" - },"5892": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5893": { - "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/ | App Store 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" - },"5894": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#how-to-contribute", - - "relUrl": "/hu-rHU/user/translate.html#how-to-contribute" - },"5895": { - "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" - },"5896": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#how-translations-are-organized", - - "relUrl": "/hu-rHU/user/translate.html#how-translations-are-organized" - },"5897": { - "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 device 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" - },"5898": { - "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" - },"5899": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html", - - "relUrl": "/bg-rBG/user/translate.html" - },"5900": { - "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/ | App Store 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" - },"5901": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "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#как-да-допринесете" - },"5902": { - "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/bg-rBG/user/translate.html#adding-a-new-language", - - "relUrl": "/bg-rBG/user/translate.html#adding-a-new-language" - },"5903": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html#how-translations-are-organized", - - "relUrl": "/bg-rBG/user/translate.html#how-translations-are-organized" - },"5904": { - "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 device 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" - },"5905": { - "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. Благодарим ви, че помогнахте за разширяването на обхвата на Meshtastic! . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html#questions", - - "relUrl": "/bg-rBG/user/translate.html#questions" - },"5906": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5907": { - "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/ | App Store 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" - },"5908": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html#how-to-contribute", - - "relUrl": "/sl-rSI/user/translate.html#how-to-contribute" - },"5909": { - "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" - },"5910": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html#how-translations-are-organized", - - "relUrl": "/sl-rSI/user/translate.html#how-translations-are-organized" - },"5911": { - "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 device 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" - },"5912": { - "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" - },"5913": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5914": { - "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/ | App Store 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" - },"5915": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html#how-to-contribute", - - "relUrl": "/pt-rPT/user/translate.html#how-to-contribute" - },"5916": { - "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" - },"5917": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html#how-translations-are-organized", - - "relUrl": "/pt-rPT/user/translate.html#how-translations-are-organized" - },"5918": { - "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 device 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" - },"5919": { - "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" - },"5920": { + "relUrl": "/ca-rES/user/translate.html#questions" + },"5787": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5921": { + },"5788": { "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/ | App Store 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" - },"5922": { + },"5789": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", "url": "/Meshtastic-Android/main/be-rBY/user/translate.html#how-to-contribute", "relUrl": "/be-rBY/user/translate.html#how-to-contribute" - },"5923": { + },"5790": { "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" - },"5924": { + },"5791": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", "url": "/Meshtastic-Android/main/be-rBY/user/translate.html#how-translations-are-organized", "relUrl": "/be-rBY/user/translate.html#how-translations-are-organized" - },"5925": { + },"5792": { "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 device 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" - },"5926": { + },"5793": { "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" - },"5927": { + },"5794": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5795": { + "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/ | App Store 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" + },"5796": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html#how-to-contribute", + + "relUrl": "/uk-rUA/user/translate.html#how-to-contribute" + },"5797": { + "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" + },"5798": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html#how-translations-are-organized", + + "relUrl": "/uk-rUA/user/translate.html#how-translations-are-organized" + },"5799": { + "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 device 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" + },"5800": { + "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" + },"5801": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5802": { + "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/ | App Store 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" + },"5803": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#how-to-contribute", + + "relUrl": "/zh-rCN/user/translate.html#how-to-contribute" + },"5804": { + "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" + },"5805": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#how-translations-are-organized", + + "relUrl": "/zh-rCN/user/translate.html#how-translations-are-organized" + },"5806": { + "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 device 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" + },"5807": { + "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" + },"5808": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html", + + "relUrl": "/bg-rBG/user/translate.html" + },"5809": { + "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/ | App Store 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" + },"5810": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "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#как-да-допринесете" + },"5811": { + "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/bg-rBG/user/translate.html#adding-a-new-language", + + "relUrl": "/bg-rBG/user/translate.html#adding-a-new-language" + },"5812": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html#how-translations-are-organized", + + "relUrl": "/bg-rBG/user/translate.html#how-translations-are-organized" + },"5813": { + "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 device 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" + },"5814": { + "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. Благодарим ви, че помогнахте за разширяването на обхвата на Meshtastic! . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html#questions", + + "relUrl": "/bg-rBG/user/translate.html#questions" + },"5815": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5816": { + "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/ | App Store 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" + },"5817": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "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#如何貢獻" + },"5818": { + "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" + },"5819": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#how-translations-are-organized", + + "relUrl": "/zh-rTW/user/translate.html#how-translations-are-organized" + },"5820": { + "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 device 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" + },"5821": { + "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. 感謝您協助擴展 Meshtastic 的觸及範圍！ . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#questions", + + "relUrl": "/zh-rTW/user/translate.html#questions" + },"5822": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5823": { + "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/ | App Store 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" + },"5824": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html#how-to-contribute", + + "relUrl": "/sr-rLatn/user/translate.html#how-to-contribute" + },"5825": { + "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" + },"5826": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html#how-translations-are-organized", + + "relUrl": "/sr-rLatn/user/translate.html#how-translations-are-organized" + },"5827": { + "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 device 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" + },"5828": { + "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" + },"5829": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html", + + "relUrl": "/cs-rCZ/user/translate.html" + },"5830": { + "doc": "Translate the App", + "title": "What Gets Translated", + "content": "| Resource | Source Location | Poznámka | . | 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/ | App Store listing title, description, and changelogs | . ⚠️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#what-gets-translated", + + "relUrl": "/cs-rCZ/user/translate.html#what-gets-translated" + },"5831": { + "doc": "Translate the App", + "title": "Jak přispět", + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "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" + },"5832": { + "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/cs-rCZ/user/translate.html#adding-a-new-language", + + "relUrl": "/cs-rCZ/user/translate.html#adding-a-new-language" + },"5833": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#how-translations-are-organized", + + "relUrl": "/cs-rCZ/user/translate.html#how-translations-are-organized" + },"5834": { + "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 device language and open the app to see how translations look in context. | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#translation-guidelines", + + "relUrl": "/cs-rCZ/user/translate.html#translation-guidelines" + },"5835": { + "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. Děkujeme, že jste pomohli rozšířit dosah Meshtastic! . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#questions", + + "relUrl": "/cs-rCZ/user/translate.html#questions" + },"5836": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5837": { + "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/ | App Store 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" + },"5838": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/en/user/translate.html#how-to-contribute", + + "relUrl": "/en/user/translate.html#how-to-contribute" + },"5839": { + "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" + },"5840": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/en/user/translate.html#how-translations-are-organized", + + "relUrl": "/en/user/translate.html#how-translations-are-organized" + },"5841": { + "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 device 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" + },"5842": { + "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" + },"5843": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5844": { + "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/ | App Store 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" + },"5845": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html#how-to-contribute", + + "relUrl": "/sl-rSI/user/translate.html#how-to-contribute" + },"5846": { + "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" + },"5847": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html#how-translations-are-organized", + + "relUrl": "/sl-rSI/user/translate.html#how-translations-are-organized" + },"5848": { + "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 device 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" + },"5849": { + "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" + },"5850": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5851": { + "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/ | App Store 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" + },"5852": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#how-to-contribute", + + "relUrl": "/it-rIT/user/translate.html#how-to-contribute" + },"5853": { + "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" + },"5854": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#how-translations-are-organized", + + "relUrl": "/it-rIT/user/translate.html#how-translations-are-organized" + },"5855": { + "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 device 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" + },"5856": { + "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" + },"5857": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5928": { + },"5858": { "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/ | App Store 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" - },"5929": { + },"5859": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", "url": "/Meshtastic-Android/main/pt-rBR/user/translate.html#how-to-contribute", "relUrl": "/pt-rBR/user/translate.html#how-to-contribute" - },"5930": { + },"5860": { "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" - },"5931": { + },"5861": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", "url": "/Meshtastic-Android/main/pt-rBR/user/translate.html#how-translations-are-organized", "relUrl": "/pt-rBR/user/translate.html#how-translations-are-organized" - },"5932": { + },"5862": { "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 device 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" - },"5933": { + },"5863": { "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" - },"5934": { + },"5864": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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", + "url": "/Meshtastic-Android/main/is-rIS/user/translate.html", - "relUrl": "/el-rGR/user/translate.html" - },"5935": { + "relUrl": "/is-rIS/user/translate.html" + },"5865": { "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/ | App Store 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", + "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#what-gets-translated", - "relUrl": "/el-rGR/user/translate.html#what-gets-translated" - },"5936": { + "relUrl": "/is-rIS/user/translate.html#what-gets-translated" + },"5866": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#how-to-contribute", + "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#how-to-contribute", - "relUrl": "/el-rGR/user/translate.html#how-to-contribute" - },"5937": { + "relUrl": "/is-rIS/user/translate.html#how-to-contribute" + },"5867": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#adding-a-new-language", - "relUrl": "/el-rGR/user/translate.html#adding-a-new-language" - },"5938": { + "relUrl": "/is-rIS/user/translate.html#adding-a-new-language" + },"5868": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#how-translations-are-organized", + "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#how-translations-are-organized", - "relUrl": "/el-rGR/user/translate.html#how-translations-are-organized" - },"5939": { + "relUrl": "/is-rIS/user/translate.html#how-translations-are-organized" + },"5869": { "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 device language and open the app to see how translations look in context. | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#translation-guidelines", + "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#translation-guidelines", - "relUrl": "/el-rGR/user/translate.html#translation-guidelines" - },"5940": { + "relUrl": "/is-rIS/user/translate.html#translation-guidelines" + },"5870": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#questions", - "relUrl": "/el-rGR/user/translate.html#questions" - },"5941": { + "relUrl": "/is-rIS/user/translate.html#questions" + },"5871": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html", - "relUrl": "/es-rES/user/translate.html" - },"5942": { - "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/ | App Store 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" - },"5943": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/es-rES/user/translate.html#how-to-contribute", - - "relUrl": "/es-rES/user/translate.html#how-to-contribute" - },"5944": { - "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" - },"5945": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/es-rES/user/translate.html#how-translations-are-organized", - - "relUrl": "/es-rES/user/translate.html#how-translations-are-organized" - },"5946": { - "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 device 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" - },"5947": { - "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" - },"5948": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5949": { + "relUrl": "/fr-rFR/user/translate.html" + },"5872": { "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/ | App Store 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#what-gets-translated", - "relUrl": "/tr-rTR/user/translate.html#what-gets-translated" - },"5950": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "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" - },"5951": { - "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" - },"5952": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#how-translations-are-organized", - - "relUrl": "/tr-rTR/user/translate.html#how-translations-are-organized" - },"5953": { - "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 device 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" - },"5954": { - "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. Meshtastic’in erişimini genişletmemize yardımcı olduğunuz için teşekkür ederiz! . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#questions", - - "relUrl": "/tr-rTR/user/translate.html#questions" - },"5955": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5956": { - "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/ | App Store 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" - },"5957": { + "relUrl": "/fr-rFR/user/translate.html#what-gets-translated" + },"5873": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#how-to-contribute", + "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#how-to-contribute", - "relUrl": "/no-rNO/user/translate.html#how-to-contribute" - },"5958": { + "relUrl": "/fr-rFR/user/translate.html#how-to-contribute" + },"5874": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#adding-a-new-language", - "relUrl": "/no-rNO/user/translate.html#adding-a-new-language" - },"5959": { + "relUrl": "/fr-rFR/user/translate.html#adding-a-new-language" + },"5875": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#how-translations-are-organized", + "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#how-translations-are-organized", - "relUrl": "/no-rNO/user/translate.html#how-translations-are-organized" - },"5960": { + "relUrl": "/fr-rFR/user/translate.html#how-translations-are-organized" + },"5876": { "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 device language and open the app to see how translations look in context. | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#translation-guidelines", + "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#translation-guidelines", - "relUrl": "/no-rNO/user/translate.html#translation-guidelines" - },"5961": { + "relUrl": "/fr-rFR/user/translate.html#translation-guidelines" + },"5877": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#questions", - "relUrl": "/no-rNO/user/translate.html#questions" - },"5962": { + "relUrl": "/fr-rFR/user/translate.html#questions" + },"5878": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5879": { + "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/ | App Store 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" + },"5880": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/srp/user/translate.html#how-to-contribute", + + "relUrl": "/srp/user/translate.html#how-to-contribute" + },"5881": { + "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" + },"5882": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/srp/user/translate.html#how-translations-are-organized", + + "relUrl": "/srp/user/translate.html#how-translations-are-organized" + },"5883": { + "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 device 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" + },"5884": { + "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" + },"5885": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5886": { + "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/ | App Store 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" + },"5887": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html#how-to-contribute", + + "relUrl": "/sk-rSK/user/translate.html#how-to-contribute" + },"5888": { + "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" + },"5889": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html#how-translations-are-organized", + + "relUrl": "/sk-rSK/user/translate.html#how-translations-are-organized" + },"5890": { + "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 device 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" + },"5891": { + "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" + },"5892": { + "doc": "Käännä sovellus", + "title": "Käännä sovellus", + "content": "Käännöksiin osallistuminen auttaa tekemään Meshtasticista saavutettavamman laajemmalle yleisölle. 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" + },"5893": { + "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/ | Sovelluskaupan listauksen otsikko, kuvaus ja muutoslokit | . ⚠️ Huomautus: Kehittäjän oppaan 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" + },"5894": { + "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. | Lähetä. Hyväksytyt käännökset yhdistetään automaattisesti seuraavaan julkaisuun. | . 💡 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" + },"5895": { + "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" + },"5896": { + "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) │ └── ... └── ... Aluekansiot käyttävät Androidin resurssikäytäntöä {kieli}-r{ALUE} (esim. fr-rFR, de-rDE, ja-rJP), joka vastaa sovelluksen merkkijonoissa käytettyjä values-*-hakemistoja. Sovellus valitsee automaattisesti oikean kielialueen laitteen Kieli & alue -asetusten perusteella. ", + "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" + },"5897": { + "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 jos mahdollista. Vaihda laitteesi kieli ja avaa sovellus nähdäksesi käännökset kontekstissa. | . ", + "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" + },"5898": { + "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ää" + },"5899": { "doc": "Перевод приложения", "title": "Перевод приложения", "content": "Внесение вклада в перевод помогает сделать Meshtastic доступным для более широкой аудитории. Приложение использует Crowdin для управления переводами сообщества как для пользовательского интерфейса, так и для документации в приложении. ", "url": "/Meshtastic-Android/main/ru-rRU/user/translate.html", "relUrl": "/ru-rRU/user/translate.html" - },"5963": { + },"5900": { "doc": "Перевод приложения", "title": "Что переводится", "content": "| Ресурс | Исходное местоположение | Заметки | . | Строки интерфейса | core/resources/src/commonMain/composeResources/values/strings.xml | Кнопки, ярлыки, сообщения и весь видимый пользователю текст | . | Страницы руководства пользователя | docs/en/user/*.md | Встроенная документация, отображаемая в разделе «Справка и документация» | . | Метаданные Fastlane | fastlane/metadata/android/en-US/ | Название, описание и журналы изменений в App Store | . ⚠️ Примечание: Страницы руководства для разработчиков только на английском. Документация, ориентированная на код и для участников, не переводится. ", "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#что-переводится" - },"5964": { + },"5901": { "doc": "Перевод приложения", "title": "Как внести вклад", "content": ". | Посетите проект Crowdin. Откройте проект Meshtastic Android на Crowdin и войдите в систему или создайте бесплатный аккаунт. | Выберите свой язык. Выберите существующий язык или запросите новый, открыв GitHub issue. | Переводите строки. 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#как-внести-вклад" - },"5965": { + },"5902": { "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#добавление-нового-языка" - },"5966": { + },"5903": { "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}-r{REGION} (например, fr-rFR, de-rDE, ja-rJP), совпадая с директориями values-*, которые используются для строк в приложении. Приложение автоматически выбирает правильную локаль на основе настроек Язык и регион вашего устройства. ", "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#как-организованы-переводы" - },"5967": { + },"5904": { "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#руководство-по-переводу" - },"5968": { + },"5905": { "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#вопросы" + },"5906": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5907": { + "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/ | App Store 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" + },"5908": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html#how-to-contribute", + + "relUrl": "/ko-rKR/user/translate.html#how-to-contribute" + },"5909": { + "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" + },"5910": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html#how-translations-are-organized", + + "relUrl": "/ko-rKR/user/translate.html#how-translations-are-organized" + },"5911": { + "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 device 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" + },"5912": { + "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" + },"5913": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5914": { + "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/ | App Store 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" + },"5915": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#how-to-contribute", + + "relUrl": "/hr-rHR/user/translate.html#how-to-contribute" + },"5916": { + "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" + },"5917": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#how-translations-are-organized", + + "relUrl": "/hr-rHR/user/translate.html#how-translations-are-organized" + },"5918": { + "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 device 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" + },"5919": { + "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" + },"5920": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5921": { + "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/ | App Store 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" + },"5922": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#how-to-contribute", + + "relUrl": "/sq-rAL/user/translate.html#how-to-contribute" + },"5923": { + "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" + },"5924": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#how-translations-are-organized", + + "relUrl": "/sq-rAL/user/translate.html#how-translations-are-organized" + },"5925": { + "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 device 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" + },"5926": { + "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" + },"5927": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5928": { + "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/ | App Store 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" + },"5929": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#how-to-contribute", + + "relUrl": "/no-rNO/user/translate.html#how-to-contribute" + },"5930": { + "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" + },"5931": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#how-translations-are-organized", + + "relUrl": "/no-rNO/user/translate.html#how-translations-are-organized" + },"5932": { + "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 device 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" + },"5933": { + "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" + },"5934": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5935": { + "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/ | App Store 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" + },"5936": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html#how-to-contribute", + + "relUrl": "/lt-rLT/user/translate.html#how-to-contribute" + },"5937": { + "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" + },"5938": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html#how-translations-are-organized", + + "relUrl": "/lt-rLT/user/translate.html#how-translations-are-organized" + },"5939": { + "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 device 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" + },"5940": { + "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" + },"5941": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5942": { + "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/ | App Store 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" + },"5943": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html#how-to-contribute", + + "relUrl": "/ar-rSA/user/translate.html#how-to-contribute" + },"5944": { + "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" + },"5945": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html#how-translations-are-organized", + + "relUrl": "/ar-rSA/user/translate.html#how-translations-are-organized" + },"5946": { + "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 device 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" + },"5947": { + "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" + },"5948": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5949": { + "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/ | App Store 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" + },"5950": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html#how-to-contribute", + + "relUrl": "/pt-rPT/user/translate.html#how-to-contribute" + },"5951": { + "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" + },"5952": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html#how-translations-are-organized", + + "relUrl": "/pt-rPT/user/translate.html#how-translations-are-organized" + },"5953": { + "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 device 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" + },"5954": { + "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" + },"5955": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5956": { + "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/ | App Store 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" + },"5957": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html#how-to-contribute", + + "relUrl": "/iw-rIL/user/translate.html#how-to-contribute" + },"5958": { + "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" + },"5959": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html#how-translations-are-organized", + + "relUrl": "/iw-rIL/user/translate.html#how-translations-are-organized" + },"5960": { + "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 device 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" + },"5961": { + "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" + },"5962": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"5963": { + "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/ | App Store 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" + },"5964": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#how-to-contribute", + + "relUrl": "/el-rGR/user/translate.html#how-to-contribute" + },"5965": { + "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" + },"5966": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#how-translations-are-organized", + + "relUrl": "/el-rGR/user/translate.html#how-translations-are-organized" + },"5967": { + "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 device 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" + },"5968": { + "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" },"5969": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html", - "relUrl": "/nl-rNL/user/translate.html" + "relUrl": "/ro-rRO/user/translate.html" },"5970": { "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/ | App Store 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", + "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/ | App Store 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": "/nl-rNL/user/translate.html#what-gets-translated" + "relUrl": "/ro-rRO/user/translate.html#what-gets-translated" },"5971": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#how-to-contribute", + "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#how-to-contribute", - "relUrl": "/nl-rNL/user/translate.html#how-to-contribute" + "relUrl": "/ro-rRO/user/translate.html#how-to-contribute" },"5972": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#adding-a-new-language", - "relUrl": "/nl-rNL/user/translate.html#adding-a-new-language" + "relUrl": "/ro-rRO/user/translate.html#adding-a-new-language" },"5973": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#how-translations-are-organized", + "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#how-translations-are-organized", - "relUrl": "/nl-rNL/user/translate.html#how-translations-are-organized" + "relUrl": "/ro-rRO/user/translate.html#how-translations-are-organized" },"5974": { "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 device language and open the app to see how translations look in context. | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#translation-guidelines", + "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#translation-guidelines", - "relUrl": "/nl-rNL/user/translate.html#translation-guidelines" + "relUrl": "/ro-rRO/user/translate.html#translation-guidelines" },"5975": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#questions", - "relUrl": "/nl-rNL/user/translate.html#questions" + "relUrl": "/ro-rRO/user/translate.html#questions" },"5976": { "doc": "Tõlgi rakendus", "title": "Tõlgi rakendus", @@ -41883,492 +41883,492 @@ "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html", - "relUrl": "/it-rIT/user/translate.html" + "relUrl": "/ga-rIE/user/translate.html" },"5984": { "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/ | App Store 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", + "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/ | App Store 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": "/it-rIT/user/translate.html#what-gets-translated" + "relUrl": "/ga-rIE/user/translate.html#what-gets-translated" },"5985": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#how-to-contribute", + "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#how-to-contribute", - "relUrl": "/it-rIT/user/translate.html#how-to-contribute" + "relUrl": "/ga-rIE/user/translate.html#how-to-contribute" },"5986": { "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#adding-a-new-language", - "relUrl": "/it-rIT/user/translate.html#adding-a-new-language" + "relUrl": "/ga-rIE/user/translate.html#adding-a-new-language" },"5987": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#how-translations-are-organized", + "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#how-translations-are-organized", - "relUrl": "/it-rIT/user/translate.html#how-translations-are-organized" + "relUrl": "/ga-rIE/user/translate.html#how-translations-are-organized" },"5988": { "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 device language and open the app to see how translations look in context. | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#translation-guidelines", + "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#translation-guidelines", - "relUrl": "/it-rIT/user/translate.html#translation-guidelines" + "relUrl": "/ga-rIE/user/translate.html#translation-guidelines" },"5989": { "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#questions", - "relUrl": "/it-rIT/user/translate.html#questions" + "relUrl": "/ga-rIE/user/translate.html#questions" },"5990": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5991": { - "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/ | App Store 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" - },"5992": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html#how-to-contribute", - - "relUrl": "/ar-rSA/user/translate.html#how-to-contribute" - },"5993": { - "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" - },"5994": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html#how-translations-are-organized", - - "relUrl": "/ar-rSA/user/translate.html#how-translations-are-organized" - },"5995": { - "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 device 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" - },"5996": { - "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" - },"5997": { - "doc": "Translate the App", - "title": "Translate the App", - "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"5998": { - "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/ | App Store 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" - },"5999": { - "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html#how-to-contribute", - - "relUrl": "/sk-rSK/user/translate.html#how-to-contribute" - },"6000": { - "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" - },"6001": { - "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html#how-translations-are-organized", - - "relUrl": "/sk-rSK/user/translate.html#how-translations-are-organized" - },"6002": { - "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 device 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" - },"6003": { - "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" - },"6004": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" - },"6005": { + },"5991": { "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/ | App Store 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" - },"6006": { + },"5992": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", "url": "/Meshtastic-Android/main/pl-rPL/user/translate.html#how-to-contribute", "relUrl": "/pl-rPL/user/translate.html#how-to-contribute" - },"6007": { + },"5993": { "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" - },"6008": { + },"5994": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", "url": "/Meshtastic-Android/main/pl-rPL/user/translate.html#how-translations-are-organized", "relUrl": "/pl-rPL/user/translate.html#how-translations-are-organized" - },"6009": { + },"5995": { "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 device 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" - },"6010": { + },"5996": { "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" - },"6011": { + },"5997": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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", + "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html", - "relUrl": "/zh-rTW/user/translate.html" - },"6012": { + "relUrl": "/nl-rNL/user/translate.html" + },"5998": { "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/ | App Store 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", + "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/ | App Store 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": "/zh-rTW/user/translate.html#what-gets-translated" - },"6013": { + "relUrl": "/nl-rNL/user/translate.html#what-gets-translated" + },"5999": { "doc": "Translate the App", - "title": "如何貢獻", + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#%E5%A6%82%E4%BD%95%E8%B2%A2%E7%8D%BB", + "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#how-to-contribute", - "relUrl": "/zh-rTW/user/translate.html#如何貢獻" - },"6014": { + "relUrl": "/nl-rNL/user/translate.html#how-to-contribute" + },"6000": { "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", + "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#adding-a-new-language", - "relUrl": "/zh-rTW/user/translate.html#adding-a-new-language" - },"6015": { + "relUrl": "/nl-rNL/user/translate.html#adding-a-new-language" + },"6001": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#how-translations-are-organized", + "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#how-translations-are-organized", - "relUrl": "/zh-rTW/user/translate.html#how-translations-are-organized" - },"6016": { + "relUrl": "/nl-rNL/user/translate.html#how-translations-are-organized" + },"6002": { "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 device language and open the app to see how translations look in context. | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#translation-guidelines", + "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#translation-guidelines", - "relUrl": "/zh-rTW/user/translate.html#translation-guidelines" - },"6017": { + "relUrl": "/nl-rNL/user/translate.html#translation-guidelines" + },"6003": { "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. 感謝您協助擴展 Meshtastic 的觸及範圍！ . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#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": "/zh-rTW/user/translate.html#questions" + "relUrl": "/nl-rNL/user/translate.html#questions" + },"6004": { + "doc": "Translate the App", + "title": "Translate the App", + "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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" + },"6005": { + "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/ | App Store 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" + },"6006": { + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html#how-to-contribute", + + "relUrl": "/sv-rSE/user/translate.html#how-to-contribute" + },"6007": { + "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" + },"6008": { + "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html#how-translations-are-organized", + + "relUrl": "/sv-rSE/user/translate.html#how-translations-are-organized" + },"6009": { + "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 device 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" + },"6010": { + "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" + },"6011": { + "doc": "アプリを翻訳する", + "title": "アプリを翻訳する", + "content": "翻訳への貢献は、Meshtastic をより多くの人が使えるようにするのに役立ちます。 アプリは、ユーザーインターフェースとアプリ内ドキュメントの両方のコミュニティ翻訳を管理するために Crowdin を使用しています。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/translate.html", + + "relUrl": "/ja-rJP/user/translate.html" + },"6012": { + "doc": "アプリを翻訳する", + "title": "翻訳される対象", + "content": "| リソース | ソースの場所 | 備考 | . | UI 文字列 | core/resources/src/commonMain/composeResources/values/strings.xml | ボタン、ラベル、メッセージ、およびユーザーに表示されるすべてのテキスト | . | ユーザーガイドのページ | docs/en/user/*.md | 「ヘルプとドキュメント」に表示されるアプリ内ドキュメント | . | Fastlane メタデータ | fastlane/metadata/android/en-US/ | アプリストアの掲載タイトル、説明、変更履歴 | . ⚠️ 注意： 開発者ガイドのページは英語のみです。 コントリビューター向けの、コード中心のドキュメントは翻訳されません。 . ", + "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#翻訳される対象" + },"6013": { + "doc": "アプリを翻訳する", + "title": "貢献する方法", + "content": ". | Crowdin プロジェクトにアクセスします。 Meshtastic Android の Crowdin プロジェクト を開き、サインインするか、無料アカウントを作成します。 | 言語を選びます。 既存の言語を選択するか、GitHub の issue を作成して新しい言語をリクエストします。 | 文字列を翻訳します。 Crowdin では、左側に英語の原文、右側に自分の翻訳が表示されます。 各文字列を翻訳して保存します。 | コンテキストを確認します。 多くの文字列には、スクリーンショットやコンテキストのコメントが含まれています。これらを確認して、テキストがアプリのどこに表示されるかを把握してください。 | 送信します。 承認された翻訳は、次のリリースに自動的にマージされます。 | . 💡 ヒント： 翻訳は短くしてください。 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#貢献する方法" + },"6014": { + "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#新しい言語を追加する" + },"6015": { + "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/ ← ドイツ語（ドイツ） │ └── ... └── ... ロケールフォルダーは、Android のリソース規則 {lang}-r{REGION}（例：fr-rFR、de-rDE、ja-rJP）を使用し、アプリ文字列に使われる values-* ディレクトリと対応しています。 . アプリは、デバイスの言語と地域の設定に基づいて、正しいロケールを自動的に選択します。 . ", + "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#翻訳の構成" + },"6016": { + "doc": "アプリを翻訳する", + "title": "翻訳ガイドライン", + "content": ". | 「LoRa」「MQTT」「BLE」「TAK」「SNR」「RSSI」などの技術用語は翻訳しないでください。これらは共通です。 | プレースホルダーはそのまま保ちます。 %1$s や %d のような文字列は、実行時に値が埋め込まれます。 自分の言語の文法上必要な場合を除き、削除したり並び替えたりしないでください。 | トーンを合わせます。 アプリは、親しみやすく率直な語り口を使っています。 過度に堅い言葉は避けてください。 | 可能ならテストします。 デバイスの言語を切り替えてアプリを開き、翻訳が実際の文脈でどう見えるか確認してください。 | . ", + "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#翻訳ガイドライン" + },"6017": { + "doc": "アプリを翻訳する", + "title": "質問がありますか？", + "content": "特定の文字列のコンテキストについて質問がある場合や、始め方について助けが必要な場合は、Meshtastic GitHub Discussions のページでディスカッションを作成してください。 . 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#質問がありますか" },"6018": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html", + "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html", - "relUrl": "/cs-rCZ/user/translate.html" + "relUrl": "/hu-rHU/user/translate.html" },"6019": { "doc": "Translate the App", "title": "What Gets Translated", - "content": "| Resource | Source Location | Poznámka | . | 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/ | App Store listing title, description, and changelogs | . ⚠️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#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/ | App Store 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": "/cs-rCZ/user/translate.html#what-gets-translated" + "relUrl": "/hu-rHU/user/translate.html#what-gets-translated" },"6020": { "doc": "Translate the App", - "title": "Jak přispět", + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#jak-p%C5%99isp%C4%9Bt", + "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#how-to-contribute", - "relUrl": "/cs-rCZ/user/translate.html#jak-přispět" + "relUrl": "/hu-rHU/user/translate.html#how-to-contribute" },"6021": { "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/cs-rCZ/user/translate.html#adding-a-new-language", + "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#adding-a-new-language", - "relUrl": "/cs-rCZ/user/translate.html#adding-a-new-language" + "relUrl": "/hu-rHU/user/translate.html#adding-a-new-language" },"6022": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#how-translations-are-organized", + "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#how-translations-are-organized", - "relUrl": "/cs-rCZ/user/translate.html#how-translations-are-organized" + "relUrl": "/hu-rHU/user/translate.html#how-translations-are-organized" },"6023": { "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 device language and open the app to see how translations look in context. | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#translation-guidelines", + "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#translation-guidelines", - "relUrl": "/cs-rCZ/user/translate.html#translation-guidelines" + "relUrl": "/hu-rHU/user/translate.html#translation-guidelines" },"6024": { "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. Děkujeme, že jste pomohli rozšířit dosah Meshtastic! . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#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": "/cs-rCZ/user/translate.html#questions" + "relUrl": "/hu-rHU/user/translate.html#questions" },"6025": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html", - "relUrl": "/fr-rFR/user/translate.html" + "relUrl": "/ht-rHT/user/translate.html" },"6026": { "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/ | App Store 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#what-gets-translated", + "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#what-gets-translated", - "relUrl": "/fr-rFR/user/translate.html#what-gets-translated" + "relUrl": "/ht-rHT/user/translate.html#what-gets-translated" },"6027": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#how-to-contribute", + "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#how-to-contribute", - "relUrl": "/fr-rFR/user/translate.html#how-to-contribute" + "relUrl": "/ht-rHT/user/translate.html#how-to-contribute" },"6028": { "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/fr-rFR/user/translate.html#adding-a-new-language", + "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#adding-a-new-language", - "relUrl": "/fr-rFR/user/translate.html#adding-a-new-language" + "relUrl": "/ht-rHT/user/translate.html#adding-a-new-language" },"6029": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#how-translations-are-organized", + "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#how-translations-are-organized", - "relUrl": "/fr-rFR/user/translate.html#how-translations-are-organized" + "relUrl": "/ht-rHT/user/translate.html#how-translations-are-organized" },"6030": { "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 device language and open the app to see how translations look in context. | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#translation-guidelines", + "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#translation-guidelines", - "relUrl": "/fr-rFR/user/translate.html#translation-guidelines" + "relUrl": "/ht-rHT/user/translate.html#translation-guidelines" },"6031": { "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/fr-rFR/user/translate.html#questions", + "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#questions", - "relUrl": "/fr-rFR/user/translate.html#questions" + "relUrl": "/ht-rHT/user/translate.html#questions" },"6032": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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", + "url": "/Meshtastic-Android/main/gl-rES/user/translate.html", - "relUrl": "/zh-rCN/user/translate.html" + "relUrl": "/gl-rES/user/translate.html" },"6033": { "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/ | App Store 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", + "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/ | App Store 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": "/zh-rCN/user/translate.html#what-gets-translated" + "relUrl": "/gl-rES/user/translate.html#what-gets-translated" },"6034": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#how-to-contribute", + "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#how-to-contribute", - "relUrl": "/zh-rCN/user/translate.html#how-to-contribute" + "relUrl": "/gl-rES/user/translate.html#how-to-contribute" },"6035": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#adding-a-new-language", - "relUrl": "/zh-rCN/user/translate.html#adding-a-new-language" + "relUrl": "/gl-rES/user/translate.html#adding-a-new-language" },"6036": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#how-translations-are-organized", + "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#how-translations-are-organized", - "relUrl": "/zh-rCN/user/translate.html#how-translations-are-organized" + "relUrl": "/gl-rES/user/translate.html#how-translations-are-organized" },"6037": { "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 device language and open the app to see how translations look in context. | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#translation-guidelines", + "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#translation-guidelines", - "relUrl": "/zh-rCN/user/translate.html#translation-guidelines" + "relUrl": "/gl-rES/user/translate.html#translation-guidelines" },"6038": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#questions", - "relUrl": "/zh-rCN/user/translate.html#questions" + "relUrl": "/gl-rES/user/translate.html#questions" },"6039": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html", - "relUrl": "/srp/user/translate.html" + "relUrl": "/tr-rTR/user/translate.html" },"6040": { "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/ | App Store 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", + "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/ | App Store 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": "/srp/user/translate.html#what-gets-translated" + "relUrl": "/tr-rTR/user/translate.html#what-gets-translated" },"6041": { "doc": "Translate the App", - "title": "How to Contribute", + "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/srp/user/translate.html#how-to-contribute", + "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#nas%C4%B1l-katk%C4%B1da-bulunulur", - "relUrl": "/srp/user/translate.html#how-to-contribute" + "relUrl": "/tr-rTR/user/translate.html#nasıl-katkıda-bulunulur" },"6042": { "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#adding-a-new-language", - "relUrl": "/srp/user/translate.html#adding-a-new-language" + "relUrl": "/tr-rTR/user/translate.html#adding-a-new-language" },"6043": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/srp/user/translate.html#how-translations-are-organized", + "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#how-translations-are-organized", - "relUrl": "/srp/user/translate.html#how-translations-are-organized" + "relUrl": "/tr-rTR/user/translate.html#how-translations-are-organized" },"6044": { "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 device language and open the app to see how translations look in context. | . ", - "url": "/Meshtastic-Android/main/srp/user/translate.html#translation-guidelines", + "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#translation-guidelines", - "relUrl": "/srp/user/translate.html#translation-guidelines" + "relUrl": "/tr-rTR/user/translate.html#translation-guidelines" },"6045": { "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", + "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. Meshtastic’in erişimini genişletmemize yardımcı olduğunuz için teşekkür ederiz! . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#questions", - "relUrl": "/srp/user/translate.html#questions" + "relUrl": "/tr-rTR/user/translate.html#questions" },"6046": { "doc": "Translate the App", "title": "Translate the App", "content": "Contributing translations helps make Meshtastic accessible to a wider audience. 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", + "url": "/Meshtastic-Android/main/es-rES/user/translate.html", - "relUrl": "/sq-rAL/user/translate.html" + "relUrl": "/es-rES/user/translate.html" },"6047": { "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/ | App Store 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", + "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/ | App Store 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": "/sq-rAL/user/translate.html#what-gets-translated" + "relUrl": "/es-rES/user/translate.html#what-gets-translated" },"6048": { "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. | Submit. Approved translations are automatically merged into the next release. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#how-to-contribute", + "url": "/Meshtastic-Android/main/es-rES/user/translate.html#how-to-contribute", - "relUrl": "/sq-rAL/user/translate.html#how-to-contribute" + "relUrl": "/es-rES/user/translate.html#how-to-contribute" },"6049": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/translate.html#adding-a-new-language", - "relUrl": "/sq-rAL/user/translate.html#adding-a-new-language" + "relUrl": "/es-rES/user/translate.html#adding-a-new-language" },"6050": { "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) │ └── ... └── ... Locale folders use the Android resource convention {lang}-r{REGION} (e.g. fr-rFR, de-rDE, ja-rJP), matching the values-* directories used for app strings. The app automatically selects the correct locale based on your device’s Language & Region settings. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#how-translations-are-organized", + "url": "/Meshtastic-Android/main/es-rES/user/translate.html#how-translations-are-organized", - "relUrl": "/sq-rAL/user/translate.html#how-translations-are-organized" + "relUrl": "/es-rES/user/translate.html#how-translations-are-organized" },"6051": { "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 device language and open the app to see how translations look in context. | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#translation-guidelines", + "url": "/Meshtastic-Android/main/es-rES/user/translate.html#translation-guidelines", - "relUrl": "/sq-rAL/user/translate.html#translation-guidelines" + "relUrl": "/es-rES/user/translate.html#translation-guidelines" },"6052": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/translate.html#questions", - "relUrl": "/sq-rAL/user/translate.html#questions" + "relUrl": "/es-rES/user/translate.html#questions" },"6053": { "doc": "Transport", "title": "Transport", @@ -42426,3337 +42426,3337 @@ "relUrl": "/en/developer/transport.html#adding-a-new-transport" },"6061": { - "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 — no settings to change inside the app. ", - "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" - },"6062": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6063": { - "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. ", - "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#temperature", - - "relUrl": "/is-rIS/user/units-and-locale.html#temperature" - },"6064": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#distance--altitude", - - "relUrl": "/is-rIS/user/units-and-locale.html#distance--altitude" - },"6065": { - "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" - },"6066": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#wind", - - "relUrl": "/is-rIS/user/units-and-locale.html#wind" - },"6067": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#rainfall", - - "relUrl": "/is-rIS/user/units-and-locale.html#rainfall" - },"6068": { - "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/hr | 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" - },"6069": { - "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 localised 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" - },"6070": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/is-rIS/user/units-and-locale.html#changing-your-measurement-system-android" - },"6071": { - "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 | . ", - "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#related-topics", - - "relUrl": "/is-rIS/user/units-and-locale.html#related-topics" - },"6072": { - "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" - },"6073": { - "doc": "単位・計測・ロケール", - "title": "単位・計測・ロケール", - "content": "Meshtastic アプリは、温度・距離・速度・時刻を、デバイスで設定されている単位で自動的に表示します。アプリ内で変更する設定はありません。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html", - - "relUrl": "/ja-rJP/user/units-and-locale.html" - },"6074": { - "doc": "単位・計測・ロケール", - "title": "仕組み", - "content": "Meshtastic の無線機は、常にメートル法の単位（メートル、°C、m/s、hPa など）でデータを送信します。 アプリはこのデータを受信すると、デバイスのロケールで指定された単位系に変換して値を表示します。 . Android では、計測の設定はシステムの言語と地域の設定によって決まります。 デスクトップ（JVM）では、アプリは JVM のデフォルトの Locale を使用します。 . 💡 ヒント： アプリ内で単位を切り替える必要はまったくありません。 システムの計測設定を変更すると、Meshtastic のすべての画面（ノードの詳細、テレメトリのグラフ、天気、標高など）が自動的に更新されます。 . ", - "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#仕組み" - },"6075": { - "doc": "単位・計測・ロケール", - "title": "温度", - "content": "環境センサーの温度値は °C で送信され、デバイスの温度単位の設定に基づいて表示されます。 . | あなたの設定 | 表示 | . | 摂氏 | 22°C | . | 華氏 | 72°F | . これは、アプリ全体のすべての温度表示に影響します：ノードの環境テレメトリ、土壌温度、露点、テレメトリグラフの軸。 . ", - "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#温度" - },"6076": { - "doc": "単位・計測・ロケール", - "title": "距離と標高", - "content": "ノード間の距離と GPS の標高はメートルで送信され、自動的にスケーリングされて変換されます。 . | あなたの設定 | 短い距離 | 長い距離 | 標高 | . | メートル法 | 350 m | 2.5 km | 1,200 m | . | ヤード・ポンド法（米国） | 1,148 ft | 1.6 mi | 3,937 ft | . アプリは自然なスケーリングを使用します。短い距離はメートルやフィートのままで、長い距離は自動的にキロメートルやマイルに切り替わります。 . 表示される場所 . | ノードリスト：各ノードまでの距離と方位 | ノードの詳細：標高、自分の位置からの距離 | マップ：ウェイポイントまでの距離、ルート追跡のホップ距離 | コンパス：選択したノードまでの距離 | . ", - "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#距離と標高" - },"6077": { - "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#速度" - },"6078": { - "doc": "単位・計測・ロケール", - "title": "風力", - "content": "環境センサーの風速と突風のデータは m/s で送信され、表示用に変換されます。 . | あなたの設定 | 表示 | . | メートル法 | 5 m/s | . | ヤード・ポンド法（米国） | 11 mph | . 風の測定値は、「ノードの詳細」の環境セクションと「環境テレメトリ」のグラフに表示されます。 . ", - "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#風力" - },"6079": { - "doc": "単位・計測・ロケール", - "title": "降水量", - "content": "降水量の測定値（1 時間および 24 時間の合計）は mm で送信され、表示用に変換されます。 . | あなたの設定 | 表示 | . | メートル法 | 12 mm | . | ヤード・ポンド法（米国） | 0.5 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#降水量" - },"6080": { - "doc": "単位・計測・ロケール", - "title": "変わらない単位", - "content": "一部の単位は国際標準であり、ロケールに関係なく同じように表示されます： . | 計測項目 | 単位 | 理由 | . | 大気圧 | hPa | 国際的な気象標準 | . | 方位／進行方向 | °（度） | 普遍的な航法の慣例 | . | 放射線 | μR/hr | 標準的な線量測定の単位 | . | 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#変わらない単位" - },"6081": { - "doc": "単位・計測・ロケール", - "title": "日付と時刻", - "content": "アプリ全体のすべてのタイムスタンプ（最後の通信、メッセージの時刻、テレメトリのログ、グラフの軸）は、デバイスの日付と時刻の設定に従います。 . | 設定 | 制御する内容 | 例 | . | 24 時間表示 | 時刻の形式 | 14:30 vs 2:30 PM | . | 日付形式 | 日付の並び順 | 09/05/2026 vs 05/09/2026 | . アプリは、意味がある場面では相対時間も使用します。たとえばノードリストの「5 分前」や「2 時間前」で、これらはデバイスの言語に自動的にローカライズされます。 . ", - "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#日付と時刻" - },"6082": { - "doc": "単位・計測・ロケール", - "title": "計測系を変更する（Android）", - "content": "Android では、計測系（メートル法かヤード・ポンド法か）は地域設定に連動しています： . | 「Android の設定 → システム → 言語と地域」を開きます | 「地域」または「計測単位」の設定を変更します | Meshtastic に戻ります。値がすぐに更新されます | . 💡 ヒント： すべての計測値の書式は一元的に処理され、プラットフォームのロケールに従うため、単位はアプリ全体で一貫しています。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E8%A8%88%E6%B8%AC%E7%B3%BB%E3%82%92%E5%A4%89%E6%9B%B4%E3%81%99%E3%82%8Bandroid", - - "relUrl": "/ja-rJP/user/units-and-locale.html#計測系を変更するandroid" - },"6083": { - "doc": "単位・計測・ロケール", - "title": "関連トピック", - "content": ". | ノードメトリクス：温度・距離・センサー値が表示される場所 | テレメトリとセンサー：これらの計測値を生成するセンサー | 計測と書式：書式ユーティリティの開発者向けリファレンス | 設定：無線機とユーザー：単位の選択を決める地域設定 | . ", - "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#関連トピック" - },"6084": { - "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 — no settings to change inside the app. ", - "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" - },"6085": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6086": { - "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. ", - "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#temperature", - - "relUrl": "/ca-rES/user/units-and-locale.html#temperature" - },"6087": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#distance--altitude", - - "relUrl": "/ca-rES/user/units-and-locale.html#distance--altitude" - },"6088": { - "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" - },"6089": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#wind", - - "relUrl": "/ca-rES/user/units-and-locale.html#wind" - },"6090": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#rainfall", - - "relUrl": "/ca-rES/user/units-and-locale.html#rainfall" - },"6091": { - "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/hr | 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" - },"6092": { - "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 localised 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" - },"6093": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/ca-rES/user/units-and-locale.html#changing-your-measurement-system-android" - },"6094": { - "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 | . ", - "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#related-topics", - - "relUrl": "/ca-rES/user/units-and-locale.html#related-topics" - },"6095": { - "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" - },"6096": { - "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 — no settings to change inside the app. ", - "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" - },"6097": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6098": { - "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. ", - "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#температура" - },"6099": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#distance--altitude", - - "relUrl": "/sr-rLatn/user/units-and-locale.html#distance--altitude" - },"6100": { - "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#брзина" - },"6101": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Метрика | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#wind", - - "relUrl": "/sr-rLatn/user/units-and-locale.html#wind" - },"6102": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#rainfall", - - "relUrl": "/sr-rLatn/user/units-and-locale.html#rainfall" - },"6103": { - "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/hr | 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" - },"6104": { - "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 localised 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" - },"6105": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/sr-rLatn/user/units-and-locale.html#changing-your-measurement-system-android" - },"6106": { - "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 | . ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#related-topics", - - "relUrl": "/sr-rLatn/user/units-and-locale.html#related-topics" - },"6107": { - "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" - },"6108": { - "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 — no settings to change inside the app. ", - "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" - },"6109": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6110": { - "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. ", - "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#온도" - },"6111": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#distance--altitude", - - "relUrl": "/ko-rKR/user/units-and-locale.html#distance--altitude" - },"6112": { - "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" - },"6113": { - "doc": "Units, Measurement & Locale", - "title": "바람", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "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#바람" - },"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 | . | Metric | 12 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#rainfall", - - "relUrl": "/ko-rKR/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/hr | 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" - },"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 localised 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" - },"6117": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/ko-rKR/user/units-and-locale.html#changing-your-measurement-system-android" - },"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 | . ", - "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#related-topics", - - "relUrl": "/ko-rKR/user/units-and-locale.html#related-topics" - },"6119": { - "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" - },"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 — no settings to change inside the app. ", - "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" - },"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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6122": { - "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. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#temperature", - - "relUrl": "/ro-rRO/user/units-and-locale.html#temperature" - },"6123": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#distance--altitude", - - "relUrl": "/ro-rRO/user/units-and-locale.html#distance--altitude" - },"6124": { - "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" - },"6125": { - "doc": "Units, Measurement & Locale", - "title": "Vânt", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#v%C3%A2nt", - - "relUrl": "/ro-rRO/user/units-and-locale.html#vânt" - },"6126": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#rainfall", - - "relUrl": "/ro-rRO/user/units-and-locale.html#rainfall" - },"6127": { - "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/hr | 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" - },"6128": { - "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 localised 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" - },"6129": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/ro-rRO/user/units-and-locale.html#changing-your-measurement-system-android" - },"6130": { - "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 | . ", - "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#related-topics", - - "relUrl": "/ro-rRO/user/units-and-locale.html#related-topics" - },"6131": { - "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" - },"6132": { - "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 — no settings to change inside the app. ", - "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" - },"6133": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6134": { - "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. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#teocht", - - "relUrl": "/ga-rIE/user/units-and-locale.html#teocht" - },"6135": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#distance--altitude", - - "relUrl": "/ga-rIE/user/units-and-locale.html#distance--altitude" - },"6136": { - "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" - },"6137": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#wind", - - "relUrl": "/ga-rIE/user/units-and-locale.html#wind" - },"6138": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#rainfall", - - "relUrl": "/ga-rIE/user/units-and-locale.html#rainfall" - },"6139": { - "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/hr | 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" - },"6140": { - "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 localised 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" - },"6141": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/ga-rIE/user/units-and-locale.html#changing-your-measurement-system-android" - },"6142": { - "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 | . ", - "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#related-topics", - - "relUrl": "/ga-rIE/user/units-and-locale.html#related-topics" - },"6143": { - "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" - },"6144": { - "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 — no settings to change inside the app. ", - "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" - },"6145": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6146": { - "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. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#temperature", - - "relUrl": "/iw-rIL/user/units-and-locale.html#temperature" - },"6147": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#distance--altitude", - - "relUrl": "/iw-rIL/user/units-and-locale.html#distance--altitude" - },"6148": { - "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" - },"6149": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#wind", - - "relUrl": "/iw-rIL/user/units-and-locale.html#wind" - },"6150": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#rainfall", - - "relUrl": "/iw-rIL/user/units-and-locale.html#rainfall" - },"6151": { - "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/hr | 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" - },"6152": { - "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 localised 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" - },"6153": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/iw-rIL/user/units-and-locale.html#changing-your-measurement-system-android" - },"6154": { - "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 | . ", - "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#related-topics", - - "relUrl": "/iw-rIL/user/units-and-locale.html#related-topics" - },"6155": { - "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" - },"6156": { - "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 — no settings to change inside the app. ", - "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" - },"6157": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6158": { - "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. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#temperatur", - - "relUrl": "/sv-rSE/user/units-and-locale.html#temperatur" - },"6159": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#distance--altitude", - - "relUrl": "/sv-rSE/user/units-and-locale.html#distance--altitude" - },"6160": { - "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" - },"6161": { - "doc": "Units, Measurement & Locale", - "title": "Vind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#vind", - - "relUrl": "/sv-rSE/user/units-and-locale.html#vind" - },"6162": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#rainfall", - - "relUrl": "/sv-rSE/user/units-and-locale.html#rainfall" - },"6163": { - "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/hr | 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" - },"6164": { - "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 localised 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" - },"6165": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/sv-rSE/user/units-and-locale.html#changing-your-measurement-system-android" - },"6166": { - "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 | . ", - "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#related-topics", - - "relUrl": "/sv-rSE/user/units-and-locale.html#related-topics" - },"6167": { - "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" - },"6168": { - "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 — no settings to change inside the app. ", - "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" - },"6169": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6170": { - "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. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#tanperati", - - "relUrl": "/ht-rHT/user/units-and-locale.html#tanperati" - },"6171": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#distance--altitude", - - "relUrl": "/ht-rHT/user/units-and-locale.html#distance--altitude" - },"6172": { - "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" - },"6173": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#wind", - - "relUrl": "/ht-rHT/user/units-and-locale.html#wind" - },"6174": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#rainfall", - - "relUrl": "/ht-rHT/user/units-and-locale.html#rainfall" - },"6175": { - "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/hr | 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" - },"6176": { - "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 localised 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" - },"6177": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/ht-rHT/user/units-and-locale.html#changing-your-measurement-system-android" - },"6178": { - "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 | . ", - "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#related-topics", - - "relUrl": "/ht-rHT/user/units-and-locale.html#related-topics" - },"6179": { - "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" - },"6180": { - "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset", - "title": "Yksiköt, mittaus ja kieli- ja alueasetukset", - "content": "Meshtastic-sovellus näyttää automaattisesti lämpötilat, etäisyydet, nopeudet ja ajat niissä yksiköissä, jotka laitteesi on asetettu käyttämään — asetuksia ei tarvitse muuttaa sovelluksessa. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html", - - "relUrl": "/fi-rFI/user/units-and-locale.html" - },"6181": { - "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset", - "title": "Miten 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. 💡 Vinkki: Mittayksiköitä ei tarvitse koskaan vaihtaa sovelluksen sisältä. Muuta järjestelmäsi mittayksikköasetuksia, niin kaikki Meshtasticin näkymät päivittyvät automaattisesti — radion tiedot, telemetriakaaviot, sää, korkeus ja paljon muuta. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#miten-se-toimii", - - "relUrl": "/fi-rFI/user/units-and-locale.html#miten-se-toimii" - },"6182": { - "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. ", - "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" - },"6183": { - "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 | . Sovellus käyttää luonnollista skaalausta — lyhyet etäisyydet pysyvät metreissä tai jaloissa, kun taas pidemmät etäisyydet vaihtuvat automaattisesti kilometreihin tai maileihin. 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" - },"6184": { - "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" - },"6185": { - "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset", - "title": "Tuuli", - "content": "Tuulen nopeus- ja puuskadata ympäristösensoreista lähetetään muodossa m/s ja muunnetaan näyttöä varten. | Asetuksesi | Näet | . | Metrijärjestelmä | 5 m/s | . | Imperiaalinen (US) | 11 mph | . Tuulimittaukset näkyvät Radion tiedot -näkymän ympäristöosiossa sekä Ympäristötelemetria -kaavioissa. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#tuuli", - - "relUrl": "/fi-rFI/user/units-and-locale.html#tuuli" - },"6186": { - "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 mm | . | Imperiaalinen (US) | 0.5 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ä" - },"6187": { - "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/hr | 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" - },"6188": { - "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 | . Sovellus käyttää myös suhteellista aikaa silloin kun se on järkevää — esimerkiksi “5 min sitten” tai “2 tuntia sitten” radiolistassa — ja tämä mukautuu automaattisesti laitteesi kieleen. ", - "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" - },"6189": { - "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset", - "title": "Mittausjärjestelmän vaihtaminen (Android)", - "content": "Androidissa mittausjärjestelmäsi (metrinen vs imperial) on sidottu alueasetuksiin: . | Avaa Asetukset → Järjestelmä → Kieli ja alue | Vaihda Alue- tai Mittausyksiköt-asetusta | Palaa Meshtasticiin — arvot päivittyvät välittömästi | . 💡 Vinkki: Kaikki mittausten muotoilut tehdään keskitetysti ja ne noudattavat käyttöympäristösi alueasetuksia, joten yksiköt pysyvät yhtenäisinä kaikkialla sovelluksessa. ", - "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#mittausj%C3%A4rjestelm%C3%A4n-vaihtaminen-android", - - "relUrl": "/fi-rFI/user/units-and-locale.html#mittausjärjestelmän-vaihtaminen-android" - },"6190": { - "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 | . ", - "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" - },"6191": { - "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 — no settings to change inside the app. ", - "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" - },"6192": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6193": { - "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. ", - "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#temperature", - - "relUrl": "/gl-rES/user/units-and-locale.html#temperature" - },"6194": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#distance--altitude", - - "relUrl": "/gl-rES/user/units-and-locale.html#distance--altitude" - },"6195": { - "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" - },"6196": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#wind", - - "relUrl": "/gl-rES/user/units-and-locale.html#wind" - },"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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#rainfall", - - "relUrl": "/gl-rES/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/hr | 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" - },"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 localised 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" - },"6200": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/gl-rES/user/units-and-locale.html#changing-your-measurement-system-android" - },"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 | . ", - "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#related-topics", - - "relUrl": "/gl-rES/user/units-and-locale.html#related-topics" - },"6202": { - "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" - },"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 — no settings to change inside the app. ", - "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" - },"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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6205": { - "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. ", - "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#температура" - },"6206": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#distance--altitude", - - "relUrl": "/uk-rUA/user/units-and-locale.html#distance--altitude" - },"6207": { - "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#швидкість" - },"6208": { - "doc": "Units, Measurement & Locale", - "title": "Вітер", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "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#вітер" - },"6209": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#rainfall", - - "relUrl": "/uk-rUA/user/units-and-locale.html#rainfall" - },"6210": { - "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/hr | 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" - },"6211": { - "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 localised 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" - },"6212": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/uk-rUA/user/units-and-locale.html#changing-your-measurement-system-android" - },"6213": { - "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 | . ", - "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#related-topics", - - "relUrl": "/uk-rUA/user/units-and-locale.html#related-topics" - },"6214": { - "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" - },"6215": { "doc": "Units, Measurement & Locale", "title": "Units, Measurement & Locale", "content": "Die Meshtastic-App zeigt Temperaturen, Entfernungen, Geschwindigkeiten und Zeiten automatisch in den Einheiten an, auf die Ihr Gerät konfiguriert ist – es sind keine Einstellungen innerhalb der App zu ändern. ", "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" - },"6216": { + },"6062": { "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#so-funktionierts", "relUrl": "/de-rDE/user/units-and-locale.html#so-funktionierts" - },"6217": { + },"6063": { "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. ", "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#temperatur", "relUrl": "/de-rDE/user/units-and-locale.html#temperatur" - },"6218": { + },"6064": { "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#distance--altitude", "relUrl": "/de-rDE/user/units-and-locale.html#distance--altitude" - },"6219": { + },"6065": { "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" - },"6220": { + },"6066": { "doc": "Units, Measurement & Locale", "title": "Wind", "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metrisch | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#wind", "relUrl": "/de-rDE/user/units-and-locale.html#wind" - },"6221": { + },"6067": { "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 mm | . | Imperial (US) | 0.5 in | . ", "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#rainfall", "relUrl": "/de-rDE/user/units-and-locale.html#rainfall" - },"6222": { + },"6068": { "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/hr | 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" - },"6223": { + },"6069": { "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 | . Die App verwendet zudem relative Zeitangaben, wo dies sinnvoll ist – zum Beispiel „vor 5 Min.“ oder „vor 2 Stunden“ in der Knotenliste –, die automatisch in die Sprache Ihres Geräts lokalisiert werden. ", "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#date--time", "relUrl": "/de-rDE/user/units-and-locale.html#date--time" - },"6224": { + },"6070": { "doc": "Units, Measurement & Locale", "title": "Changing Your Measurement System (Android)", "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#changing-your-measurement-system-android", "relUrl": "/de-rDE/user/units-and-locale.html#changing-your-measurement-system-android" - },"6225": { + },"6071": { "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 | . ", "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#related-topics", "relUrl": "/de-rDE/user/units-and-locale.html#related-topics" - },"6226": { + },"6072": { "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" - },"6227": { + },"6073": { "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 — no settings to change inside the app. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#units-measurement--locale", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#units-measurement--locale", - "relUrl": "/hr-rHR/user/units-and-locale.html#units-measurement--locale" - },"6228": { + "relUrl": "/ca-rES/user/units-and-locale.html#units-measurement--locale" + },"6074": { "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#how-it-works", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#how-it-works", - "relUrl": "/hr-rHR/user/units-and-locale.html#how-it-works" - },"6229": { + "relUrl": "/ca-rES/user/units-and-locale.html#how-it-works" + },"6075": { "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. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#temperature", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#temperature", - "relUrl": "/hr-rHR/user/units-and-locale.html#temperature" - },"6230": { + "relUrl": "/ca-rES/user/units-and-locale.html#temperature" + },"6076": { "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#distance--altitude", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#distance--altitude", - "relUrl": "/hr-rHR/user/units-and-locale.html#distance--altitude" - },"6231": { + "relUrl": "/ca-rES/user/units-and-locale.html#distance--altitude" + },"6077": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#speed", - "relUrl": "/hr-rHR/user/units-and-locale.html#speed" - },"6232": { + "relUrl": "/ca-rES/user/units-and-locale.html#speed" + },"6078": { "doc": "Units, Measurement & Locale", "title": "Wind", "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#wind", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#wind", - "relUrl": "/hr-rHR/user/units-and-locale.html#wind" - },"6233": { + "relUrl": "/ca-rES/user/units-and-locale.html#wind" + },"6079": { "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#rainfall", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#rainfall", - "relUrl": "/hr-rHR/user/units-and-locale.html#rainfall" - },"6234": { + "relUrl": "/ca-rES/user/units-and-locale.html#rainfall" + },"6080": { "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/hr | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#units-that-never-change", - "relUrl": "/hr-rHR/user/units-and-locale.html#units-that-never-change" - },"6235": { + "relUrl": "/ca-rES/user/units-and-locale.html#units-that-never-change" + },"6081": { "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 localised into your device language. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#date--time", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#date--time", - "relUrl": "/hr-rHR/user/units-and-locale.html#date--time" - },"6236": { + "relUrl": "/ca-rES/user/units-and-locale.html#date--time" + },"6082": { "doc": "Units, Measurement & Locale", "title": "Changing Your Measurement System (Android)", "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#changing-your-measurement-system-android", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#changing-your-measurement-system-android", - "relUrl": "/hr-rHR/user/units-and-locale.html#changing-your-measurement-system-android" - },"6237": { + "relUrl": "/ca-rES/user/units-and-locale.html#changing-your-measurement-system-android" + },"6083": { "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 | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#related-topics", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#related-topics", - "relUrl": "/hr-rHR/user/units-and-locale.html#related-topics" - },"6238": { + "relUrl": "/ca-rES/user/units-and-locale.html#related-topics" + },"6084": { "doc": "Units, Measurement & Locale", "title": "Units, Measurement & Locale", "content": " ", - "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html", + "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html", - "relUrl": "/hr-rHR/user/units-and-locale.html" - },"6239": { - "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 — no settings to change inside the app. ", - "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" - },"6240": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6241": { - "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. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#temperat%C5%ABra", - - "relUrl": "/lt-rLT/user/units-and-locale.html#temperatūra" - },"6242": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#distance--altitude", - - "relUrl": "/lt-rLT/user/units-and-locale.html#distance--altitude" - },"6243": { - "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" - },"6244": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#wind", - - "relUrl": "/lt-rLT/user/units-and-locale.html#wind" - },"6245": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#rainfall", - - "relUrl": "/lt-rLT/user/units-and-locale.html#rainfall" - },"6246": { - "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/hr | 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" - },"6247": { - "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 localised 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" - },"6248": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/lt-rLT/user/units-and-locale.html#changing-your-measurement-system-android" - },"6249": { - "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 | . ", - "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#related-topics", - - "relUrl": "/lt-rLT/user/units-and-locale.html#related-topics" - },"6250": { - "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" - },"6251": { - "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 — no settings to change inside the app. ", - "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#units-measurement--locale", - - "relUrl": "/en/user/units-and-locale.html#units-measurement--locale" - },"6252": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#how-it-works", - - "relUrl": "/en/user/units-and-locale.html#how-it-works" - },"6253": { - "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. ", - "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#temperature", - - "relUrl": "/en/user/units-and-locale.html#temperature" - },"6254": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#distance--altitude", - - "relUrl": "/en/user/units-and-locale.html#distance--altitude" - },"6255": { - "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" - },"6256": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#wind", - - "relUrl": "/en/user/units-and-locale.html#wind" - },"6257": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#rainfall", - - "relUrl": "/en/user/units-and-locale.html#rainfall" - },"6258": { - "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/hr | 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" - },"6259": { - "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 localised 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" - },"6260": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/en/user/units-and-locale.html#changing-your-measurement-system-android" - },"6261": { - "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 | . ", - "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#related-topics", - - "relUrl": "/en/user/units-and-locale.html#related-topics" - },"6262": { - "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" - },"6263": { - "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 — no settings to change inside the app. ", - "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" - },"6264": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6265": { - "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. ", - "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" - },"6266": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#distance--altitude", - - "relUrl": "/hu-rHU/user/units-and-locale.html#distance--altitude" - },"6267": { - "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" - },"6268": { - "doc": "Units, Measurement & Locale", - "title": "Szél", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#sz%C3%A9l", - - "relUrl": "/hu-rHU/user/units-and-locale.html#szél" - },"6269": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#rainfall", - - "relUrl": "/hu-rHU/user/units-and-locale.html#rainfall" - },"6270": { - "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/hr | 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" - },"6271": { - "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 localised 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" - },"6272": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/hu-rHU/user/units-and-locale.html#changing-your-measurement-system-android" - },"6273": { - "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 | . ", - "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#related-topics", - - "relUrl": "/hu-rHU/user/units-and-locale.html#related-topics" - },"6274": { - "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" - },"6275": { - "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 — no settings to change inside the app. ", - "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" - },"6276": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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#как-работи" - },"6277": { - "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. ", - "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#температура" - },"6278": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#distance--altitude", - - "relUrl": "/bg-rBG/user/units-and-locale.html#distance--altitude" - },"6279": { - "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#скорост" - },"6280": { - "doc": "Units, Measurement & Locale", - "title": "Вятър", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Метрични | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "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#вятър" - },"6281": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#rainfall", - - "relUrl": "/bg-rBG/user/units-and-locale.html#rainfall" - },"6282": { - "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/hr | 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" - },"6283": { - "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 localised 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" - },"6284": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/bg-rBG/user/units-and-locale.html#changing-your-measurement-system-android" - },"6285": { - "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 | . ", - "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#related-topics", - - "relUrl": "/bg-rBG/user/units-and-locale.html#related-topics" - },"6286": { - "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" - },"6287": { - "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 — no settings to change inside the app. ", - "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" - },"6288": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6289": { - "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. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#temperatura", - - "relUrl": "/sl-rSI/user/units-and-locale.html#temperatura" - },"6290": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#distance--altitude", - - "relUrl": "/sl-rSI/user/units-and-locale.html#distance--altitude" - },"6291": { - "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" - },"6292": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#wind", - - "relUrl": "/sl-rSI/user/units-and-locale.html#wind" - },"6293": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#rainfall", - - "relUrl": "/sl-rSI/user/units-and-locale.html#rainfall" - },"6294": { - "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/hr | 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" - },"6295": { - "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 localised 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" - },"6296": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/sl-rSI/user/units-and-locale.html#changing-your-measurement-system-android" - },"6297": { - "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 | . ", - "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#related-topics", - - "relUrl": "/sl-rSI/user/units-and-locale.html#related-topics" - },"6298": { - "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" - },"6299": { - "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 — no settings to change inside the app. ", - "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" - },"6300": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6301": { - "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. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#temperatura", - - "relUrl": "/pt-rPT/user/units-and-locale.html#temperatura" - },"6302": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#distance--altitude", - - "relUrl": "/pt-rPT/user/units-and-locale.html#distance--altitude" - },"6303": { - "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" - },"6304": { - "doc": "Units, Measurement & Locale", - "title": "Vento", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#vento", - - "relUrl": "/pt-rPT/user/units-and-locale.html#vento" - },"6305": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#rainfall", - - "relUrl": "/pt-rPT/user/units-and-locale.html#rainfall" - },"6306": { - "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/hr | 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" - },"6307": { - "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 localised 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" - },"6308": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/pt-rPT/user/units-and-locale.html#changing-your-measurement-system-android" - },"6309": { - "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 | . ", - "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#related-topics", - - "relUrl": "/pt-rPT/user/units-and-locale.html#related-topics" - },"6310": { - "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" - },"6311": { + "relUrl": "/ca-rES/user/units-and-locale.html" + },"6085": { "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 — no settings to change inside the app. ", "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" - },"6312": { + },"6086": { "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", "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" - },"6313": { + },"6087": { "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. ", "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#тэмпература" - },"6314": { + },"6088": { "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#distance--altitude", "relUrl": "/be-rBY/user/units-and-locale.html#distance--altitude" - },"6315": { + },"6089": { "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#хуткасць" - },"6316": { + },"6090": { "doc": "Units, Measurement & Locale", "title": "Wind", "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#wind", "relUrl": "/be-rBY/user/units-and-locale.html#wind" - },"6317": { + },"6091": { "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 mm | . | Imperial (US) | 0.5 in | . ", "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#rainfall", "relUrl": "/be-rBY/user/units-and-locale.html#rainfall" - },"6318": { + },"6092": { "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/hr | 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" - },"6319": { + },"6093": { "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 localised 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" - },"6320": { + },"6094": { "doc": "Units, Measurement & Locale", "title": "Changing Your Measurement System (Android)", "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#changing-your-measurement-system-android", "relUrl": "/be-rBY/user/units-and-locale.html#changing-your-measurement-system-android" - },"6321": { + },"6095": { "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 | . ", "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#related-topics", "relUrl": "/be-rBY/user/units-and-locale.html#related-topics" - },"6322": { + },"6096": { "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" - },"6323": { + },"6097": { "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 — no settings to change inside the app. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#units-measurement--locale", + "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#units-measurement--locale", - "relUrl": "/pt-rBR/user/units-and-locale.html#units-measurement--locale" - },"6324": { + "relUrl": "/uk-rUA/user/units-and-locale.html#units-measurement--locale" + },"6098": { "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#how-it-works", + "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#how-it-works", - "relUrl": "/pt-rBR/user/units-and-locale.html#how-it-works" - },"6325": { + "relUrl": "/uk-rUA/user/units-and-locale.html#how-it-works" + },"6099": { "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. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#temperatura", - - "relUrl": "/pt-rBR/user/units-and-locale.html#temperatura" - },"6326": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#distance--altitude", - - "relUrl": "/pt-rBR/user/units-and-locale.html#distance--altitude" - },"6327": { - "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" - },"6328": { - "doc": "Units, Measurement & Locale", - "title": "Vento", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#vento", - - "relUrl": "/pt-rBR/user/units-and-locale.html#vento" - },"6329": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#rainfall", - - "relUrl": "/pt-rBR/user/units-and-locale.html#rainfall" - },"6330": { - "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/hr | 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" - },"6331": { - "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 localised 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" - },"6332": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/pt-rBR/user/units-and-locale.html#changing-your-measurement-system-android" - },"6333": { - "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 | . ", - "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#related-topics", - - "relUrl": "/pt-rBR/user/units-and-locale.html#related-topics" - },"6334": { - "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" - },"6335": { - "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 — no settings to change inside the app. ", - "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" - },"6336": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6337": { - "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. ", - "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#θερμοκρασία" - },"6338": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#distance--altitude", - - "relUrl": "/el-rGR/user/units-and-locale.html#distance--altitude" - },"6339": { - "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" - },"6340": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#wind", - - "relUrl": "/el-rGR/user/units-and-locale.html#wind" - },"6341": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#rainfall", - - "relUrl": "/el-rGR/user/units-and-locale.html#rainfall" - },"6342": { - "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/hr | 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" - },"6343": { - "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 localised 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" - },"6344": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/el-rGR/user/units-and-locale.html#changing-your-measurement-system-android" - },"6345": { - "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 | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#related-topics", - - "relUrl": "/el-rGR/user/units-and-locale.html#related-topics" - },"6346": { - "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" - },"6347": { - "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 — no settings to change inside the app. ", - "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" - },"6348": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6349": { - "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. ", - "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#temperatura", - - "relUrl": "/es-rES/user/units-and-locale.html#temperatura" - },"6350": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#distance--altitude", - - "relUrl": "/es-rES/user/units-and-locale.html#distance--altitude" - },"6351": { - "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" - },"6352": { - "doc": "Units, Measurement & Locale", - "title": "Viento", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Métrico | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#viento", - - "relUrl": "/es-rES/user/units-and-locale.html#viento" - },"6353": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#rainfall", - - "relUrl": "/es-rES/user/units-and-locale.html#rainfall" - },"6354": { - "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/hr | 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" - },"6355": { - "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 localised 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" - },"6356": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/es-rES/user/units-and-locale.html#changing-your-measurement-system-android" - },"6357": { - "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 | . ", - "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#related-topics", - - "relUrl": "/es-rES/user/units-and-locale.html#related-topics" - },"6358": { - "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" - },"6359": { - "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 — no settings to change inside the app. ", - "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" - },"6360": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6361": { - "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. ", - "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" - },"6362": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#distance--altitude", - - "relUrl": "/tr-rTR/user/units-and-locale.html#distance--altitude" - },"6363": { - "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" - },"6364": { - "doc": "Units, Measurement & Locale", - "title": "Rüzgar", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#r%C3%BCzgar", - - "relUrl": "/tr-rTR/user/units-and-locale.html#rüzgar" - },"6365": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#rainfall", - - "relUrl": "/tr-rTR/user/units-and-locale.html#rainfall" - },"6366": { - "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/hr | 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" - },"6367": { - "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 localised 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" - },"6368": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/tr-rTR/user/units-and-locale.html#changing-your-measurement-system-android" - },"6369": { - "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 | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#related-topics", - - "relUrl": "/tr-rTR/user/units-and-locale.html#related-topics" - },"6370": { - "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" - },"6371": { - "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 — no settings to change inside the app. ", - "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" - },"6372": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6373": { - "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. ", - "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#temperatur", - - "relUrl": "/no-rNO/user/units-and-locale.html#temperatur" - },"6374": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#distance--altitude", - - "relUrl": "/no-rNO/user/units-and-locale.html#distance--altitude" - },"6375": { - "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" - },"6376": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#wind", - - "relUrl": "/no-rNO/user/units-and-locale.html#wind" - },"6377": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#rainfall", - - "relUrl": "/no-rNO/user/units-and-locale.html#rainfall" - },"6378": { - "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/hr | 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" - },"6379": { - "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 localised 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" - },"6380": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/no-rNO/user/units-and-locale.html#changing-your-measurement-system-android" - },"6381": { - "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 | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#related-topics", - - "relUrl": "/no-rNO/user/units-and-locale.html#related-topics" - },"6382": { - "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" - },"6383": { - "doc": "Единицы измерения и локаль", - "title": "Единицы измерения и локаль", - "content": "Приложение Meshtastic автоматически отображает температуру, расстояние, скорость и время в единицах, настроенных на вашем устройстве — никаких настроек внутри приложения менять не нужно. ", - "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html", - - "relUrl": "/ru-rRU/user/units-and-locale.html" - },"6384": { - "doc": "Единицы измерения и локаль", - "title": "Как это работает", - "content": "Радиостанции Meshtastic всегда передают данные в метрических единицах (метры, °C, м/с, гПа и т.д.). Когда приложение получает эти данные, оно преобразует их и показывает значения в той системе единиц, которую задает локаль устройства. На Android твои предпочтения единиц измерений определяются настройками системы Язык и регион. На настольном компьютере (JVM) приложение использует стандартную Locale JVM. 💡 Совет: тебе никогда не нужно менять единицы измерения в приложении. Измени настройки единиц измерения в системе, и все экраны в Meshtastic обновятся автоматически — детали ноды, графики телеметрии, погода, высота и многое другое. ", - "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#как-это-работает" - },"6385": { - "doc": "Единицы измерения и локаль", "title": "Температура", - "content": "Значения температуры от датчиков окружающей среды передаются в °C и отображаются в соответствии с предпочтительным единицами температуры твоего устройства. | Твои настройки | Ты видишь | . | Цельсий | 22°C | . | Фаренгейт | 72°F | . Это влияет на все отображения температуры в приложении: телеметрия окружающей среды ноды, температура почвы, точка росы и оси диаграммы телеметрии. ", - "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#температура" - },"6386": { - "doc": "Единицы измерения и локаль", - "title": "Расстояние и высота", - "content": "Расстояния между нодами и высоты GPS передаются в метрах и автоматически масштабируются и преобразуются. | Твои настройки | Небольшое расстояние | Дальнее расстояние | Высота | . | Метрическая | 350 м | 2,5 км | 1200 м | . | Имперская | 1148 фт | 1,6 миль | 3937 фт | . Приложение использует естественное масштабирование — небольшие расстояния остаются в метрах или футах, а более дальние автоматически переключаются на километры или мили. Где они появляются . | Список нод — расстояние и азимут до каждой ноды | Детали ноды — высота, расстояние от твоего положения | Карта — расстояния между путевыми точками, расстояния между хопами трассировки | Компас — расстояние до выбранной ноды | . ", - "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#расстояние-и-высота" - },"6387": { - "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#скорость" - },"6388": { - "doc": "Единицы измерения и локаль", - "title": "Ветер", - "content": "Данные о скорости ветра и порывах с датчиков окружающей среды передаются в м/с и преобразуются для отображения. | Твоя настройка | Ты видишь | . | Метрическая | 5 м/с | . | Имперская (США) | 11 миль/ч | . Показания ветра отображаются в разделе среды Детали ноды и на диаграммах Телеметрия окружающей среды. ", - "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#ветер" - },"6389": { - "doc": "Единицы измерения и локаль", - "title": "Осадки", - "content": "Измерения осадков (за 1 час и за 24 часа) передаются в мм и конвертируются для отображения. | Твоя настройка | Ты видишь | . | Метрическая | 12 мм | . | Имперская (США) | 0,5 дюймов | . ", - "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#осадки" - },"6390": { - "doc": "Единицы измерения и локаль", - "title": "Единицы, которые никогда не меняются", - "content": "Некоторые единицы являются международными стандартами и отображаются одинаково независимо от вашего региона: . | Показатель | Единица | Почему | . | Барометрическое давление | гПа | Международный метеорологический стандарт | . | Курс / азимут | ° (градусы) | Универсальная навигационная конвенция | . | Радиация | мкР/ч | Стандартная единица дозиметрии | . | 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#единицы-которые-никогда-не-меняются" - },"6391": { - "doc": "Единицы измерения и локаль", - "title": "Дата и время", - "content": "Все отметки времени в приложении — последняя активность, время сообщений, журналы телеметрии, оси графиков — следуют настройкам даты и времени вашего устройства. | Настройка | Что это контролирует | Пример | . | 24-часовой формат времени | Формат часов | 14:30 или 2:30 PM | . | Формат даты | Сортировка даты | 09/05/2026 или 05/09/2026 | . Приложение также использует относительное время в списке нод, где это имеет смысл — например, “5 минут назад” или “2 часа назад”, которое автоматически локализуется на язык твоего устройства. ", - "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#дата-и-время" - },"6392": { - "doc": "Единицы измерения и локаль", - "title": "Изменение системы измерений (Android)", - "content": "На Android система измерений (метрическая или имперская) связана с настройкой региона: . | Откройте Настройки Android → Система → Язык и регион | Измените свои предпочтения в Регион или Единицы измерения | Вернуться к Meshtastic — значения обновляются немедленно | . 💡 Совет: Все форматирование производится в централизованном порядке и уважает локаль платформы, поэтому единицы измерения всегда в приложении. ", - "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D0%B8%D0%B7%D0%BC%D0%B5%D0%BD%D0%B5%D0%BD%D0%B8%D0%B5-%D1%81%D0%B8%D1%81%D1%82%D0%B5%D0%BC%D1%8B-%D0%B8%D0%B7%D0%BC%D0%B5%D1%80%D0%B5%D0%BD%D0%B8%D0%B9-android", - - "relUrl": "/ru-rRU/user/units-and-locale.html#изменение-системы-измерений-android" - },"6393": { - "doc": "Единицы измерения и локаль", - "title": "Связанные темы", - "content": ". | Метрики ноды — здесь отображаются температура, расстояние и значения датчиков | Телеметрия и датчики — датчики, производящие эти измерения | Измерение и форматирование — ссылка на разработчика утилит форматирования | Настройки — Радио и Пользователь — настройка региона, управляющая выбором единиц | . ", - "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#связанные-темы" - },"6394": { - "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 — no settings to change inside the app. ", - "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" - },"6395": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6396": { - "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. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#temperatuur", + "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": "/nl-rNL/user/units-and-locale.html#temperatuur" - },"6397": { + "relUrl": "/uk-rUA/user/units-and-locale.html#температура" + },"6100": { "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#distance--altitude", - "relUrl": "/nl-rNL/user/units-and-locale.html#distance--altitude" - },"6398": { + "relUrl": "/uk-rUA/user/units-and-locale.html#distance--altitude" + },"6101": { "doc": "Units, Measurement & Locale", - "title": "Speed", + "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/nl-rNL/user/units-and-locale.html#speed", + "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": "/nl-rNL/user/units-and-locale.html#speed" - },"6399": { + "relUrl": "/uk-rUA/user/units-and-locale.html#швидкість" + },"6102": { "doc": "Units, Measurement & Locale", - "title": "Wind", + "title": "Вітер", "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#wind", + "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#%D0%B2%D1%96%D1%82%D0%B5%D1%80", - "relUrl": "/nl-rNL/user/units-and-locale.html#wind" - },"6400": { + "relUrl": "/uk-rUA/user/units-and-locale.html#вітер" + },"6103": { "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#rainfall", + "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#rainfall", - "relUrl": "/nl-rNL/user/units-and-locale.html#rainfall" - },"6401": { + "relUrl": "/uk-rUA/user/units-and-locale.html#rainfall" + },"6104": { "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/hr | 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", + "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/hr | 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": "/nl-rNL/user/units-and-locale.html#units-that-never-change" - },"6402": { + "relUrl": "/uk-rUA/user/units-and-locale.html#units-that-never-change" + },"6105": { "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 localised into your device language. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#date--time", + "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#date--time", - "relUrl": "/nl-rNL/user/units-and-locale.html#date--time" - },"6403": { + "relUrl": "/uk-rUA/user/units-and-locale.html#date--time" + },"6106": { "doc": "Units, Measurement & Locale", "title": "Changing Your Measurement System (Android)", "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#changing-your-measurement-system-android", + "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#changing-your-measurement-system-android", - "relUrl": "/nl-rNL/user/units-and-locale.html#changing-your-measurement-system-android" - },"6404": { + "relUrl": "/uk-rUA/user/units-and-locale.html#changing-your-measurement-system-android" + },"6107": { "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 | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#related-topics", + "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#related-topics", - "relUrl": "/nl-rNL/user/units-and-locale.html#related-topics" - },"6405": { + "relUrl": "/uk-rUA/user/units-and-locale.html#related-topics" + },"6108": { "doc": "Units, Measurement & Locale", "title": "Units, Measurement & Locale", "content": " ", - "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html", + "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html", - "relUrl": "/nl-rNL/user/units-and-locale.html" - },"6406": { - "doc": "Ühikud, mõõtühikud ja lokaat", - "title": "Ühikud, mõõtühikud ja lokaat", - "content": "Meshtastic rakendus kuvab automaatselt temperatuure, vahemaid, kiirusi ja aegu ühikutes, milleks sinu seade on seadistatud – rakenduses pole vaja sätteid muuta. ", - "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html", - - "relUrl": "/et-rEE/user/units-and-locale.html" - },"6407": { - "doc": "Ühikud, mõõtühikud ja lokaat", - "title": "How It Works", - "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”. 💡 Vihje: Rakenduses pole kunagi vaja ühikuid vahetada. Muuda oma süsteemi mõõtmiste eelistusi ja kõik Meshtasticu ekraanid värskendatakse automaatselt – sõlmede üksikasjad, telemeetriadiagrammid, ilm, kõrgus ja palju muud. ", - "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#how-it-works", - - "relUrl": "/et-rEE/user/units-and-locale.html#how-it-works" - },"6408": { - "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. ", - "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#temperatuur", - - "relUrl": "/et-rEE/user/units-and-locale.html#temperatuur" - },"6409": { - "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 | 1,200 m | . | Imperial (US) | 1,148 ft | 1.6 mi | 3,937 ft | . Rakendus kasutab loomulikku skaleerimist – lühikesed vahemaad jäävad meetritesse või jalgadesse, pikemad vahemaad aga muutuvad automaatselt kilomeetriteks või miilideks. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Kaart — teekonnapunktide vahemaad, traceroute’i hüppevahemaad | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#distance--altitude", - - "relUrl": "/et-rEE/user/units-and-locale.html#distance--altitude" - },"6410": { - "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" - },"6411": { - "doc": "Ühikud, mõõtühikud ja lokaat", - "title": "Tuul", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Sinu sätted | Teadmiseks | . | Meetriline | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#tuul", - - "relUrl": "/et-rEE/user/units-and-locale.html#tuul" - },"6412": { - "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 mm | . | Imperial (US) | 0,5 in | . ", - "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#rainfall", - - "relUrl": "/et-rEE/user/units-and-locale.html#rainfall" - },"6413": { - "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/hr | 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" - },"6414": { - "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-Hour Time | Kella vorming | 14:30 vs 2:30 PM | . | Kuupäeva vorming | Date ordering | 09/05/2026 vs 05/09/2026 | . The app also uses relative time where it makes sense — for example, “5 min ago” or “2 hours ago” in the node list — which is automatically localised into your device language. ", - "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#date--time", - - "relUrl": "/et-rEE/user/units-and-locale.html#date--time" - },"6415": { - "doc": "Ühikud, mõõtühikud ja lokaat", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Ava Androidi seaded → Süsteem → Keel ja piirkond | Change your Region or Measurement units preference | Tagasi Meshtastic juurde — väärtused värskendatakse kohe | . 💡 Vihje: Kogu mõõtühikute vormindamine toimub tsentraalselt ja arvestab platvormi lokaaduga, seega püsivad ühikud kogu rakenduses ühtsed. ", - "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/et-rEE/user/units-and-locale.html#changing-your-measurement-system-android" - },"6416": { - "doc": "Ühikud, mõõtühikud ja lokaat", - "title": "Related Topics", - "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 | . ", - "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#related-topics", - - "relUrl": "/et-rEE/user/units-and-locale.html#related-topics" - },"6417": { - "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 — no settings to change inside the app. ", - "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" - },"6418": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#come-funziona", - - "relUrl": "/it-rIT/user/units-and-locale.html#come-funziona" - },"6419": { - "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. ", - "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#temperatura", - - "relUrl": "/it-rIT/user/units-and-locale.html#temperatura" - },"6420": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#distance--altitude", - - "relUrl": "/it-rIT/user/units-and-locale.html#distance--altitude" - },"6421": { - "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à" - },"6422": { - "doc": "Units, Measurement & Locale", - "title": "Vento", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metrico | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#vento", - - "relUrl": "/it-rIT/user/units-and-locale.html#vento" - },"6423": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#rainfall", - - "relUrl": "/it-rIT/user/units-and-locale.html#rainfall" - },"6424": { - "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/hr | 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" - },"6425": { - "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 localised 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" - },"6426": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/it-rIT/user/units-and-locale.html#changing-your-measurement-system-android" - },"6427": { - "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 | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#related-topics", - - "relUrl": "/it-rIT/user/units-and-locale.html#related-topics" - },"6428": { - "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" - },"6429": { - "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 — no settings to change inside the app. ", - "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" - },"6430": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6431": { - "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. ", - "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#الحرارة" - },"6432": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#distance--altitude", - - "relUrl": "/ar-rSA/user/units-and-locale.html#distance--altitude" - },"6433": { - "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" - },"6434": { - "doc": "Units, Measurement & Locale", - "title": "Wind", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#wind", - - "relUrl": "/ar-rSA/user/units-and-locale.html#wind" - },"6435": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#rainfall", - - "relUrl": "/ar-rSA/user/units-and-locale.html#rainfall" - },"6436": { - "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/hr | 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" - },"6437": { - "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 localised 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" - },"6438": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/ar-rSA/user/units-and-locale.html#changing-your-measurement-system-android" - },"6439": { - "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 | . ", - "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#related-topics", - - "relUrl": "/ar-rSA/user/units-and-locale.html#related-topics" - },"6440": { - "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" - },"6441": { - "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 — no settings to change inside the app. ", - "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" - },"6442": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6443": { - "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. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#teplota", - - "relUrl": "/sk-rSK/user/units-and-locale.html#teplota" - },"6444": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#distance--altitude", - - "relUrl": "/sk-rSK/user/units-and-locale.html#distance--altitude" - },"6445": { - "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ť" - },"6446": { - "doc": "Units, Measurement & Locale", - "title": "Vietor", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#vietor", - - "relUrl": "/sk-rSK/user/units-and-locale.html#vietor" - },"6447": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#rainfall", - - "relUrl": "/sk-rSK/user/units-and-locale.html#rainfall" - },"6448": { - "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/hr | 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" - },"6449": { - "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 localised 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" - },"6450": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/sk-rSK/user/units-and-locale.html#changing-your-measurement-system-android" - },"6451": { - "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 | . ", - "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#related-topics", - - "relUrl": "/sk-rSK/user/units-and-locale.html#related-topics" - },"6452": { - "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" - },"6453": { - "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 — no settings to change inside the app. ", - "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" - },"6454": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6455": { - "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. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#temperatura", - - "relUrl": "/pl-rPL/user/units-and-locale.html#temperatura" - },"6456": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#distance--altitude", - - "relUrl": "/pl-rPL/user/units-and-locale.html#distance--altitude" - },"6457": { - "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ść" - },"6458": { - "doc": "Units, Measurement & Locale", - "title": "Wiatr", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#wiatr", - - "relUrl": "/pl-rPL/user/units-and-locale.html#wiatr" - },"6459": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#rainfall", - - "relUrl": "/pl-rPL/user/units-and-locale.html#rainfall" - },"6460": { - "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/hr | 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" - },"6461": { - "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 localised 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" - },"6462": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/pl-rPL/user/units-and-locale.html#changing-your-measurement-system-android" - },"6463": { - "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 | . ", - "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#related-topics", - - "relUrl": "/pl-rPL/user/units-and-locale.html#related-topics" - },"6464": { - "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" - },"6465": { - "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 — no settings to change inside the app. ", - "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" - },"6466": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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#運作方式" - },"6467": { - "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. ", - "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#溫度" - },"6468": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#distance--altitude", - - "relUrl": "/zh-rTW/user/units-and-locale.html#distance--altitude" - },"6469": { - "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#速度" - },"6470": { - "doc": "Units, Measurement & Locale", - "title": "風速", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | 公制（公里/公尺） | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "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#風速" - },"6471": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#rainfall", - - "relUrl": "/zh-rTW/user/units-and-locale.html#rainfall" - },"6472": { - "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/hr | 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" - },"6473": { - "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 localised 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" - },"6474": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/zh-rTW/user/units-and-locale.html#changing-your-measurement-system-android" - },"6475": { - "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 | . ", - "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#相關主題" - },"6476": { - "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" - },"6477": { - "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 — no settings to change inside the app. ", - "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" - },"6478": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "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" - },"6479": { - "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. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#teplota", - - "relUrl": "/cs-rCZ/user/units-and-locale.html#teplota" - },"6480": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#distance--altitude", - - "relUrl": "/cs-rCZ/user/units-and-locale.html#distance--altitude" - },"6481": { - "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" - },"6482": { - "doc": "Units, Measurement & Locale", - "title": "Vítr", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metrický | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry 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" - },"6483": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#rainfall", - - "relUrl": "/cs-rCZ/user/units-and-locale.html#rainfall" - },"6484": { - "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/hr | 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" - },"6485": { - "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 localised 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" - },"6486": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/cs-rCZ/user/units-and-locale.html#changing-your-measurement-system-android" - },"6487": { - "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 | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#related-topics", - - "relUrl": "/cs-rCZ/user/units-and-locale.html#related-topics" - },"6488": { - "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" - },"6489": { - "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 — no settings to change inside the app. ", - "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" - },"6490": { - "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#how-it-works", - - "relUrl": "/fr-rFR/user/units-and-locale.html#how-it-works" - },"6491": { - "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. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#temp%C3%A9rature", - - "relUrl": "/fr-rFR/user/units-and-locale.html#température" - },"6492": { - "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#distance--altitude", - - "relUrl": "/fr-rFR/user/units-and-locale.html#distance--altitude" - },"6493": { - "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" - },"6494": { - "doc": "Units, Measurement & Locale", - "title": "Vent", - "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#vent", - - "relUrl": "/fr-rFR/user/units-and-locale.html#vent" - },"6495": { - "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 mm | . | Imperial (US) | 0.5 in | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#rainfall", - - "relUrl": "/fr-rFR/user/units-and-locale.html#rainfall" - },"6496": { - "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/hr | 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" - },"6497": { - "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 localised 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" - },"6498": { - "doc": "Units, Measurement & Locale", - "title": "Changing Your Measurement System (Android)", - "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#changing-your-measurement-system-android", - - "relUrl": "/fr-rFR/user/units-and-locale.html#changing-your-measurement-system-android" - },"6499": { - "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 | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#related-topics", - - "relUrl": "/fr-rFR/user/units-and-locale.html#related-topics" - },"6500": { - "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" - },"6501": { + "relUrl": "/uk-rUA/user/units-and-locale.html" + },"6109": { "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 — no settings to change inside the app. ", "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" - },"6502": { + },"6110": { "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", "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" - },"6503": { + },"6111": { "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. ", "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#温度" - },"6504": { + },"6112": { "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#distance--altitude", "relUrl": "/zh-rCN/user/units-and-locale.html#distance--altitude" - },"6505": { + },"6113": { "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#速度" - },"6506": { + },"6114": { "doc": "Units, Measurement & Locale", "title": "风", "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | 公制 | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#%E9%A3%8E", "relUrl": "/zh-rCN/user/units-and-locale.html#风" - },"6507": { + },"6115": { "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 mm | . | Imperial (US) | 0.5 in | . ", "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#rainfall", "relUrl": "/zh-rCN/user/units-and-locale.html#rainfall" - },"6508": { + },"6116": { "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/hr | 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" - },"6509": { + },"6117": { "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 localised 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" - },"6510": { + },"6118": { "doc": "Units, Measurement & Locale", "title": "Changing Your Measurement System (Android)", "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#changing-your-measurement-system-android", "relUrl": "/zh-rCN/user/units-and-locale.html#changing-your-measurement-system-android" - },"6511": { + },"6119": { "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 | . ", "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#related-topics", "relUrl": "/zh-rCN/user/units-and-locale.html#related-topics" - },"6512": { + },"6120": { "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" - },"6513": { + },"6121": { + "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 — no settings to change inside the app. ", + "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" + },"6122": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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#как-работи" + },"6123": { + "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. ", + "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#температура" + },"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 | Надморска височина | . | Метрични | 350 m | 2.5 km | 1,200 m | . | Imperial (US) | 1,148 ft | 1.6 mi | 3,937 ft | . The app uses natural scaling — short distances stay in meters or feet, while longer distances switch to kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#distance--altitude", + + "relUrl": "/bg-rBG/user/units-and-locale.html#distance--altitude" + },"6125": { + "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#скорост" + },"6126": { + "doc": "Units, Measurement & Locale", + "title": "Вятър", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Метрични | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "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#вятър" + },"6127": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#rainfall", + + "relUrl": "/bg-rBG/user/units-and-locale.html#rainfall" + },"6128": { + "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/hr | 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" + },"6129": { + "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 localised 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" + },"6130": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/bg-rBG/user/units-and-locale.html#changing-your-measurement-system-android" + },"6131": { + "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 | . ", + "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#related-topics", + + "relUrl": "/bg-rBG/user/units-and-locale.html#related-topics" + },"6132": { + "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" + },"6133": { + "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 — no settings to change inside the app. ", + "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" + },"6134": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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#運作方式" + },"6135": { + "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. ", + "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#溫度" + },"6136": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#distance--altitude", + + "relUrl": "/zh-rTW/user/units-and-locale.html#distance--altitude" + },"6137": { + "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#速度" + },"6138": { + "doc": "Units, Measurement & Locale", + "title": "風速", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | 公制（公里/公尺） | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "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#風速" + },"6139": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#rainfall", + + "relUrl": "/zh-rTW/user/units-and-locale.html#rainfall" + },"6140": { + "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/hr | 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" + },"6141": { + "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 localised 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" + },"6142": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/zh-rTW/user/units-and-locale.html#changing-your-measurement-system-android" + },"6143": { + "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 | . ", + "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#相關主題" + },"6144": { + "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" + },"6145": { + "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 — no settings to change inside the app. ", + "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" + },"6146": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6147": { + "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. ", + "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#температура" + },"6148": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#distance--altitude", + + "relUrl": "/sr-rLatn/user/units-and-locale.html#distance--altitude" + },"6149": { + "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#брзина" + },"6150": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Метрика | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#wind", + + "relUrl": "/sr-rLatn/user/units-and-locale.html#wind" + },"6151": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#rainfall", + + "relUrl": "/sr-rLatn/user/units-and-locale.html#rainfall" + },"6152": { + "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/hr | 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" + },"6153": { + "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 localised 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" + },"6154": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/sr-rLatn/user/units-and-locale.html#changing-your-measurement-system-android" + },"6155": { + "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 | . ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#related-topics", + + "relUrl": "/sr-rLatn/user/units-and-locale.html#related-topics" + },"6156": { + "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" + },"6157": { + "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 — no settings to change inside the app. ", + "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" + },"6158": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6159": { + "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. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#teplota", + + "relUrl": "/cs-rCZ/user/units-and-locale.html#teplota" + },"6160": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#distance--altitude", + + "relUrl": "/cs-rCZ/user/units-and-locale.html#distance--altitude" + },"6161": { + "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" + },"6162": { + "doc": "Units, Measurement & Locale", + "title": "Vítr", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metrický | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry 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" + },"6163": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#rainfall", + + "relUrl": "/cs-rCZ/user/units-and-locale.html#rainfall" + },"6164": { + "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/hr | 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" + },"6165": { + "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 localised 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" + },"6166": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/cs-rCZ/user/units-and-locale.html#changing-your-measurement-system-android" + },"6167": { + "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 | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#related-topics", + + "relUrl": "/cs-rCZ/user/units-and-locale.html#related-topics" + },"6168": { + "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" + },"6169": { + "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 — no settings to change inside the app. ", + "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#units-measurement--locale", + + "relUrl": "/en/user/units-and-locale.html#units-measurement--locale" + },"6170": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#how-it-works", + + "relUrl": "/en/user/units-and-locale.html#how-it-works" + },"6171": { + "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. ", + "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#temperature", + + "relUrl": "/en/user/units-and-locale.html#temperature" + },"6172": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#distance--altitude", + + "relUrl": "/en/user/units-and-locale.html#distance--altitude" + },"6173": { + "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" + },"6174": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#wind", + + "relUrl": "/en/user/units-and-locale.html#wind" + },"6175": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#rainfall", + + "relUrl": "/en/user/units-and-locale.html#rainfall" + },"6176": { + "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/hr | 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" + },"6177": { + "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 localised 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" + },"6178": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/en/user/units-and-locale.html#changing-your-measurement-system-android" + },"6179": { + "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 | . ", + "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#related-topics", + + "relUrl": "/en/user/units-and-locale.html#related-topics" + },"6180": { + "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" + },"6181": { + "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 — no settings to change inside the app. ", + "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" + },"6182": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6183": { + "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. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#temperatura", + + "relUrl": "/sl-rSI/user/units-and-locale.html#temperatura" + },"6184": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#distance--altitude", + + "relUrl": "/sl-rSI/user/units-and-locale.html#distance--altitude" + },"6185": { + "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" + },"6186": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#wind", + + "relUrl": "/sl-rSI/user/units-and-locale.html#wind" + },"6187": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#rainfall", + + "relUrl": "/sl-rSI/user/units-and-locale.html#rainfall" + },"6188": { + "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/hr | 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" + },"6189": { + "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 localised 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" + },"6190": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/sl-rSI/user/units-and-locale.html#changing-your-measurement-system-android" + },"6191": { + "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 | . ", + "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#related-topics", + + "relUrl": "/sl-rSI/user/units-and-locale.html#related-topics" + },"6192": { + "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" + },"6193": { + "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 — no settings to change inside the app. ", + "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" + },"6194": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#come-funziona", + + "relUrl": "/it-rIT/user/units-and-locale.html#come-funziona" + },"6195": { + "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. ", + "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#temperatura", + + "relUrl": "/it-rIT/user/units-and-locale.html#temperatura" + },"6196": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#distance--altitude", + + "relUrl": "/it-rIT/user/units-and-locale.html#distance--altitude" + },"6197": { + "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à" + },"6198": { + "doc": "Units, Measurement & Locale", + "title": "Vento", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metrico | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#vento", + + "relUrl": "/it-rIT/user/units-and-locale.html#vento" + },"6199": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#rainfall", + + "relUrl": "/it-rIT/user/units-and-locale.html#rainfall" + },"6200": { + "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/hr | 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" + },"6201": { + "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 localised 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" + },"6202": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/it-rIT/user/units-and-locale.html#changing-your-measurement-system-android" + },"6203": { + "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 | . ", + "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#related-topics", + + "relUrl": "/it-rIT/user/units-and-locale.html#related-topics" + },"6204": { + "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" + },"6205": { + "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 — no settings to change inside the app. ", + "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" + },"6206": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6207": { + "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. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#temperatura", + + "relUrl": "/pt-rBR/user/units-and-locale.html#temperatura" + },"6208": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#distance--altitude", + + "relUrl": "/pt-rBR/user/units-and-locale.html#distance--altitude" + },"6209": { + "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" + },"6210": { + "doc": "Units, Measurement & Locale", + "title": "Vento", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#vento", + + "relUrl": "/pt-rBR/user/units-and-locale.html#vento" + },"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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#rainfall", + + "relUrl": "/pt-rBR/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ção | μR/hr | 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" + },"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 localised 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" + },"6214": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/pt-rBR/user/units-and-locale.html#changing-your-measurement-system-android" + },"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 | . ", + "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#related-topics", + + "relUrl": "/pt-rBR/user/units-and-locale.html#related-topics" + },"6216": { + "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" + },"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 — no settings to change inside the app. ", + "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" + },"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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6219": { + "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. ", + "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#temperature", + + "relUrl": "/is-rIS/user/units-and-locale.html#temperature" + },"6220": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#distance--altitude", + + "relUrl": "/is-rIS/user/units-and-locale.html#distance--altitude" + },"6221": { + "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" + },"6222": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#wind", + + "relUrl": "/is-rIS/user/units-and-locale.html#wind" + },"6223": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#rainfall", + + "relUrl": "/is-rIS/user/units-and-locale.html#rainfall" + },"6224": { + "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/hr | 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" + },"6225": { + "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 localised 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" + },"6226": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/is-rIS/user/units-and-locale.html#changing-your-measurement-system-android" + },"6227": { + "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 | . ", + "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#related-topics", + + "relUrl": "/is-rIS/user/units-and-locale.html#related-topics" + },"6228": { + "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" + },"6229": { + "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 — no settings to change inside the app. ", + "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" + },"6230": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#how-it-works", + + "relUrl": "/fr-rFR/user/units-and-locale.html#how-it-works" + },"6231": { + "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. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#temp%C3%A9rature", + + "relUrl": "/fr-rFR/user/units-and-locale.html#température" + },"6232": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#distance--altitude", + + "relUrl": "/fr-rFR/user/units-and-locale.html#distance--altitude" + },"6233": { + "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" + },"6234": { + "doc": "Units, Measurement & Locale", + "title": "Vent", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#vent", + + "relUrl": "/fr-rFR/user/units-and-locale.html#vent" + },"6235": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#rainfall", + + "relUrl": "/fr-rFR/user/units-and-locale.html#rainfall" + },"6236": { + "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/hr | 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" + },"6237": { + "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 localised 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" + },"6238": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/fr-rFR/user/units-and-locale.html#changing-your-measurement-system-android" + },"6239": { + "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 | . ", + "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#related-topics", + + "relUrl": "/fr-rFR/user/units-and-locale.html#related-topics" + },"6240": { + "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" + },"6241": { "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 — no settings to change inside the app. ", "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#units-measurement--locale", "relUrl": "/srp/user/units-and-locale.html#units-measurement--locale" - },"6514": { + },"6242": { "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#how-it-works", "relUrl": "/srp/user/units-and-locale.html#how-it-works" - },"6515": { + },"6243": { "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. ", "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#температура" - },"6516": { + },"6244": { "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#distance--altitude", "relUrl": "/srp/user/units-and-locale.html#distance--altitude" - },"6517": { + },"6245": { "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#брзина" - },"6518": { + },"6246": { "doc": "Units, Measurement & Locale", "title": "Wind", "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Метрика | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#wind", "relUrl": "/srp/user/units-and-locale.html#wind" - },"6519": { + },"6247": { "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 mm | . | Imperial (US) | 0.5 in | . ", "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#rainfall", "relUrl": "/srp/user/units-and-locale.html#rainfall" - },"6520": { + },"6248": { "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/hr | 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" - },"6521": { + },"6249": { "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 localised 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" - },"6522": { + },"6250": { "doc": "Units, Measurement & Locale", "title": "Changing Your Measurement System (Android)", "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#changing-your-measurement-system-android", "relUrl": "/srp/user/units-and-locale.html#changing-your-measurement-system-android" - },"6523": { + },"6251": { "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 | . ", "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#related-topics", "relUrl": "/srp/user/units-and-locale.html#related-topics" - },"6524": { + },"6252": { "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" - },"6525": { + },"6253": { + "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 — no settings to change inside the app. ", + "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" + },"6254": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6255": { + "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. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#teplota", + + "relUrl": "/sk-rSK/user/units-and-locale.html#teplota" + },"6256": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#distance--altitude", + + "relUrl": "/sk-rSK/user/units-and-locale.html#distance--altitude" + },"6257": { + "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ť" + },"6258": { + "doc": "Units, Measurement & Locale", + "title": "Vietor", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#vietor", + + "relUrl": "/sk-rSK/user/units-and-locale.html#vietor" + },"6259": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#rainfall", + + "relUrl": "/sk-rSK/user/units-and-locale.html#rainfall" + },"6260": { + "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/hr | 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" + },"6261": { + "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 localised 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" + },"6262": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/sk-rSK/user/units-and-locale.html#changing-your-measurement-system-android" + },"6263": { + "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 | . ", + "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#related-topics", + + "relUrl": "/sk-rSK/user/units-and-locale.html#related-topics" + },"6264": { + "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" + },"6265": { + "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset", + "title": "Yksiköt, mittaus ja kieli- ja alueasetukset", + "content": "Meshtastic-sovellus näyttää automaattisesti lämpötilat, etäisyydet, nopeudet ja ajat niissä yksiköissä, jotka laitteesi on asetettu käyttämään — asetuksia ei tarvitse muuttaa sovelluksessa. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html", + + "relUrl": "/fi-rFI/user/units-and-locale.html" + },"6266": { + "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset", + "title": "Miten 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. 💡 Vinkki: Mittayksiköitä ei tarvitse koskaan vaihtaa sovelluksen sisältä. Muuta järjestelmäsi mittayksikköasetuksia, niin kaikki Meshtasticin näkymät päivittyvät automaattisesti — radion tiedot, telemetriakaaviot, sää, korkeus ja paljon muuta. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#miten-se-toimii", + + "relUrl": "/fi-rFI/user/units-and-locale.html#miten-se-toimii" + },"6267": { + "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. ", + "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" + },"6268": { + "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 | . Sovellus käyttää luonnollista skaalausta — lyhyet etäisyydet pysyvät metreissä tai jaloissa, kun taas pidemmät etäisyydet vaihtuvat automaattisesti kilometreihin tai maileihin. 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" + },"6269": { + "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" + },"6270": { + "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset", + "title": "Tuuli", + "content": "Tuulen nopeus- ja puuskadata ympäristösensoreista lähetetään muodossa m/s ja muunnetaan näyttöä varten. | Asetuksesi | Näet | . | Metrijärjestelmä | 5 m/s | . | Imperiaalinen (US) | 11 mph | . Tuulimittaukset näkyvät Radion tiedot -näkymän ympäristöosiossa sekä Ympäristötelemetria -kaavioissa. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#tuuli", + + "relUrl": "/fi-rFI/user/units-and-locale.html#tuuli" + },"6271": { + "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 mm | . | Imperiaalinen (US) | 0.5 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ä" + },"6272": { + "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/hr | 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" + },"6273": { + "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 | . Sovellus käyttää myös suhteellista aikaa silloin kun se on järkevää — esimerkiksi “5 min sitten” tai “2 tuntia sitten” radiolistassa — ja tämä mukautuu automaattisesti laitteesi kieleen. ", + "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" + },"6274": { + "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset", + "title": "Mittausjärjestelmän vaihtaminen (Android)", + "content": "Androidissa mittausjärjestelmäsi (metrinen vs imperial) on sidottu alueasetuksiin: . | Avaa Asetukset → Järjestelmä → Kieli ja alue | Vaihda Alue- tai Mittausyksiköt-asetusta | Palaa Meshtasticiin — arvot päivittyvät välittömästi | . 💡 Vinkki: Kaikki mittausten muotoilut tehdään keskitetysti ja ne noudattavat käyttöympäristösi alueasetuksia, joten yksiköt pysyvät yhtenäisinä kaikkialla sovelluksessa. ", + "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#mittausj%C3%A4rjestelm%C3%A4n-vaihtaminen-android", + + "relUrl": "/fi-rFI/user/units-and-locale.html#mittausjärjestelmän-vaihtaminen-android" + },"6275": { + "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 | . ", + "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" + },"6276": { + "doc": "Единицы измерения и локаль", + "title": "Единицы измерения и локаль", + "content": "Приложение Meshtastic автоматически отображает температуру, расстояние, скорость и время в единицах, настроенных на вашем устройстве — никаких настроек внутри приложения менять не нужно. ", + "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html", + + "relUrl": "/ru-rRU/user/units-and-locale.html" + },"6277": { + "doc": "Единицы измерения и локаль", + "title": "Как это работает", + "content": "Радиостанции Meshtastic всегда передают данные в метрических единицах (метры, °C, м/с, гПа и т.д.). Когда приложение получает эти данные, оно преобразует их и показывает значения в той системе единиц, которую задает локаль устройства. На Android твои предпочтения единиц измерений определяются настройками системы Язык и регион. На настольном компьютере (JVM) приложение использует стандартную Locale JVM. 💡 Совет: тебе никогда не нужно менять единицы измерения в приложении. Измени настройки единиц измерения в системе, и все экраны в Meshtastic обновятся автоматически — детали ноды, графики телеметрии, погода, высота и многое другое. ", + "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#как-это-работает" + },"6278": { + "doc": "Единицы измерения и локаль", + "title": "Температура", + "content": "Значения температуры от датчиков окружающей среды передаются в °C и отображаются в соответствии с предпочтительным единицами температуры твоего устройства. | Твои настройки | Ты видишь | . | Цельсий | 22°C | . | Фаренгейт | 72°F | . Это влияет на все отображения температуры в приложении: телеметрия окружающей среды ноды, температура почвы, точка росы и оси диаграммы телеметрии. ", + "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#температура" + },"6279": { + "doc": "Единицы измерения и локаль", + "title": "Расстояние и высота", + "content": "Расстояния между нодами и высоты GPS передаются в метрах и автоматически масштабируются и преобразуются. | Твои настройки | Небольшое расстояние | Дальнее расстояние | Высота | . | Метрическая | 350 м | 2,5 км | 1200 м | . | Имперская | 1148 фт | 1,6 миль | 3937 фт | . Приложение использует естественное масштабирование — небольшие расстояния остаются в метрах или футах, а более дальние автоматически переключаются на километры или мили. Где они появляются . | Список нод — расстояние и азимут до каждой ноды | Детали ноды — высота, расстояние от твоего положения | Карта — расстояния между путевыми точками, расстояния между хопами трассировки | Компас — расстояние до выбранной ноды | . ", + "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#расстояние-и-высота" + },"6280": { + "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#скорость" + },"6281": { + "doc": "Единицы измерения и локаль", + "title": "Ветер", + "content": "Данные о скорости ветра и порывах с датчиков окружающей среды передаются в м/с и преобразуются для отображения. | Твоя настройка | Ты видишь | . | Метрическая | 5 м/с | . | Имперская (США) | 11 миль/ч | . Показания ветра отображаются в разделе среды Детали ноды и на диаграммах Телеметрия окружающей среды. ", + "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#ветер" + },"6282": { + "doc": "Единицы измерения и локаль", + "title": "Осадки", + "content": "Измерения осадков (за 1 час и за 24 часа) передаются в мм и конвертируются для отображения. | Твоя настройка | Ты видишь | . | Метрическая | 12 мм | . | Имперская (США) | 0,5 дюймов | . ", + "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#осадки" + },"6283": { + "doc": "Единицы измерения и локаль", + "title": "Единицы, которые никогда не меняются", + "content": "Некоторые единицы являются международными стандартами и отображаются одинаково независимо от вашего региона: . | Показатель | Единица | Почему | . | Барометрическое давление | гПа | Международный метеорологический стандарт | . | Курс / азимут | ° (градусы) | Универсальная навигационная конвенция | . | Радиация | мкР/ч | Стандартная единица дозиметрии | . | 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#единицы-которые-никогда-не-меняются" + },"6284": { + "doc": "Единицы измерения и локаль", + "title": "Дата и время", + "content": "Все отметки времени в приложении — последняя активность, время сообщений, журналы телеметрии, оси графиков — следуют настройкам даты и времени вашего устройства. | Настройка | Что это контролирует | Пример | . | 24-часовой формат времени | Формат часов | 14:30 или 2:30 PM | . | Формат даты | Сортировка даты | 09/05/2026 или 05/09/2026 | . Приложение также использует относительное время в списке нод, где это имеет смысл — например, “5 минут назад” или “2 часа назад”, которое автоматически локализуется на язык твоего устройства. ", + "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#дата-и-время" + },"6285": { + "doc": "Единицы измерения и локаль", + "title": "Изменение системы измерений (Android)", + "content": "На Android система измерений (метрическая или имперская) связана с настройкой региона: . | Откройте Настройки Android → Система → Язык и регион | Измените свои предпочтения в Регион или Единицы измерения | Вернуться к Meshtastic — значения обновляются немедленно | . 💡 Совет: Все форматирование производится в централизованном порядке и уважает локаль платформы, поэтому единицы измерения всегда в приложении. ", + "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D0%B8%D0%B7%D0%BC%D0%B5%D0%BD%D0%B5%D0%BD%D0%B8%D0%B5-%D1%81%D0%B8%D1%81%D1%82%D0%B5%D0%BC%D1%8B-%D0%B8%D0%B7%D0%BC%D0%B5%D1%80%D0%B5%D0%BD%D0%B8%D0%B9-android", + + "relUrl": "/ru-rRU/user/units-and-locale.html#изменение-системы-измерений-android" + },"6286": { + "doc": "Единицы измерения и локаль", + "title": "Связанные темы", + "content": ". | Метрики ноды — здесь отображаются температура, расстояние и значения датчиков | Телеметрия и датчики — датчики, производящие эти измерения | Измерение и форматирование — ссылка на разработчика утилит форматирования | Настройки — Радио и Пользователь — настройка региона, управляющая выбором единиц | . ", + "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#связанные-темы" + },"6287": { + "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 — no settings to change inside the app. ", + "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" + },"6288": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6289": { + "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. ", + "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#온도" + },"6290": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#distance--altitude", + + "relUrl": "/ko-rKR/user/units-and-locale.html#distance--altitude" + },"6291": { + "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" + },"6292": { + "doc": "Units, Measurement & Locale", + "title": "바람", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "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#바람" + },"6293": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#rainfall", + + "relUrl": "/ko-rKR/user/units-and-locale.html#rainfall" + },"6294": { + "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/hr | 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" + },"6295": { + "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 localised 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" + },"6296": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/ko-rKR/user/units-and-locale.html#changing-your-measurement-system-android" + },"6297": { + "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 | . ", + "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#related-topics", + + "relUrl": "/ko-rKR/user/units-and-locale.html#related-topics" + },"6298": { + "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" + },"6299": { + "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 — no settings to change inside the app. ", + "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" + },"6300": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6301": { + "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. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#temperature", + + "relUrl": "/hr-rHR/user/units-and-locale.html#temperature" + },"6302": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#distance--altitude", + + "relUrl": "/hr-rHR/user/units-and-locale.html#distance--altitude" + },"6303": { + "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" + },"6304": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#wind", + + "relUrl": "/hr-rHR/user/units-and-locale.html#wind" + },"6305": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#rainfall", + + "relUrl": "/hr-rHR/user/units-and-locale.html#rainfall" + },"6306": { + "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/hr | 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" + },"6307": { + "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 localised 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" + },"6308": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/hr-rHR/user/units-and-locale.html#changing-your-measurement-system-android" + },"6309": { + "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 | . ", + "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#related-topics", + + "relUrl": "/hr-rHR/user/units-and-locale.html#related-topics" + },"6310": { + "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" + },"6311": { "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 — no settings to change inside the app. ", "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" - },"6526": { + },"6312": { "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", "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" - },"6527": { + },"6313": { "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. ", "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#temperatura", "relUrl": "/sq-rAL/user/units-and-locale.html#temperatura" - },"6528": { + },"6314": { "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#distance--altitude", "relUrl": "/sq-rAL/user/units-and-locale.html#distance--altitude" - },"6529": { + },"6315": { "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" - },"6530": { + },"6316": { "doc": "Units, Measurement & Locale", "title": "Wind", "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#wind", "relUrl": "/sq-rAL/user/units-and-locale.html#wind" - },"6531": { + },"6317": { "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 mm | . | Imperial (US) | 0.5 in | . ", "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#rainfall", "relUrl": "/sq-rAL/user/units-and-locale.html#rainfall" - },"6532": { + },"6318": { "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/hr | 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" - },"6533": { + },"6319": { "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 localised 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" - },"6534": { + },"6320": { "doc": "Units, Measurement & Locale", "title": "Changing Your Measurement System (Android)", "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#changing-your-measurement-system-android", "relUrl": "/sq-rAL/user/units-and-locale.html#changing-your-measurement-system-android" - },"6535": { + },"6321": { "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 | . ", "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#related-topics", "relUrl": "/sq-rAL/user/units-and-locale.html#related-topics" - },"6536": { + },"6322": { "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" + },"6323": { + "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 — no settings to change inside the app. ", + "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" + },"6324": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6325": { + "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. ", + "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#temperatur", + + "relUrl": "/no-rNO/user/units-and-locale.html#temperatur" + },"6326": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#distance--altitude", + + "relUrl": "/no-rNO/user/units-and-locale.html#distance--altitude" + },"6327": { + "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" + },"6328": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#wind", + + "relUrl": "/no-rNO/user/units-and-locale.html#wind" + },"6329": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#rainfall", + + "relUrl": "/no-rNO/user/units-and-locale.html#rainfall" + },"6330": { + "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/hr | 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" + },"6331": { + "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 localised 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" + },"6332": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/no-rNO/user/units-and-locale.html#changing-your-measurement-system-android" + },"6333": { + "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 | . ", + "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#related-topics", + + "relUrl": "/no-rNO/user/units-and-locale.html#related-topics" + },"6334": { + "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" + },"6335": { + "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 — no settings to change inside the app. ", + "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" + },"6336": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6337": { + "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. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#temperat%C5%ABra", + + "relUrl": "/lt-rLT/user/units-and-locale.html#temperatūra" + },"6338": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#distance--altitude", + + "relUrl": "/lt-rLT/user/units-and-locale.html#distance--altitude" + },"6339": { + "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" + },"6340": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#wind", + + "relUrl": "/lt-rLT/user/units-and-locale.html#wind" + },"6341": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#rainfall", + + "relUrl": "/lt-rLT/user/units-and-locale.html#rainfall" + },"6342": { + "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/hr | 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" + },"6343": { + "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 localised 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" + },"6344": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/lt-rLT/user/units-and-locale.html#changing-your-measurement-system-android" + },"6345": { + "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 | . ", + "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#related-topics", + + "relUrl": "/lt-rLT/user/units-and-locale.html#related-topics" + },"6346": { + "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" + },"6347": { + "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 — no settings to change inside the app. ", + "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" + },"6348": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6349": { + "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. ", + "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#الحرارة" + },"6350": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#distance--altitude", + + "relUrl": "/ar-rSA/user/units-and-locale.html#distance--altitude" + },"6351": { + "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" + },"6352": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#wind", + + "relUrl": "/ar-rSA/user/units-and-locale.html#wind" + },"6353": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#rainfall", + + "relUrl": "/ar-rSA/user/units-and-locale.html#rainfall" + },"6354": { + "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/hr | 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" + },"6355": { + "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 localised 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" + },"6356": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/ar-rSA/user/units-and-locale.html#changing-your-measurement-system-android" + },"6357": { + "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 | . ", + "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#related-topics", + + "relUrl": "/ar-rSA/user/units-and-locale.html#related-topics" + },"6358": { + "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" + },"6359": { + "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 — no settings to change inside the app. ", + "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" + },"6360": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6361": { + "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. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#temperatura", + + "relUrl": "/pt-rPT/user/units-and-locale.html#temperatura" + },"6362": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#distance--altitude", + + "relUrl": "/pt-rPT/user/units-and-locale.html#distance--altitude" + },"6363": { + "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" + },"6364": { + "doc": "Units, Measurement & Locale", + "title": "Vento", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#vento", + + "relUrl": "/pt-rPT/user/units-and-locale.html#vento" + },"6365": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#rainfall", + + "relUrl": "/pt-rPT/user/units-and-locale.html#rainfall" + },"6366": { + "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/hr | 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" + },"6367": { + "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 localised 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" + },"6368": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/pt-rPT/user/units-and-locale.html#changing-your-measurement-system-android" + },"6369": { + "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 | . ", + "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#related-topics", + + "relUrl": "/pt-rPT/user/units-and-locale.html#related-topics" + },"6370": { + "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" + },"6371": { + "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 — no settings to change inside the app. ", + "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" + },"6372": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6373": { + "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. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#temperature", + + "relUrl": "/iw-rIL/user/units-and-locale.html#temperature" + },"6374": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#distance--altitude", + + "relUrl": "/iw-rIL/user/units-and-locale.html#distance--altitude" + },"6375": { + "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" + },"6376": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#wind", + + "relUrl": "/iw-rIL/user/units-and-locale.html#wind" + },"6377": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#rainfall", + + "relUrl": "/iw-rIL/user/units-and-locale.html#rainfall" + },"6378": { + "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/hr | 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" + },"6379": { + "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 localised 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" + },"6380": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/iw-rIL/user/units-and-locale.html#changing-your-measurement-system-android" + },"6381": { + "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 | . ", + "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#related-topics", + + "relUrl": "/iw-rIL/user/units-and-locale.html#related-topics" + },"6382": { + "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" + },"6383": { + "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 — no settings to change inside the app. ", + "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" + },"6384": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6385": { + "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. ", + "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#θερμοκρασία" + },"6386": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#distance--altitude", + + "relUrl": "/el-rGR/user/units-and-locale.html#distance--altitude" + },"6387": { + "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" + },"6388": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#wind", + + "relUrl": "/el-rGR/user/units-and-locale.html#wind" + },"6389": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#rainfall", + + "relUrl": "/el-rGR/user/units-and-locale.html#rainfall" + },"6390": { + "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/hr | 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" + },"6391": { + "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 localised 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" + },"6392": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/el-rGR/user/units-and-locale.html#changing-your-measurement-system-android" + },"6393": { + "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 | . ", + "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#related-topics", + + "relUrl": "/el-rGR/user/units-and-locale.html#related-topics" + },"6394": { + "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" + },"6395": { + "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 — no settings to change inside the app. ", + "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" + },"6396": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6397": { + "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. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#temperature", + + "relUrl": "/ro-rRO/user/units-and-locale.html#temperature" + },"6398": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#distance--altitude", + + "relUrl": "/ro-rRO/user/units-and-locale.html#distance--altitude" + },"6399": { + "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" + },"6400": { + "doc": "Units, Measurement & Locale", + "title": "Vânt", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#v%C3%A2nt", + + "relUrl": "/ro-rRO/user/units-and-locale.html#vânt" + },"6401": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#rainfall", + + "relUrl": "/ro-rRO/user/units-and-locale.html#rainfall" + },"6402": { + "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/hr | 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" + },"6403": { + "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 localised 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" + },"6404": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/ro-rRO/user/units-and-locale.html#changing-your-measurement-system-android" + },"6405": { + "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 | . ", + "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#related-topics", + + "relUrl": "/ro-rRO/user/units-and-locale.html#related-topics" + },"6406": { + "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" + },"6407": { + "doc": "Ühikud, mõõtühikud ja lokaat", + "title": "Ühikud, mõõtühikud ja lokaat", + "content": "Meshtastic rakendus kuvab automaatselt temperatuure, vahemaid, kiirusi ja aegu ühikutes, milleks sinu seade on seadistatud – rakenduses pole vaja sätteid muuta. ", + "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html", + + "relUrl": "/et-rEE/user/units-and-locale.html" + },"6408": { + "doc": "Ühikud, mõõtühikud ja lokaat", + "title": "How It Works", + "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”. 💡 Vihje: Rakenduses pole kunagi vaja ühikuid vahetada. Muuda oma süsteemi mõõtmiste eelistusi ja kõik Meshtasticu ekraanid värskendatakse automaatselt – sõlmede üksikasjad, telemeetriadiagrammid, ilm, kõrgus ja palju muud. ", + "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#how-it-works", + + "relUrl": "/et-rEE/user/units-and-locale.html#how-it-works" + },"6409": { + "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. ", + "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#temperatuur", + + "relUrl": "/et-rEE/user/units-and-locale.html#temperatuur" + },"6410": { + "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 | 1,200 m | . | Imperial (US) | 1,148 ft | 1.6 mi | 3,937 ft | . Rakendus kasutab loomulikku skaleerimist – lühikesed vahemaad jäävad meetritesse või jalgadesse, pikemad vahemaad aga muutuvad automaatselt kilomeetriteks või miilideks. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Kaart — teekonnapunktide vahemaad, traceroute’i hüppevahemaad | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#distance--altitude", + + "relUrl": "/et-rEE/user/units-and-locale.html#distance--altitude" + },"6411": { + "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" + },"6412": { + "doc": "Ühikud, mõõtühikud ja lokaat", + "title": "Tuul", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Sinu sätted | Teadmiseks | . | Meetriline | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#tuul", + + "relUrl": "/et-rEE/user/units-and-locale.html#tuul" + },"6413": { + "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 mm | . | Imperial (US) | 0,5 in | . ", + "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#rainfall", + + "relUrl": "/et-rEE/user/units-and-locale.html#rainfall" + },"6414": { + "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/hr | 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" + },"6415": { + "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-Hour Time | Kella vorming | 14:30 vs 2:30 PM | . | Kuupäeva vorming | Date ordering | 09/05/2026 vs 05/09/2026 | . The app also uses relative time where it makes sense — for example, “5 min ago” or “2 hours ago” in the node list — which is automatically localised into your device language. ", + "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#date--time", + + "relUrl": "/et-rEE/user/units-and-locale.html#date--time" + },"6416": { + "doc": "Ühikud, mõõtühikud ja lokaat", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Ava Androidi seaded → Süsteem → Keel ja piirkond | Change your Region or Measurement units preference | Tagasi Meshtastic juurde — väärtused värskendatakse kohe | . 💡 Vihje: Kogu mõõtühikute vormindamine toimub tsentraalselt ja arvestab platvormi lokaaduga, seega püsivad ühikud kogu rakenduses ühtsed. ", + "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/et-rEE/user/units-and-locale.html#changing-your-measurement-system-android" + },"6417": { + "doc": "Ühikud, mõõtühikud ja lokaat", + "title": "Related Topics", + "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 | . ", + "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#related-topics", + + "relUrl": "/et-rEE/user/units-and-locale.html#related-topics" + },"6418": { + "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 — no settings to change inside the app. ", + "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" + },"6419": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6420": { + "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. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#teocht", + + "relUrl": "/ga-rIE/user/units-and-locale.html#teocht" + },"6421": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#distance--altitude", + + "relUrl": "/ga-rIE/user/units-and-locale.html#distance--altitude" + },"6422": { + "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" + },"6423": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#wind", + + "relUrl": "/ga-rIE/user/units-and-locale.html#wind" + },"6424": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#rainfall", + + "relUrl": "/ga-rIE/user/units-and-locale.html#rainfall" + },"6425": { + "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/hr | 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" + },"6426": { + "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 localised 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" + },"6427": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/ga-rIE/user/units-and-locale.html#changing-your-measurement-system-android" + },"6428": { + "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 | . ", + "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#related-topics", + + "relUrl": "/ga-rIE/user/units-and-locale.html#related-topics" + },"6429": { + "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" + },"6430": { + "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 — no settings to change inside the app. ", + "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" + },"6431": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6432": { + "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. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#temperatura", + + "relUrl": "/pl-rPL/user/units-and-locale.html#temperatura" + },"6433": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#distance--altitude", + + "relUrl": "/pl-rPL/user/units-and-locale.html#distance--altitude" + },"6434": { + "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ść" + },"6435": { + "doc": "Units, Measurement & Locale", + "title": "Wiatr", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#wiatr", + + "relUrl": "/pl-rPL/user/units-and-locale.html#wiatr" + },"6436": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#rainfall", + + "relUrl": "/pl-rPL/user/units-and-locale.html#rainfall" + },"6437": { + "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/hr | 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" + },"6438": { + "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 localised 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" + },"6439": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/pl-rPL/user/units-and-locale.html#changing-your-measurement-system-android" + },"6440": { + "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 | . ", + "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#related-topics", + + "relUrl": "/pl-rPL/user/units-and-locale.html#related-topics" + },"6441": { + "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" + },"6442": { + "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 — no settings to change inside the app. ", + "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" + },"6443": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6444": { + "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. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#temperatuur", + + "relUrl": "/nl-rNL/user/units-and-locale.html#temperatuur" + },"6445": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#distance--altitude", + + "relUrl": "/nl-rNL/user/units-and-locale.html#distance--altitude" + },"6446": { + "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" + },"6447": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#wind", + + "relUrl": "/nl-rNL/user/units-and-locale.html#wind" + },"6448": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#rainfall", + + "relUrl": "/nl-rNL/user/units-and-locale.html#rainfall" + },"6449": { + "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/hr | 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" + },"6450": { + "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 localised 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" + },"6451": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/nl-rNL/user/units-and-locale.html#changing-your-measurement-system-android" + },"6452": { + "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 | . ", + "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#related-topics", + + "relUrl": "/nl-rNL/user/units-and-locale.html#related-topics" + },"6453": { + "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" + },"6454": { + "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 — no settings to change inside the app. ", + "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" + },"6455": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6456": { + "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. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#temperatur", + + "relUrl": "/sv-rSE/user/units-and-locale.html#temperatur" + },"6457": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#distance--altitude", + + "relUrl": "/sv-rSE/user/units-and-locale.html#distance--altitude" + },"6458": { + "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" + },"6459": { + "doc": "Units, Measurement & Locale", + "title": "Vind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#vind", + + "relUrl": "/sv-rSE/user/units-and-locale.html#vind" + },"6460": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#rainfall", + + "relUrl": "/sv-rSE/user/units-and-locale.html#rainfall" + },"6461": { + "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/hr | 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" + },"6462": { + "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 localised 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" + },"6463": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/sv-rSE/user/units-and-locale.html#changing-your-measurement-system-android" + },"6464": { + "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 | . ", + "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#related-topics", + + "relUrl": "/sv-rSE/user/units-and-locale.html#related-topics" + },"6465": { + "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" + },"6466": { + "doc": "単位・計測・ロケール", + "title": "単位・計測・ロケール", + "content": "Meshtastic アプリは、温度・距離・速度・時刻を、デバイスで設定されている単位で自動的に表示します。アプリ内で変更する設定はありません。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html", + + "relUrl": "/ja-rJP/user/units-and-locale.html" + },"6467": { + "doc": "単位・計測・ロケール", + "title": "仕組み", + "content": "Meshtastic の無線機は、常にメートル法の単位（メートル、°C、m/s、hPa など）でデータを送信します。 アプリはこのデータを受信すると、デバイスのロケールで指定された単位系に変換して値を表示します。 . Android では、計測の設定はシステムの言語と地域の設定によって決まります。 デスクトップ（JVM）では、アプリは JVM のデフォルトの Locale を使用します。 . 💡 ヒント： アプリ内で単位を切り替える必要はまったくありません。 システムの計測設定を変更すると、Meshtastic のすべての画面（ノードの詳細、テレメトリのグラフ、天気、標高など）が自動的に更新されます。 . ", + "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#仕組み" + },"6468": { + "doc": "単位・計測・ロケール", + "title": "温度", + "content": "環境センサーの温度値は °C で送信され、デバイスの温度単位の設定に基づいて表示されます。 . | あなたの設定 | 表示 | . | 摂氏 | 22°C | . | 華氏 | 72°F | . これは、アプリ全体のすべての温度表示に影響します：ノードの環境テレメトリ、土壌温度、露点、テレメトリグラフの軸。 . ", + "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#温度" + },"6469": { + "doc": "単位・計測・ロケール", + "title": "距離と標高", + "content": "ノード間の距離と GPS の標高はメートルで送信され、自動的にスケーリングされて変換されます。 . | あなたの設定 | 短い距離 | 長い距離 | 標高 | . | メートル法 | 350 m | 2.5 km | 1,200 m | . | ヤード・ポンド法（米国） | 1,148 ft | 1.6 mi | 3,937 ft | . アプリは自然なスケーリングを使用します。短い距離はメートルやフィートのままで、長い距離は自動的にキロメートルやマイルに切り替わります。 . 表示される場所 . | ノードリスト：各ノードまでの距離と方位 | ノードの詳細：標高、自分の位置からの距離 | マップ：ウェイポイントまでの距離、ルート追跡のホップ距離 | コンパス：選択したノードまでの距離 | . ", + "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#距離と標高" + },"6470": { + "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#速度" + },"6471": { + "doc": "単位・計測・ロケール", + "title": "風力", + "content": "環境センサーの風速と突風のデータは m/s で送信され、表示用に変換されます。 . | あなたの設定 | 表示 | . | メートル法 | 5 m/s | . | ヤード・ポンド法（米国） | 11 mph | . 風の測定値は、「ノードの詳細」の環境セクションと「環境テレメトリ」のグラフに表示されます。 . ", + "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#風力" + },"6472": { + "doc": "単位・計測・ロケール", + "title": "降水量", + "content": "降水量の測定値（1 時間および 24 時間の合計）は mm で送信され、表示用に変換されます。 . | あなたの設定 | 表示 | . | メートル法 | 12 mm | . | ヤード・ポンド法（米国） | 0.5 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#降水量" + },"6473": { + "doc": "単位・計測・ロケール", + "title": "変わらない単位", + "content": "一部の単位は国際標準であり、ロケールに関係なく同じように表示されます： . | 計測項目 | 単位 | 理由 | . | 大気圧 | hPa | 国際的な気象標準 | . | 方位／進行方向 | °（度） | 普遍的な航法の慣例 | . | 放射線 | μR/hr | 標準的な線量測定の単位 | . | 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#変わらない単位" + },"6474": { + "doc": "単位・計測・ロケール", + "title": "日付と時刻", + "content": "アプリ全体のすべてのタイムスタンプ（最後の通信、メッセージの時刻、テレメトリのログ、グラフの軸）は、デバイスの日付と時刻の設定に従います。 . | 設定 | 制御する内容 | 例 | . | 24 時間表示 | 時刻の形式 | 14:30 vs 2:30 PM | . | 日付形式 | 日付の並び順 | 09/05/2026 vs 05/09/2026 | . アプリは、意味がある場面では相対時間も使用します。たとえばノードリストの「5 分前」や「2 時間前」で、これらはデバイスの言語に自動的にローカライズされます。 . ", + "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#日付と時刻" + },"6475": { + "doc": "単位・計測・ロケール", + "title": "計測系を変更する（Android）", + "content": "Android では、計測系（メートル法かヤード・ポンド法か）は地域設定に連動しています： . | 「Android の設定 → システム → 言語と地域」を開きます | 「地域」または「計測単位」の設定を変更します | Meshtastic に戻ります。値がすぐに更新されます | . 💡 ヒント： すべての計測値の書式は一元的に処理され、プラットフォームのロケールに従うため、単位はアプリ全体で一貫しています。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E8%A8%88%E6%B8%AC%E7%B3%BB%E3%82%92%E5%A4%89%E6%9B%B4%E3%81%99%E3%82%8Bandroid", + + "relUrl": "/ja-rJP/user/units-and-locale.html#計測系を変更するandroid" + },"6476": { + "doc": "単位・計測・ロケール", + "title": "関連トピック", + "content": ". | ノードメトリクス：温度・距離・センサー値が表示される場所 | テレメトリとセンサー：これらの計測値を生成するセンサー | 計測と書式：書式ユーティリティの開発者向けリファレンス | 設定：無線機とユーザー：単位の選択を決める地域設定 | . ", + "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#関連トピック" + },"6477": { + "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 — no settings to change inside the app. ", + "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" + },"6478": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6479": { + "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. ", + "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" + },"6480": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#distance--altitude", + + "relUrl": "/hu-rHU/user/units-and-locale.html#distance--altitude" + },"6481": { + "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" + },"6482": { + "doc": "Units, Measurement & Locale", + "title": "Szél", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#sz%C3%A9l", + + "relUrl": "/hu-rHU/user/units-and-locale.html#szél" + },"6483": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#rainfall", + + "relUrl": "/hu-rHU/user/units-and-locale.html#rainfall" + },"6484": { + "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/hr | 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" + },"6485": { + "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 localised 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" + },"6486": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/hu-rHU/user/units-and-locale.html#changing-your-measurement-system-android" + },"6487": { + "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 | . ", + "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#related-topics", + + "relUrl": "/hu-rHU/user/units-and-locale.html#related-topics" + },"6488": { + "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" + },"6489": { + "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 — no settings to change inside the app. ", + "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" + },"6490": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6491": { + "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. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#tanperati", + + "relUrl": "/ht-rHT/user/units-and-locale.html#tanperati" + },"6492": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#distance--altitude", + + "relUrl": "/ht-rHT/user/units-and-locale.html#distance--altitude" + },"6493": { + "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" + },"6494": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#wind", + + "relUrl": "/ht-rHT/user/units-and-locale.html#wind" + },"6495": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#rainfall", + + "relUrl": "/ht-rHT/user/units-and-locale.html#rainfall" + },"6496": { + "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/hr | 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" + },"6497": { + "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 localised 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" + },"6498": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/ht-rHT/user/units-and-locale.html#changing-your-measurement-system-android" + },"6499": { + "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 | . ", + "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#related-topics", + + "relUrl": "/ht-rHT/user/units-and-locale.html#related-topics" + },"6500": { + "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" + },"6501": { + "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 — no settings to change inside the app. ", + "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" + },"6502": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6503": { + "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. ", + "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#temperature", + + "relUrl": "/gl-rES/user/units-and-locale.html#temperature" + },"6504": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#distance--altitude", + + "relUrl": "/gl-rES/user/units-and-locale.html#distance--altitude" + },"6505": { + "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" + },"6506": { + "doc": "Units, Measurement & Locale", + "title": "Wind", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#wind", + + "relUrl": "/gl-rES/user/units-and-locale.html#wind" + },"6507": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#rainfall", + + "relUrl": "/gl-rES/user/units-and-locale.html#rainfall" + },"6508": { + "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/hr | 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" + },"6509": { + "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 localised 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" + },"6510": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/gl-rES/user/units-and-locale.html#changing-your-measurement-system-android" + },"6511": { + "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 | . ", + "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#related-topics", + + "relUrl": "/gl-rES/user/units-and-locale.html#related-topics" + },"6512": { + "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" + },"6513": { + "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 — no settings to change inside the app. ", + "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" + },"6514": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6515": { + "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. ", + "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" + },"6516": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#distance--altitude", + + "relUrl": "/tr-rTR/user/units-and-locale.html#distance--altitude" + },"6517": { + "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" + },"6518": { + "doc": "Units, Measurement & Locale", + "title": "Rüzgar", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Metric | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#r%C3%BCzgar", + + "relUrl": "/tr-rTR/user/units-and-locale.html#rüzgar" + },"6519": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#rainfall", + + "relUrl": "/tr-rTR/user/units-and-locale.html#rainfall" + },"6520": { + "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/hr | 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" + },"6521": { + "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 localised 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" + },"6522": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/tr-rTR/user/units-and-locale.html#changing-your-measurement-system-android" + },"6523": { + "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 | . ", + "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#related-topics", + + "relUrl": "/tr-rTR/user/units-and-locale.html#related-topics" + },"6524": { + "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" + },"6525": { + "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 — no settings to change inside the app. ", + "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" + },"6526": { + "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. 💡 Tip: You never need to toggle units inside the app. Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more. ", + "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" + },"6527": { + "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. ", + "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#temperatura", + + "relUrl": "/es-rES/user/units-and-locale.html#temperatura" + },"6528": { + "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 kilometres or miles automatically. Where these appear . | Node list — distance and bearing to each node | Node detail — altitude, distance from your position | Map — waypoint distances, traceroute hop distances | Compass — distance to selected node | . ", + "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#distance--altitude", + + "relUrl": "/es-rES/user/units-and-locale.html#distance--altitude" + },"6529": { + "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" + },"6530": { + "doc": "Units, Measurement & Locale", + "title": "Viento", + "content": "Wind speed and gust data from environment sensors are transmitted as m/s and converted for display. | Your Setting | You See | . | Métrico | 5 m/s | . | Imperial (US) | 11 mph | . Wind readings appear in the Node Detail environment section and the Environment Telemetry charts. ", + "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#viento", + + "relUrl": "/es-rES/user/units-and-locale.html#viento" + },"6531": { + "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 mm | . | Imperial (US) | 0.5 in | . ", + "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#rainfall", + + "relUrl": "/es-rES/user/units-and-locale.html#rainfall" + },"6532": { + "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/hr | 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" + },"6533": { + "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 localised 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" + },"6534": { + "doc": "Units, Measurement & Locale", + "title": "Changing Your Measurement System (Android)", + "content": "On Android, your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region or Measurement units preference | Return to Meshtastic — values update immediately | . 💡 Tip: All measurement formatting is handled centrally and respects your platform’s locale, so units stay consistent everywhere in the app. ", + "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#changing-your-measurement-system-android", + + "relUrl": "/es-rES/user/units-and-locale.html#changing-your-measurement-system-android" + },"6535": { + "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 | . ", + "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#related-topics", + + "relUrl": "/es-rES/user/units-and-locale.html#related-topics" + },"6536": { + "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" },"6537": { "doc": "User Guide", "title": "User Guide", @@ -45772,817 +45772,817 @@ "relUrl": "/en/user.html#whats-new-in-the-docs" },"6539": { - "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" - },"6540": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/is-rIS/user/widget.html#what-it-shows", - - "relUrl": "/is-rIS/user/widget.html#what-it-shows" - },"6541": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6542": { - "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 | 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" - },"6543": { - "doc": "ホーム画面ウィジェット", - "title": "ホーム画面ウィジェット", - "content": "Android では、Meshtastic はホーム画面のウィジェットを提供しており、接続中の無線機のライブなローカル統計をひと目で確認できます。アプリを開く必要はありません。 . ", - "url": "/Meshtastic-Android/main/ja-rJP/user/widget.html", - - "relUrl": "/ja-rJP/user/widget.html" - },"6544": { - "doc": "ホーム画面ウィジェット", - "title": "表示される内容", - "content": "ウィジェットは、接続中の無線機の現在のローカル統計を表示します： . | Battery：無線機のバッテリー残量。外部電源で動作している場合は Powered（給電中） | ChUtil：チャンネル利用率（LoRa チャンネルがどれだけ混雑しているかを割合で表示） | AirUtil：電波利用率（無線機がデューティサイクルのうちどれだけ送信しているか） | Traffic：送受信したパケットと、検出した重複 | Relays：中継したパケットと、中継のキャンセル（無線機が中継しているときに表示） | . ウィジェットをタップするとアプリが開きます。更新コントロールを使うと、最新の統計を要求できます。 . 💡 ヒント： 値は、現在接続している無線機を反映します。 アプリが無線機に接続していない場合、ウィジェットは再接続するまで、最後に分かっている統計を表示します。 . ", - "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#表示される内容" - },"6545": { - "doc": "ホーム画面ウィジェット", - "title": "ウィジェットを追加する", - "content": ". | Android のホーム画面の空いている場所を長押しします。 | 「ウィジェット」をタップします。 | リストで Meshtastic を見つけ、「Local Stats」ウィジェットをホーム画面にドラッグします。 | 必要に応じてサイズを変更します。レイアウトは利用可能なスペースに合わせて調整されます。 | . ⚠️ 注意： このウィジェットは Android 専用です。 デスクトップ版や 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#ウィジェットを追加する" - },"6546": { - "doc": "ホーム画面ウィジェット", - "title": "関連トピック", - "content": ". | ノードメトリクス：アプリ内の完全な信号品質とローカル統計の履歴 | コネクション：ウィジェットに表示する統計が得られるよう、無線機に接続する | 探索：メッシュ全体のチャンネル利用率と電波利用率 | . ", - "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#関連トピック" - },"6547": { - "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" - },"6548": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/ca-rES/user/widget.html#what-it-shows", - - "relUrl": "/ca-rES/user/widget.html#what-it-shows" - },"6549": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6550": { - "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 | 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" - },"6551": { - "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" - },"6552": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/sr-rLatn/user/widget.html#what-it-shows", - - "relUrl": "/sr-rLatn/user/widget.html#what-it-shows" - },"6553": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6554": { - "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 | 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" - },"6555": { - "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" - },"6556": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/ko-rKR/user/widget.html#what-it-shows", - - "relUrl": "/ko-rKR/user/widget.html#what-it-shows" - },"6557": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6558": { - "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 | 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" - },"6559": { - "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" - },"6560": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/ro-rRO/user/widget.html#what-it-shows", - - "relUrl": "/ro-rRO/user/widget.html#what-it-shows" - },"6561": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6562": { - "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 | 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" - },"6563": { - "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" - },"6564": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/ga-rIE/user/widget.html#what-it-shows", - - "relUrl": "/ga-rIE/user/widget.html#what-it-shows" - },"6565": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6566": { - "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 | 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" - },"6567": { - "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" - },"6568": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/iw-rIL/user/widget.html#what-it-shows", - - "relUrl": "/iw-rIL/user/widget.html#what-it-shows" - },"6569": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6570": { - "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 | 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" - },"6571": { - "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" - },"6572": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/sv-rSE/user/widget.html#what-it-shows", - - "relUrl": "/sv-rSE/user/widget.html#what-it-shows" - },"6573": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6574": { - "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 | 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" - },"6575": { - "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" - },"6576": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/ht-rHT/user/widget.html#what-it-shows", - - "relUrl": "/ht-rHT/user/widget.html#what-it-shows" - },"6577": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6578": { - "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 | 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" - },"6579": { - "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" - },"6580": { - "doc": "Aloitusnäytön widget", - "title": "Mitä se näyttää", - "content": "Widget näyttää yhdistetyn radion tämänhetkiset paikalliset tilastot: . | 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ä) | . Avaa sovellus napauttamalla widgetiä tai pyydä uudet tilastot sen päivityspainikkeella. 💡 Vinkki: Arvot vastaavat sitä radiota, johon olet parhaillaan yhdistetty. Jos sovellus ei ole yhdistetty radioon, widget näyttää viimeksi tunnetut tilastot, kunnes yhteys muodostuu uudelleen. ", - "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ää" - },"6581": { - "doc": "Aloitusnäytön widget", - "title": "Widgetin lisääminen", - "content": ". | Paina pitkään tyhjää kohtaa Androidin aloitusnäytössä. | Napauta Widgetit. | Etsi luettelosta Meshtastic ja vedä Paikalliset tilastot -widget aloitusnäyttöön. | Muuta widgetin kokoa tarvittaessa — asettelu mukautuu käytettävissä olevaan tilaan. | . ⚠️ Huomautus: Widget 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" - },"6582": { - "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 | Haku — kanavan ja lähetysajan käyttöaste koko 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" - },"6583": { - "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" - },"6584": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/gl-rES/user/widget.html#what-it-shows", - - "relUrl": "/gl-rES/user/widget.html#what-it-shows" - },"6585": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6586": { - "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 | 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" - },"6587": { - "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" - },"6588": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/uk-rUA/user/widget.html#what-it-shows", - - "relUrl": "/uk-rUA/user/widget.html#what-it-shows" - },"6589": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6590": { - "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 | 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" - },"6591": { "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" - },"6592": { + },"6540": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", "url": "/Meshtastic-Android/main/de-rDE/user/widget.html#what-it-shows", "relUrl": "/de-rDE/user/widget.html#what-it-shows" - },"6593": { + },"6541": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6594": { + },"6542": { "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 | 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" - },"6595": { + },"6543": { "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", + "url": "/Meshtastic-Android/main/ca-rES/user/widget.html", - "relUrl": "/hr-rHR/user/widget.html" - },"6596": { + "relUrl": "/ca-rES/user/widget.html" + },"6544": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/hr-rHR/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/ca-rES/user/widget.html#what-it-shows", - "relUrl": "/hr-rHR/user/widget.html#what-it-shows" - },"6597": { + "relUrl": "/ca-rES/user/widget.html#what-it-shows" + },"6545": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/ca-rES/user/widget.html#adding-the-widget", - "relUrl": "/hr-rHR/user/widget.html#adding-the-widget" - },"6598": { + "relUrl": "/ca-rES/user/widget.html#adding-the-widget" + },"6546": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/hr-rHR/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/ca-rES/user/widget.html#related-topics", - "relUrl": "/hr-rHR/user/widget.html#related-topics" - },"6599": { - "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" - },"6600": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/lt-rLT/user/widget.html#what-it-shows", - - "relUrl": "/lt-rLT/user/widget.html#what-it-shows" - },"6601": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6602": { - "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 | 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" - },"6603": { - "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" - },"6604": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/en/user/widget.html#what-it-shows", - - "relUrl": "/en/user/widget.html#what-it-shows" - },"6605": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6606": { - "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 | 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" - },"6607": { - "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" - },"6608": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/hu-rHU/user/widget.html#what-it-shows", - - "relUrl": "/hu-rHU/user/widget.html#what-it-shows" - },"6609": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6610": { - "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 | 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" - },"6611": { - "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" - },"6612": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/bg-rBG/user/widget.html#what-it-shows", - - "relUrl": "/bg-rBG/user/widget.html#what-it-shows" - },"6613": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6614": { - "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 | 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" - },"6615": { - "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" - },"6616": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/sl-rSI/user/widget.html#what-it-shows", - - "relUrl": "/sl-rSI/user/widget.html#what-it-shows" - },"6617": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6618": { - "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 | 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" - },"6619": { - "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" - },"6620": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/pt-rPT/user/widget.html#what-it-shows", - - "relUrl": "/pt-rPT/user/widget.html#what-it-shows" - },"6621": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6622": { - "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 | 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" - },"6623": { + "relUrl": "/ca-rES/user/widget.html#related-topics" + },"6547": { "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" - },"6624": { + },"6548": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", "url": "/Meshtastic-Android/main/be-rBY/user/widget.html#what-it-shows", "relUrl": "/be-rBY/user/widget.html#what-it-shows" - },"6625": { + },"6549": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6626": { + },"6550": { "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 | 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" - },"6627": { + },"6551": { + "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" + },"6552": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/uk-rUA/user/widget.html#what-it-shows", + + "relUrl": "/uk-rUA/user/widget.html#what-it-shows" + },"6553": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6554": { + "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 | 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" + },"6555": { + "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" + },"6556": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/zh-rCN/user/widget.html#what-it-shows", + + "relUrl": "/zh-rCN/user/widget.html#what-it-shows" + },"6557": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6558": { + "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 | 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" + },"6559": { + "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" + },"6560": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/bg-rBG/user/widget.html#what-it-shows", + + "relUrl": "/bg-rBG/user/widget.html#what-it-shows" + },"6561": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6562": { + "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 | 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" + },"6563": { + "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" + },"6564": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/zh-rTW/user/widget.html#what-it-shows", + + "relUrl": "/zh-rTW/user/widget.html#what-it-shows" + },"6565": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6566": { + "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 | 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#相關主題" + },"6567": { + "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" + },"6568": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/sr-rLatn/user/widget.html#what-it-shows", + + "relUrl": "/sr-rLatn/user/widget.html#what-it-shows" + },"6569": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6570": { + "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 | 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" + },"6571": { + "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/cs-rCZ/user/widget.html", + + "relUrl": "/cs-rCZ/user/widget.html" + },"6572": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/widget.html#what-it-shows", + + "relUrl": "/cs-rCZ/user/widget.html#what-it-shows" + },"6573": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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/cs-rCZ/user/widget.html#adding-the-widget", + + "relUrl": "/cs-rCZ/user/widget.html#adding-the-widget" + },"6574": { + "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 | Discovery — channel and airtime utilization across the mesh | . ", + "url": "/Meshtastic-Android/main/cs-rCZ/user/widget.html#related-topics", + + "relUrl": "/cs-rCZ/user/widget.html#related-topics" + },"6575": { + "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" + },"6576": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/en/user/widget.html#what-it-shows", + + "relUrl": "/en/user/widget.html#what-it-shows" + },"6577": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6578": { + "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 | 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" + },"6579": { + "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" + },"6580": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/sl-rSI/user/widget.html#what-it-shows", + + "relUrl": "/sl-rSI/user/widget.html#what-it-shows" + },"6581": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6582": { + "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 | 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" + },"6583": { + "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" + },"6584": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/it-rIT/user/widget.html#what-it-shows", + + "relUrl": "/it-rIT/user/widget.html#what-it-shows" + },"6585": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6586": { + "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 | 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" + },"6587": { "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" - },"6628": { + },"6588": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", "url": "/Meshtastic-Android/main/pt-rBR/user/widget.html#what-it-shows", "relUrl": "/pt-rBR/user/widget.html#what-it-shows" - },"6629": { + },"6589": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6630": { + },"6590": { "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 | 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" - },"6631": { + },"6591": { "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", + "url": "/Meshtastic-Android/main/is-rIS/user/widget.html", - "relUrl": "/el-rGR/user/widget.html" - },"6632": { + "relUrl": "/is-rIS/user/widget.html" + },"6592": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/el-rGR/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/is-rIS/user/widget.html#what-it-shows", - "relUrl": "/el-rGR/user/widget.html#what-it-shows" - },"6633": { + "relUrl": "/is-rIS/user/widget.html#what-it-shows" + },"6593": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/is-rIS/user/widget.html#adding-the-widget", - "relUrl": "/el-rGR/user/widget.html#adding-the-widget" - },"6634": { + "relUrl": "/is-rIS/user/widget.html#adding-the-widget" + },"6594": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/el-rGR/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/is-rIS/user/widget.html#related-topics", - "relUrl": "/el-rGR/user/widget.html#related-topics" - },"6635": { + "relUrl": "/is-rIS/user/widget.html#related-topics" + },"6595": { "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", + "url": "/Meshtastic-Android/main/fr-rFR/user/widget.html", - "relUrl": "/es-rES/user/widget.html" - },"6636": { + "relUrl": "/fr-rFR/user/widget.html" + },"6596": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/es-rES/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/fr-rFR/user/widget.html#what-it-shows", - "relUrl": "/es-rES/user/widget.html#what-it-shows" - },"6637": { + "relUrl": "/fr-rFR/user/widget.html#what-it-shows" + },"6597": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/fr-rFR/user/widget.html#adding-the-widget", - "relUrl": "/es-rES/user/widget.html#adding-the-widget" - },"6638": { + "relUrl": "/fr-rFR/user/widget.html#adding-the-widget" + },"6598": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/es-rES/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/fr-rFR/user/widget.html#related-topics", - "relUrl": "/es-rES/user/widget.html#related-topics" - },"6639": { + "relUrl": "/fr-rFR/user/widget.html#related-topics" + },"6599": { "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", + "url": "/Meshtastic-Android/main/srp/user/widget.html", - "relUrl": "/tr-rTR/user/widget.html" - },"6640": { + "relUrl": "/srp/user/widget.html" + },"6600": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/tr-rTR/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/srp/user/widget.html#what-it-shows", - "relUrl": "/tr-rTR/user/widget.html#what-it-shows" - },"6641": { + "relUrl": "/srp/user/widget.html#what-it-shows" + },"6601": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/srp/user/widget.html#adding-the-widget", - "relUrl": "/tr-rTR/user/widget.html#adding-the-widget" - },"6642": { + "relUrl": "/srp/user/widget.html#adding-the-widget" + },"6602": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/tr-rTR/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/srp/user/widget.html#related-topics", - "relUrl": "/tr-rTR/user/widget.html#related-topics" - },"6643": { + "relUrl": "/srp/user/widget.html#related-topics" + },"6603": { "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", + "url": "/Meshtastic-Android/main/sk-rSK/user/widget.html", - "relUrl": "/no-rNO/user/widget.html" - },"6644": { + "relUrl": "/sk-rSK/user/widget.html" + },"6604": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/no-rNO/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/sk-rSK/user/widget.html#what-it-shows", - "relUrl": "/no-rNO/user/widget.html#what-it-shows" - },"6645": { + "relUrl": "/sk-rSK/user/widget.html#what-it-shows" + },"6605": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/sk-rSK/user/widget.html#adding-the-widget", - "relUrl": "/no-rNO/user/widget.html#adding-the-widget" - },"6646": { + "relUrl": "/sk-rSK/user/widget.html#adding-the-widget" + },"6606": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/no-rNO/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/sk-rSK/user/widget.html#related-topics", - "relUrl": "/no-rNO/user/widget.html#related-topics" - },"6647": { + "relUrl": "/sk-rSK/user/widget.html#related-topics" + },"6607": { + "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" + },"6608": { + "doc": "Aloitusnäytön widget", + "title": "Mitä se näyttää", + "content": "Widget näyttää yhdistetyn radion tämänhetkiset paikalliset tilastot: . | 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ä) | . Avaa sovellus napauttamalla widgetiä tai pyydä uudet tilastot sen päivityspainikkeella. 💡 Vinkki: Arvot vastaavat sitä radiota, johon olet parhaillaan yhdistetty. Jos sovellus ei ole yhdistetty radioon, widget näyttää viimeksi tunnetut tilastot, kunnes yhteys muodostuu uudelleen. ", + "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ää" + },"6609": { + "doc": "Aloitusnäytön widget", + "title": "Widgetin lisääminen", + "content": ". | Paina pitkään tyhjää kohtaa Androidin aloitusnäytössä. | Napauta Widgetit. | Etsi luettelosta Meshtastic ja vedä Paikalliset tilastot -widget aloitusnäyttöön. | Muuta widgetin kokoa tarvittaessa — asettelu mukautuu käytettävissä olevaan tilaan. | . ⚠️ Huomautus: Widget 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" + },"6610": { + "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 | Haku — kanavan ja lähetysajan käyttöaste koko 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" + },"6611": { "doc": "Виджет на главный экран", "title": "Виджет на главный экран", "content": "На Android, Meshtastic предоставляет виджет главного экрана, который показывает статистику по живым локальным каналам с подключенного устройства без необходимости открывать приложение. ", "url": "/Meshtastic-Android/main/ru-rRU/user/widget.html", "relUrl": "/ru-rRU/user/widget.html" - },"6648": { + },"6612": { "doc": "Виджет на главный экран", "title": "Что он покажет", "content": "Виджет показывает текущую локальную статистику подключённого радиоустройства: . | Батарея — уровень заряда батареи радиоустройства или Питание от сети, когда работает от внешнего источника | ChUtil — использование канала (насколько занят канал LoRa, в процентах) | AirUtil — использование времени передачи (сколько рабочих циклов передаёт вашего радиоустройство) | Трафик — пакеты, переданные / полученные, и дубликаты | Relays — пересылаемые пакеты и отмены пересылки (показаны, когда радио действует как ретранслятор) | . Нажми на виджет, чтобы открыть приложение, или используй его кнопку обновления для запроса свежей статистики. 💡 Совет: значения отражают радиоустройство, к которому ты подключен в данный момент. Если приложение не подключено к радиоустройству, виджет покажет последнюю известную статистику до переподключения. ", "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#что-он-покажет" - },"6649": { + },"6613": { "doc": "Виджет на главный экран", "title": "Добавление виджета", "content": ". | Долгое нажатие на пустой области твоего рабочего стола Android. | Нажми Виджет. | Найди Meshtastic в списке и перетащи виджет Local Stats на домашний экран. | Изменение размера по мере необходимости — макет адаптируется к доступному пространству. | . ⚠️ Примечание: Виджет только для Android. Он недоступен для ПК или сборках для 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#добавление-виджета" - },"6650": { + },"6614": { "doc": "Виджет на главный экран", "title": "Связанные темы", "content": ". | Метрики нод — полная статистика сигнала и локальная статистика внутри приложения | Подключения — подключиться к радиоустройству, чтобы виджет показывал статистику | Discovery — использование канала и времени передачи через сеть | . ", "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#связанные-темы" + },"6615": { + "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" + },"6616": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/ko-rKR/user/widget.html#what-it-shows", + + "relUrl": "/ko-rKR/user/widget.html#what-it-shows" + },"6617": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6618": { + "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 | 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" + },"6619": { + "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" + },"6620": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/hr-rHR/user/widget.html#what-it-shows", + + "relUrl": "/hr-rHR/user/widget.html#what-it-shows" + },"6621": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6622": { + "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 | 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" + },"6623": { + "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" + },"6624": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/sq-rAL/user/widget.html#what-it-shows", + + "relUrl": "/sq-rAL/user/widget.html#what-it-shows" + },"6625": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6626": { + "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 | 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" + },"6627": { + "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" + },"6628": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/no-rNO/user/widget.html#what-it-shows", + + "relUrl": "/no-rNO/user/widget.html#what-it-shows" + },"6629": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6630": { + "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 | 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" + },"6631": { + "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" + },"6632": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/lt-rLT/user/widget.html#what-it-shows", + + "relUrl": "/lt-rLT/user/widget.html#what-it-shows" + },"6633": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6634": { + "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 | 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" + },"6635": { + "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" + },"6636": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/ar-rSA/user/widget.html#what-it-shows", + + "relUrl": "/ar-rSA/user/widget.html#what-it-shows" + },"6637": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6638": { + "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 | 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" + },"6639": { + "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" + },"6640": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/pt-rPT/user/widget.html#what-it-shows", + + "relUrl": "/pt-rPT/user/widget.html#what-it-shows" + },"6641": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6642": { + "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 | 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" + },"6643": { + "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" + },"6644": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/iw-rIL/user/widget.html#what-it-shows", + + "relUrl": "/iw-rIL/user/widget.html#what-it-shows" + },"6645": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6646": { + "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 | 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" + },"6647": { + "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" + },"6648": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/el-rGR/user/widget.html#what-it-shows", + + "relUrl": "/el-rGR/user/widget.html#what-it-shows" + },"6649": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6650": { + "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 | 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" },"6651": { "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", + "url": "/Meshtastic-Android/main/ro-rRO/user/widget.html", - "relUrl": "/nl-rNL/user/widget.html" + "relUrl": "/ro-rRO/user/widget.html" },"6652": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/nl-rNL/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/ro-rRO/user/widget.html#what-it-shows", - "relUrl": "/nl-rNL/user/widget.html#what-it-shows" + "relUrl": "/ro-rRO/user/widget.html#what-it-shows" },"6653": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/ro-rRO/user/widget.html#adding-the-widget", - "relUrl": "/nl-rNL/user/widget.html#adding-the-widget" + "relUrl": "/ro-rRO/user/widget.html#adding-the-widget" },"6654": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/nl-rNL/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/ro-rRO/user/widget.html#related-topics", - "relUrl": "/nl-rNL/user/widget.html#related-topics" + "relUrl": "/ro-rRO/user/widget.html#related-topics" },"6655": { "doc": "Home Screen Widget", "title": "Home Screen Widget", @@ -46615,281 +46615,281 @@ "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", + "url": "/Meshtastic-Android/main/ga-rIE/user/widget.html", - "relUrl": "/it-rIT/user/widget.html" + "relUrl": "/ga-rIE/user/widget.html" },"6660": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/it-rIT/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/ga-rIE/user/widget.html#what-it-shows", - "relUrl": "/it-rIT/user/widget.html#what-it-shows" + "relUrl": "/ga-rIE/user/widget.html#what-it-shows" },"6661": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/ga-rIE/user/widget.html#adding-the-widget", - "relUrl": "/it-rIT/user/widget.html#adding-the-widget" + "relUrl": "/ga-rIE/user/widget.html#adding-the-widget" },"6662": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/it-rIT/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/ga-rIE/user/widget.html#related-topics", - "relUrl": "/it-rIT/user/widget.html#related-topics" + "relUrl": "/ga-rIE/user/widget.html#related-topics" },"6663": { - "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" - },"6664": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/ar-rSA/user/widget.html#what-it-shows", - - "relUrl": "/ar-rSA/user/widget.html#what-it-shows" - },"6665": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6666": { - "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 | 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" - },"6667": { - "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" - },"6668": { - "doc": "Home Screen Widget", - "title": "What It Shows", - "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/sk-rSK/user/widget.html#what-it-shows", - - "relUrl": "/sk-rSK/user/widget.html#what-it-shows" - },"6669": { - "doc": "Home Screen Widget", - "title": "Adding the Widget", - "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6670": { - "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 | 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" - },"6671": { "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" - },"6672": { + },"6664": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", "url": "/Meshtastic-Android/main/pl-rPL/user/widget.html#what-it-shows", "relUrl": "/pl-rPL/user/widget.html#what-it-shows" - },"6673": { + },"6665": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" - },"6674": { + },"6666": { "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 | 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" - },"6675": { + },"6667": { "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", + "url": "/Meshtastic-Android/main/nl-rNL/user/widget.html", - "relUrl": "/zh-rTW/user/widget.html" - },"6676": { + "relUrl": "/nl-rNL/user/widget.html" + },"6668": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/zh-rTW/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/nl-rNL/user/widget.html#what-it-shows", - "relUrl": "/zh-rTW/user/widget.html#what-it-shows" - },"6677": { + "relUrl": "/nl-rNL/user/widget.html#what-it-shows" + },"6669": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/nl-rNL/user/widget.html#adding-the-widget", - "relUrl": "/zh-rTW/user/widget.html#adding-the-widget" - },"6678": { + "relUrl": "/nl-rNL/user/widget.html#adding-the-widget" + },"6670": { "doc": "Home Screen Widget", - "title": "相關主題", + "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 | 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", + "url": "/Meshtastic-Android/main/nl-rNL/user/widget.html#related-topics", - "relUrl": "/zh-rTW/user/widget.html#相關主題" + "relUrl": "/nl-rNL/user/widget.html#related-topics" + },"6671": { + "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" + },"6672": { + "doc": "Home Screen Widget", + "title": "What It Shows", + "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", + "url": "/Meshtastic-Android/main/sv-rSE/user/widget.html#what-it-shows", + + "relUrl": "/sv-rSE/user/widget.html#what-it-shows" + },"6673": { + "doc": "Home Screen Widget", + "title": "Adding the Widget", + "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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" + },"6674": { + "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 | 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" + },"6675": { + "doc": "ホーム画面ウィジェット", + "title": "ホーム画面ウィジェット", + "content": "Android では、Meshtastic はホーム画面のウィジェットを提供しており、接続中の無線機のライブなローカル統計をひと目で確認できます。アプリを開く必要はありません。 . ", + "url": "/Meshtastic-Android/main/ja-rJP/user/widget.html", + + "relUrl": "/ja-rJP/user/widget.html" + },"6676": { + "doc": "ホーム画面ウィジェット", + "title": "表示される内容", + "content": "ウィジェットは、接続中の無線機の現在のローカル統計を表示します： . | Battery：無線機のバッテリー残量。外部電源で動作している場合は Powered（給電中） | ChUtil：チャンネル利用率（LoRa チャンネルがどれだけ混雑しているかを割合で表示） | AirUtil：電波利用率（無線機がデューティサイクルのうちどれだけ送信しているか） | Traffic：送受信したパケットと、検出した重複 | Relays：中継したパケットと、中継のキャンセル（無線機が中継しているときに表示） | . ウィジェットをタップするとアプリが開きます。更新コントロールを使うと、最新の統計を要求できます。 . 💡 ヒント： 値は、現在接続している無線機を反映します。 アプリが無線機に接続していない場合、ウィジェットは再接続するまで、最後に分かっている統計を表示します。 . ", + "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#表示される内容" + },"6677": { + "doc": "ホーム画面ウィジェット", + "title": "ウィジェットを追加する", + "content": ". | Android のホーム画面の空いている場所を長押しします。 | 「ウィジェット」をタップします。 | リストで Meshtastic を見つけ、「Local Stats」ウィジェットをホーム画面にドラッグします。 | 必要に応じてサイズを変更します。レイアウトは利用可能なスペースに合わせて調整されます。 | . ⚠️ 注意： このウィジェットは Android 専用です。 デスクトップ版や 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#ウィジェットを追加する" + },"6678": { + "doc": "ホーム画面ウィジェット", + "title": "関連トピック", + "content": ". | ノードメトリクス：アプリ内の完全な信号品質とローカル統計の履歴 | コネクション：ウィジェットに表示する統計が得られるよう、無線機に接続する | 探索：メッシュ全体のチャンネル利用率と電波利用率 | . ", + "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#関連トピック" },"6679": { "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/cs-rCZ/user/widget.html", + "url": "/Meshtastic-Android/main/hu-rHU/user/widget.html", - "relUrl": "/cs-rCZ/user/widget.html" + "relUrl": "/hu-rHU/user/widget.html" },"6680": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/hu-rHU/user/widget.html#what-it-shows", - "relUrl": "/cs-rCZ/user/widget.html#what-it-shows" + "relUrl": "/hu-rHU/user/widget.html#what-it-shows" },"6681": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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/cs-rCZ/user/widget.html#adding-the-widget", + "url": "/Meshtastic-Android/main/hu-rHU/user/widget.html#adding-the-widget", - "relUrl": "/cs-rCZ/user/widget.html#adding-the-widget" + "relUrl": "/hu-rHU/user/widget.html#adding-the-widget" },"6682": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/cs-rCZ/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/hu-rHU/user/widget.html#related-topics", - "relUrl": "/cs-rCZ/user/widget.html#related-topics" + "relUrl": "/hu-rHU/user/widget.html#related-topics" },"6683": { "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", + "url": "/Meshtastic-Android/main/ht-rHT/user/widget.html", - "relUrl": "/fr-rFR/user/widget.html" + "relUrl": "/ht-rHT/user/widget.html" },"6684": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/fr-rFR/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/ht-rHT/user/widget.html#what-it-shows", - "relUrl": "/fr-rFR/user/widget.html#what-it-shows" + "relUrl": "/ht-rHT/user/widget.html#what-it-shows" },"6685": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/ht-rHT/user/widget.html#adding-the-widget", - "relUrl": "/fr-rFR/user/widget.html#adding-the-widget" + "relUrl": "/ht-rHT/user/widget.html#adding-the-widget" },"6686": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/fr-rFR/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/ht-rHT/user/widget.html#related-topics", - "relUrl": "/fr-rFR/user/widget.html#related-topics" + "relUrl": "/ht-rHT/user/widget.html#related-topics" },"6687": { "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", + "url": "/Meshtastic-Android/main/gl-rES/user/widget.html", - "relUrl": "/zh-rCN/user/widget.html" + "relUrl": "/gl-rES/user/widget.html" },"6688": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/zh-rCN/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/gl-rES/user/widget.html#what-it-shows", - "relUrl": "/zh-rCN/user/widget.html#what-it-shows" + "relUrl": "/gl-rES/user/widget.html#what-it-shows" },"6689": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/gl-rES/user/widget.html#adding-the-widget", - "relUrl": "/zh-rCN/user/widget.html#adding-the-widget" + "relUrl": "/gl-rES/user/widget.html#adding-the-widget" },"6690": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/zh-rCN/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/gl-rES/user/widget.html#related-topics", - "relUrl": "/zh-rCN/user/widget.html#related-topics" + "relUrl": "/gl-rES/user/widget.html#related-topics" },"6691": { "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", + "url": "/Meshtastic-Android/main/tr-rTR/user/widget.html", - "relUrl": "/srp/user/widget.html" + "relUrl": "/tr-rTR/user/widget.html" },"6692": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/srp/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/tr-rTR/user/widget.html#what-it-shows", - "relUrl": "/srp/user/widget.html#what-it-shows" + "relUrl": "/tr-rTR/user/widget.html#what-it-shows" },"6693": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/tr-rTR/user/widget.html#adding-the-widget", - "relUrl": "/srp/user/widget.html#adding-the-widget" + "relUrl": "/tr-rTR/user/widget.html#adding-the-widget" },"6694": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/srp/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/tr-rTR/user/widget.html#related-topics", - "relUrl": "/srp/user/widget.html#related-topics" + "relUrl": "/tr-rTR/user/widget.html#related-topics" },"6695": { "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", + "url": "/Meshtastic-Android/main/es-rES/user/widget.html", - "relUrl": "/sq-rAL/user/widget.html" + "relUrl": "/es-rES/user/widget.html" },"6696": { "doc": "Home Screen Widget", "title": "What It Shows", "content": "The widget displays the connected radio’s current local stats: . | 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) | . Tap the widget to open the app, or use its refresh control to request fresh stats. 💡 Tip: The values reflect the radio you are currently connected to. If the app isn’t connected to a radio, the widget shows the last known stats until it reconnects. ", - "url": "/Meshtastic-Android/main/sq-rAL/user/widget.html#what-it-shows", + "url": "/Meshtastic-Android/main/es-rES/user/widget.html#what-it-shows", - "relUrl": "/sq-rAL/user/widget.html#what-it-shows" + "relUrl": "/es-rES/user/widget.html#what-it-shows" },"6697": { "doc": "Home Screen Widget", "title": "Adding the Widget", "content": ". | Long-press an empty area of your Android home screen. | Tap Widgets. | Find Meshtastic in the list and drag the Local Stats widget to your home screen. | 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", + "url": "/Meshtastic-Android/main/es-rES/user/widget.html#adding-the-widget", - "relUrl": "/sq-rAL/user/widget.html#adding-the-widget" + "relUrl": "/es-rES/user/widget.html#adding-the-widget" },"6698": { "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 | Discovery — channel and airtime utilization across the mesh | . ", - "url": "/Meshtastic-Android/main/sq-rAL/user/widget.html#related-topics", + "url": "/Meshtastic-Android/main/es-rES/user/widget.html#related-topics", - "relUrl": "/sq-rAL/user/widget.html#related-topics" + "relUrl": "/es-rES/user/widget.html#related-topics" } } diff --git a/main/en/user.html b/main/en/user.html index a47db0adfe..85406c1fd1 100644 --- a/main/en/user.html +++ b/main/en/user.html @@ -1 +1 @@ - User Guide | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
Meshtastic Docs ↗

User Guide

Documentation for using the Meshtastic Android and Desktop app.

What’s New in the Docs

July 2026 — Discovery — New Mesh Beacon: broadcast invitations to your mesh and receive Mesh invitations from others, with one-tap join or a preset-seeded Discovery scan.

July 2026 — Settings — Radio & User — Security config now offers encrypted on-device key backup/restore and a packet-authenticity Protection Level (Strict / Balanced / Compatible).

July 2026 — MQTT — Documented the “MQTT proxy on this phone” toggle: see whether your phone is relaying MQTT for the node and cut it off immediately.

July 2026 — Map & Waypoints — Waypoints can now define a geofence: get notified when nodes enter or leave an area. Creator-only by default, with a per-geofence opt-in for others.

July 2026 — Map & Waypoints — Map Layers (import your own .kml/.kmz/GeoJSON overlays) and Site Planner (RF coverage estimation) are now available on F-Droid, not just Google Play.

July 2026 — Nodes — Added a “Nodes per Hop” histogram showing how many nodes sit at each hop distance, filterable to a last-heard time window.

Table of contents

+ User Guide | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
Meshtastic Docs ↗

User Guide

Documentation for using the Meshtastic Android and Desktop app.

What’s New in the Docs

July 2026 — Discovery — New Mesh Beacon: broadcast invitations to your mesh and receive Mesh invitations from others, with one-tap join or a preset-seeded Discovery scan.

July 2026 — Settings — Radio & User — Security config now offers encrypted on-device key backup/restore and a packet-authenticity Protection Level (Strict / Balanced / Compatible).

July 2026 — MQTT — Documented the “MQTT proxy on this phone” toggle: see whether your phone is relaying MQTT for the node and cut it off immediately.

July 2026 — Map & Waypoints — Waypoints can now define a geofence: get notified when nodes enter or leave an area. Creator-only by default, with a per-geofence opt-in for others.

July 2026 — Map & Waypoints — Map Layers (import your own .kml/.kmz/GeoJSON overlays) and Site Planner (RF coverage estimation) are now available on F-Droid, not just Google Play.

July 2026 — Nodes — Added a “Nodes per Hop” histogram showing how many nodes sit at each hop distance, filterable to a last-heard time window.

Table of contents