diff --git a/androidApp/README.md b/androidApp/README.md index 8ba59aa28..60704c4b2 100644 --- a/androidApp/README.md +++ b/androidApp/README.md @@ -25,6 +25,8 @@ The module primarily serves as a "glue" layer, connecting: ```mermaid graph TB :androidApp[androidApp]:::android-application + :androidApp -.-> :baselineprofile + :androidApp -.-> :feature:car :androidApp -.-> :core:ble :androidApp -.-> :core:common :androidApp -.-> :core:data @@ -48,6 +50,7 @@ graph TB :androidApp -.-> :feature:map :androidApp -.-> :feature:node :androidApp -.-> :feature:settings + :androidApp -.-> :feature:discovery :androidApp -.-> :feature:docs :androidApp -.-> :feature:firmware :androidApp -.-> :feature:wifi-provision diff --git a/androidApp/src/main/assets/firmware_releases.json b/androidApp/src/main/assets/firmware_releases.json index 280f516b1..063ee50e8 100644 --- a/androidApp/src/main/assets/firmware_releases.json +++ b/androidApp/src/main/assets/firmware_releases.json @@ -200,12 +200,6 @@ "page_url": "https://github.com/meshtastic/firmware/pull/10729", "zip_url": "https://img.shields.io/badge/Flash_this_PR_in_the_Web_Flasher-2C2D3C?style=for-the-badge" }, - { - "id": "10728", - "title": "Beta fixes", - "page_url": "https://github.com/meshtastic/firmware/pull/10728", - "zip_url": "https://img.shields.io/badge/Flash_this_PR_in_the_Web_Flasher-2C2D3C?style=for-the-badge" - }, { "id": "10726", "title": "Leave src/platform out of the build filter by default", @@ -313,6 +307,18 @@ "title": "Fix BLE advertising management to prevent crashes during reconnections", "page_url": "https://github.com/meshtastic/firmware/pull/10658", "zip_url": "+40.3 KB" + }, + { + "id": "10656", + "title": "UDP Unicast for Meshtasticd", + "page_url": "https://github.com/meshtastic/firmware/pull/10656", + "zip_url": "s" + }, + { + "id": "10633", + "title": "revert a conflict regression and introduce the DCDC workaround ", + "page_url": "https://github.com/meshtastic/firmware/pull/10633", + "zip_url": "s" } ] } \ No newline at end of file diff --git a/core/resources/src/commonMain/composeResources/values-ar/strings.xml b/core/resources/src/commonMain/composeResources/values-ar/strings.xml index 6753ca7a3..e8d0203a2 100644 --- a/core/resources/src/commonMain/composeResources/values-ar/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ar/strings.xml @@ -25,6 +25,7 @@ الإدارة + مطلوب تحديث التطبيق تفعيل هل أنت متيقِّن؟ @@ -68,6 +69,9 @@ الجهاز في وضعية السكون رسالة مباشره انقطع الاتصال + + مباشره + الرسائل إعدادات الشاشة diff --git a/core/resources/src/commonMain/composeResources/values-be/strings.xml b/core/resources/src/commonMain/composeResources/values-be/strings.xml index cfbc8f491..1ad2e1ed2 100644 --- a/core/resources/src/commonMain/composeResources/values-be/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-be/strings.xml @@ -25,6 +25,7 @@ Усе + Праграма Версія Прымяніць @@ -83,6 +84,8 @@ Прыватнае паведамленне Скасаваць змены Адлучана + + Паведамленні Экран diff --git a/core/resources/src/commonMain/composeResources/values-bg/strings.xml b/core/resources/src/commonMain/composeResources/values-bg/strings.xml index 6ed5cbc5b..bb328db3a 100644 --- a/core/resources/src/commonMain/composeResources/values-bg/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-bg/strings.xml @@ -54,6 +54,7 @@ Разширени Разширени + Качество на въздуха Икона за качество на въздуха Модулът за показатели за качеството на въздуха е активиран Интервал на актуализиране на показателите за качеството на въздуха @@ -67,6 +68,7 @@ Анализите се събират, за да ни помогнат да подобрим приложението за Android (благодарим ви). Ще получаваме анонимизирана информация за поведението на потребителите. Това включва отчети за сривове, екрани, използвани в приложението и др. Разрешаване на анализи и докладване за сривове. Аналитични платформи: + Известия от приложението Приложение Изисква се актуализация на приложението @@ -264,6 +266,12 @@ Прекъсване на връзката Прекъсната връзка Открити мрежови устройства + + Използване на канала + Дата + Директно + Съобщения + Избрани Свободен диск %1$d Дисплей @@ -886,6 +894,7 @@ Неизвестен публичен ключ Пакетът е твърде голям RSSI + Индикатор за силата на получения сигнал - измерване, използвано за определяне на нивото на получения сигнал, приемано от антената. По-високата стойност на RSSI обикновено показва по-силна и по-стабилна връзка. rsyslog сървър Сат Запис @@ -962,6 +971,7 @@ Слот Интелигентна позиция SNR + Съотношение сигнал/шум, мярка, използвана в комуникациите за количествено определяне на нивото на желания сигнал спрямо нивото на фоновия шум. В Meshtastic и други безжични системи, по-високото съотношение сигнал/шум показва по-ясен сигнал, който може да подобри надеждността и качеството на предаване на данни. Скорост %1$d Km/h SSID diff --git a/core/resources/src/commonMain/composeResources/values-ca/strings.xml b/core/resources/src/commonMain/composeResources/values-ca/strings.xml index d76a39fc3..3a2a6a999 100644 --- a/core/resources/src/commonMain/composeResources/values-ca/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ca/strings.xml @@ -25,6 +25,7 @@ Afegir + Actualització de l'aplicació necessària Aplicar Estàs segur que vols canviar al canal per defecte? @@ -62,6 +63,7 @@ Dispositiu hivernant Missatge directe Desconnectat + Distància diff --git a/core/resources/src/commonMain/composeResources/values-cs/strings.xml b/core/resources/src/commonMain/composeResources/values-cs/strings.xml index 6e5b3ddce..d0de0740c 100644 --- a/core/resources/src/commonMain/composeResources/values-cs/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-cs/strings.xml @@ -67,6 +67,7 @@ Povolit analýzu a hlášení pádů. Analytické nástroje: Vše + Oznámení aplikace Aplikace Aplikace je příliš stará @@ -280,6 +281,11 @@ Odpojit Odpojeno Nalezená síťová zařízení + + Datum + Přímý + Zprávy + Vybrané Obrazovka Obrazovka zařízení @@ -854,6 +860,7 @@ Metriky kvality ovzduší Metriky zařízení Metriky prostředí + Lokální statistiky Metadata Metriky napájení Vyžádat telemetrii @@ -899,6 +906,7 @@ Vypršel čas spojení Příliš velký paket RSSI + Indikátor síly přijímaného signálu, měření, které se používá k určení hladiny výkonu přijímané anténou. Vyšší hodnota RSSI obvykle znamená silnější a stabilnější spojení. rsyslog server Satelitů Uložit @@ -981,6 +989,7 @@ Přeskočit Chytrá poloha SNR + Poměr signálu k šumu (SNR) je veličina používaná k vyjádření poměru mezi úrovní požadovaného signálu a úrovní šumu na pozadí. V Meshtastic a dalších bezdrátových systémech vyšší hodnota SNR značí čistší signál, což může zvýšit spolehlivost a kvalitu přenosu dat. Rychlost SSID Stavová zpráva diff --git a/core/resources/src/commonMain/composeResources/values-de/strings.xml b/core/resources/src/commonMain/composeResources/values-de/strings.xml index ef6387577..4897aa40d 100644 --- a/core/resources/src/commonMain/composeResources/values-de/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-de/strings.xml @@ -86,6 +86,7 @@ Analyse und Absturzberichterstattung erlauben. Analyse Plattformen: Beliebig + App-Benachrichtigungen Anwendung Anwendungsaktualisierung erforderlich @@ -337,6 +338,14 @@ Verbindung trennen Verbindung getrennt Entdeckte Netzwerkgeräte + + Kanalauslastung + Datum + Direkt + Netz + Nachrichten + Ausgewählt + Status Laufwerkspeicher frei %1$d Display @@ -1074,6 +1083,7 @@ Gerätedaten Umweltdaten Host Kennzahlen + Lokale Statistik Metadaten Benutzerzählerdaten Energiedaten @@ -1125,6 +1135,7 @@ Zeitüberschreitung Nachricht zu groß RSSI + Indikator für die empfangene Signalstärke, eine Messung zur Bestimmung der von der Antenne empfangenen Leistungsstärke. Ein höherer RSSI-Wert weist im Allgemeinen auf eine stärkere und stabilere Verbindung hin. rsyslog Server Satelliten Speichern @@ -1217,6 +1228,7 @@ Position Intelligente Position SNR + Signal-Rausch-Verhältnis, ein in der Kommunikation verwendetes Maß, um den Pegel eines gewünschten Signals im Verhältnis zum Pegel des Hintergrundrauschens zu quantifizieren. Bei Meshtastic und anderen drahtlosen Systemen weist ein höheres SNR auf ein klareres Signal hin, das die Zuverlässigkeit und Qualität der Datenübertragung verbessern kann. Bodenfeuchte Bodentemperatur Geschwindigkeit diff --git a/core/resources/src/commonMain/composeResources/values-el/strings.xml b/core/resources/src/commonMain/composeResources/values-el/strings.xml index eaa23c71e..4eab224ba 100644 --- a/core/resources/src/commonMain/composeResources/values-el/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-el/strings.xml @@ -26,6 +26,7 @@ Διαχείριση + Εφαρμογή πολύ παλαιά Εφαρμογή Είστε σίγουροι ότι θέλετε να αλλάξετε στο προεπιλεγμένο κανάλι; @@ -79,6 +80,8 @@ Σημείο Δρόσου Άμεσο Μήνυμα Αποσυνδεδεμένο + + Μηνύματα Οθόνη diff --git a/core/resources/src/commonMain/composeResources/values-es/strings.xml b/core/resources/src/commonMain/composeResources/values-es/strings.xml index 6e5dd3d8f..f10668240 100644 --- a/core/resources/src/commonMain/composeResources/values-es/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-es/strings.xml @@ -60,6 +60,7 @@ Se recopilan analíticas de uso para ayudarnos a mejorar la aplicación Android (¡gracias!), recibiremos información anónima sobre el comportamiento del usuario. Esto incluye reportes de fallos, pantallas utilizadas en la aplicación, etc. Permitir analíticas y reporte de errores. Cualquiera + Notificaciones de la app Es necesario actualizar la aplicación Versión @@ -239,6 +240,11 @@ Desconectar Desconectado Dispositivos de red descubiertos + + Fecha + Directo + Mensajes + Seleccionados Disco libre %1$d Pantalla @@ -691,6 +697,7 @@ Estos datos de ubicación pueden ser utilizados para fines como aparecer en un m Métricas de Dispositivo Métricas de Entorno Métricas del anfitrión + Estadísticas Locales Metadatos Métricas de Energía Solicitar Telemetría @@ -734,6 +741,7 @@ Estos datos de ubicación pueden ser utilizados para fines como aparecer en un m Tiempo agotado Paquete demasiado largo RSSI + Indicador de Fuerza de Señal Recibida (RSSI en inglés), una medida utilizada para determinar el nivel de potencia que está siendo recibido por la antena. Un valor de RSSI más alto generalmente indica una conexión más fuerte y estable. Servidor rsyslog Satélites Guardar @@ -802,6 +810,7 @@ Estos datos de ubicación pueden ser utilizados para fines como aparecer en un m Ranura Ubicación inteligente SNR + SNR: Ratio de señal a ruido, una medida utilizada en las comunicaciones para cuantificar el nivel de una señal deseada respecto al nivel del ruido de fondo. En Meshtastic y otros sistemas inalámbricos, un mayor SNR indica una señal más clara que puede mejorar la fiabilidad y la calidad de la transmisión de datos. Velocidad Factor de dispersión SSID (Nombre la Red) diff --git a/core/resources/src/commonMain/composeResources/values-et/strings.xml b/core/resources/src/commonMain/composeResources/values-et/strings.xml index c92adba3f..60cceb191 100644 --- a/core/resources/src/commonMain/composeResources/values-et/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-et/strings.xml @@ -77,6 +77,7 @@ Luba analüüsi ja krahhi aruandlus. Analüütikaplatvormid: Kõik + Rakenduse märguanded Rakendus Vajalik on rakenduse värskendus @@ -312,6 +313,11 @@ Katkesta ühendus Ühendus katkenud Avastatud seadmed + + Kuupäev + Otsene + Sõnumid + Valitud Vaba kettamaht %1$d Ekraan @@ -1010,6 +1016,7 @@ Seadme mõõdikud Keskkonnamõõdikud Hosti mõõdik + Kohalik statistika Metaandmed Pax mõõdiku küsimine Võimsusnäitajad @@ -1061,6 +1068,7 @@ Aegunud Liiga suur pakett RSSI + Vastuvõetud signaali tugevuse indikaator (RSSI), mõõt mida kasutatakse antenni poolt vastuvõetava võimsustaseme määramiseks. Kõrgem RSSI väärtus näitab üldiselt tugevamat ja stabiilsemat ühendust. rsyslog server Sateliit Salvesta @@ -1153,6 +1161,7 @@ Pesa Nutikas asukoht SNR + Signaali ja müra suhe (SNR) on mõõdik, mida kasutatakse soovitud signaali taseme ja taustamüra taseme vahelise suhte määramisel. Meshtastic ja teistes traadita süsteemides näitab kõrgem signaali ja müra suhe selgemat signaali, mis võib parandada andmeedastuse usaldusväärsust ja kvaliteeti. Pinnase niiskus Pinnase temperatuur Kiirus diff --git a/core/resources/src/commonMain/composeResources/values-fi/strings.xml b/core/resources/src/commonMain/composeResources/values-fi/strings.xml index 2e7defddd..30804be8c 100644 --- a/core/resources/src/commonMain/composeResources/values-fi/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-fi/strings.xml @@ -86,6 +86,7 @@ Salli analytiikka ja virheraportit. Analytiikkapalvelut Milloin tahansa + Sovellusilmoitukset Sovellus Sovelluspäivitys vaaditaan @@ -337,6 +338,13 @@ Katkaise yhteys Ei yhdistetty Löydetyt verkkolaitteet + + Kanavan käyttöaste + Päivä + Suora + Verkko + Viestit + Valittu Vapaa levytila %1$d Näyttö @@ -1057,6 +1065,7 @@ Laitteen mittausloki Ympäristöarvot Isäntälaitteen mittausarvot + Paikalliset tilastot Metatiedot Pax mittarit Virranhallinnan arvot @@ -1108,6 +1117,7 @@ Aikakatkaisu Paketti on liian suuri RSSI + Vastaanotetun signaalin voimakkuusindikaattori (RSSI) on mittari, jota käytetään määrittämään antennilla vastaanotetun signaalin voimakkuus. Korkeampi RSSI-arvo yleensä osoittaa vahvemman ja vakaamman yhteyden. rsyslog-palvelin Satelliitit Tallenna @@ -1200,6 +1210,7 @@ Paikka Älykäs sijainti SNR + Signaali-kohinasuhde (SNR) on mittari, jota käytetään viestinnässä halutun signaalin tason ja taustahälyn tason määrittämisessä. Meshtasticissa ja muissa langattomissa järjestelmissä korkeampi SNR tarkoittaa selkeämpää signaalia, joka voi parantaa tiedonsiirron luotettavuutta ja laatua. Maaperän kosteus Maaperän lämpötila Nopeus diff --git a/core/resources/src/commonMain/composeResources/values-fr/strings.xml b/core/resources/src/commonMain/composeResources/values-fr/strings.xml index 5151611da..aded32aaf 100644 --- a/core/resources/src/commonMain/composeResources/values-fr/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-fr/strings.xml @@ -79,6 +79,7 @@ Autoriser les statistiques et les rapports de plantage. Plateformes d'analyse : N'importe laquelle + Notifications de l’application App Mise à jour de l’application requise @@ -320,6 +321,12 @@ Déconnecter Déconnecté Appareils réseau découverts + + Utilisation du canal + Date + Direct + Messages + Sélectionné Disque libre %1$d Écran @@ -996,6 +1003,7 @@ Métriques de l’appareil Métriques d'environnement Métriques de l’hôte + Statistiques locales Métadonnées Métriques de Pax Métriques d'alimentation @@ -1047,6 +1055,7 @@ Délai dépassé Paquet trop grand RSSI + Indicateur de force du signal reçu, une mesure utilisée pour déterminer le niveau de puissance reçu par l'antenne. Une valeur RSSI plus élevée indique généralement une connexion plus forte et plus stable. Serveur Rsyslog Sats Enregistrer @@ -1139,6 +1148,7 @@ Emplacement Position Intelligente SNR + Signal-to-Noise Ratio, une mesure utilisée dans les communications pour quantifier le niveau du signal par rapport au niveau du bruit de fond. Dans les systèmes Meshtastic et autres systèmes sans fil, un SNR plus élevé indique un signal plus clair qui peut améliorer la fiabilité et la qualité de la transmission de données. Hum sol Temp sol Vitesse diff --git a/core/resources/src/commonMain/composeResources/values-ga/strings.xml b/core/resources/src/commonMain/composeResources/values-ga/strings.xml index 1017ad62e..0ddf03bc0 100644 --- a/core/resources/src/commonMain/composeResources/values-ga/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ga/strings.xml @@ -27,6 +27,7 @@ Céatadán de na hamaitear úsáideach atá in úsáid laistigh de uair an chloig atá caite. + Nuashonrú feidhmchláir riachtanach Cuir i bhfeidhm An bhfuil tú cinnte gur mhaith leat an cainéal réamhshocraithe a athrú? @@ -70,6 +71,8 @@ Gléas ina chodladh Teachtaireacht dhíreach Na ceangailte + + Direach Sáth @@ -235,6 +238,7 @@ Pre-set den x-teirí code Am tráth Pacáiste ró-mhór + Táscaire Cumhachta Athnuachana Aithint an Aoise, tomhas a úsáidtear chun leibhéal cumhachta atá faighte ag an antsnáithe a mheas. Léiríonn RSSI níos airde gnóthachtáil níos laige atá i gceangal seasmhach agus níos láidre. Sábháil Sábháil @@ -249,6 +253,7 @@ Dún Sígneal Cáilíocht na Sígneal + Ráta Sigineal go Torann, tomhas a úsáidtear i gcomhfhreagras chun an leibhéal de shígnéil inmhianaithe agus torann cúlra a mheas. I Meshtastic agus i gcórais gan sreang eile, ciallaíonn SNR níos airde go bhfuil sígneál níos soiléire ann agus ábalta méadú ar chreideamh agus cáilíocht an tarchur sonraí. Téama Dorcha diff --git a/core/resources/src/commonMain/composeResources/values-gl/strings.xml b/core/resources/src/commonMain/composeResources/values-gl/strings.xml index 9f4a3a652..5d291f853 100644 --- a/core/resources/src/commonMain/composeResources/values-gl/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-gl/strings.xml @@ -25,6 +25,7 @@ Engadir + Actualización da aplicación requerida Aplicar Está seguro de que quere cambiar á canle predeterminada? @@ -64,6 +65,7 @@ Dispositivo durmindo Mensaxe directa Desconectado + Distancia diff --git a/core/resources/src/commonMain/composeResources/values-he/strings.xml b/core/resources/src/commonMain/composeResources/values-he/strings.xml index 28dd7f45c..5eebb0d30 100644 --- a/core/resources/src/commonMain/composeResources/values-he/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-he/strings.xml @@ -25,6 +25,7 @@ הוסף + נדרש עדכון של האפליקציה החל לשנות לערוץ ברירת המחדל? @@ -63,6 +64,8 @@ מכשיר במצב שינה הודעה ישירה מנותק + + הודעות מרחק diff --git a/core/resources/src/commonMain/composeResources/values-hr/strings.xml b/core/resources/src/commonMain/composeResources/values-hr/strings.xml index c12519b6e..94fbfcb0b 100644 --- a/core/resources/src/commonMain/composeResources/values-hr/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-hr/strings.xml @@ -25,6 +25,7 @@ Dodaj + Potrebna je nadogradnja aplikacije Potvrdi Jeste li sigurni da želite promijeniti na zadani kanal? @@ -68,6 +69,7 @@ Uređaj je u stanju mirovanja Izravna poruka Odspojeno + Udaljenost diff --git a/core/resources/src/commonMain/composeResources/values-ht/strings.xml b/core/resources/src/commonMain/composeResources/values-ht/strings.xml index 388357946..3c215373d 100644 --- a/core/resources/src/commonMain/composeResources/values-ht/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ht/strings.xml @@ -27,6 +27,7 @@ Pousantaj tan lè transmisyon te itilize nan dènye èdtan an. + Aplikasyon twò ansyen Aplike Eske ou sèten ou vle chanje pou kanal default la? @@ -67,6 +68,8 @@ Aparèy ap dòmi Mesaj dirèk Dekonekte + + Direk Distans @@ -232,6 +235,7 @@ Kle piblik enkoni Tan pase Pake twò gwo + Endikatè Fòs Siynal Resevwa, yon mezi ki itilize pou detèmine nivo pouvwa siynal ki resevwa pa antèn nan. Yon RSSI pi wo jeneralman endike yon koneksyon pi fò ak plis estab. Sove Sove @@ -246,6 +250,7 @@ Fèmen Siynal Kalite Siynal + Rapò Siynal sou Bri, yon mezi ki itilize nan kominikasyon pou mezire nivo siynal vle a kont nivo bri ki nan anviwònman an. Nan Meshtastic ak lòt sistèm san fil, yon SNR pi wo endike yon siynal pi klè ki ka amelyore fyab ak kalite transmisyon done. Tèm Fènwa diff --git a/core/resources/src/commonMain/composeResources/values-hu/strings.xml b/core/resources/src/commonMain/composeResources/values-hu/strings.xml index c4760cf9d..b5956cb84 100644 --- a/core/resources/src/commonMain/composeResources/values-hu/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-hu/strings.xml @@ -62,6 +62,7 @@ Analitika és hibajelentések engedélyezése. Analitikai platformok: Bármely + Alkalmazás-értesítések Alkalmazás Az alkalmazás frissítése szükséges @@ -244,6 +245,11 @@ Leválasztás Szétkapcsolva Felfedezett hálózati eszközök + + Dátum + Közvetlen + Üzenetek + Kijelölve Szabad lemezterület %1$d Kijelző @@ -693,6 +699,7 @@ Levegőminőségi metrikák Eszközmetrikák Környezeti metrikák + Helyi statisztikák Metaadatok Tápellátási metrikák Telemetria kérése @@ -735,6 +742,7 @@ Időtúllépés Túl nagy csomag RSSI + Vett jelerősség-mutató (RSSI): az antenna által vett jel teljesítményszintjének mérése. A magasabb RSSI általában erősebb, stabilabb kapcsolatot jelez. rsyslog szerver Műholdak Mentés @@ -808,6 +816,7 @@ Sávhely Intelligens pozíció SNR + Jel–zaj arány (SNR): a kommunikációban a kívánt jel szintjének és a háttérzaj szintjének aránya. A Meshtastic és más vezeték nélküli rendszerek esetében a magasabb SNR tisztább jelet jelent, ami javítja az adatátvitel megbízhatóságát és minőségét. Sebesség Szórási Faktor SSID diff --git a/core/resources/src/commonMain/composeResources/values-is/strings.xml b/core/resources/src/commonMain/composeResources/values-is/strings.xml index f6501eb4e..67cad057d 100644 --- a/core/resources/src/commonMain/composeResources/values-is/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-is/strings.xml @@ -25,6 +25,7 @@ Bæta við + Uppfærsla á smáforriti nauðsynleg Virkja Ert þú viss um að þú viljir skipta yfir á sjálfgefna rás? @@ -58,6 +59,7 @@ Radíó er í svefnham Bein skilaboð Aftengd + diff --git a/core/resources/src/commonMain/composeResources/values-it/strings.xml b/core/resources/src/commonMain/composeResources/values-it/strings.xml index 856b6f17a..e6877f218 100644 --- a/core/resources/src/commonMain/composeResources/values-it/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-it/strings.xml @@ -62,6 +62,7 @@ Consenti analisi e segnalazione di crash. Piattaforme di analytics: Qualsiasi + Notifiche dell'app App Aggiornamento dell'applicazione necessario @@ -264,6 +265,13 @@ Disconnetti Disconnesso Dispositivi di rete rilevati + + Utilizzo Canale + Data + Diretto + Mesh + Messaggi + Selezionato Disco libero %1$d Schermo @@ -780,6 +788,7 @@ Metriche Dispositivo Metriche Ambientali Metriche Host + Statistiche Locali Metadati Metriche Pax Metriche Alimentazione @@ -827,6 +836,7 @@ Timeout Pacchetto troppo grande RSSI + Indicatore di forza del segnale ricevuto (Received Signal Strength Indicator), una misura utilizzata per determinare il livello di potenza ricevuto dall'antenna. Un valore RSSI più elevato indica generalmente una connessione più forte e più stabile. server rsyslog Sat Salva @@ -901,6 +911,7 @@ Slot Posizione Smart SNR + Rapporto segnale-rumore (Signal-to-Noise Ratio), una misura utilizzata nelle comunicazioni per quantificare il livello di un segnale desiderato rispetto al livello di rumore di fondo. In Meshtastic e in altri sistemi wireless, un SNR più elevato indica un segnale più chiaro che può migliorare l'affidabilità e la qualità della trasmissione dei dati. Umidità del Suolo Temperatura Del Suolo Velocità diff --git a/core/resources/src/commonMain/composeResources/values-ja/strings.xml b/core/resources/src/commonMain/composeResources/values-ja/strings.xml index 327fbc6bd..f52757d63 100644 --- a/core/resources/src/commonMain/composeResources/values-ja/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ja/strings.xml @@ -17,21 +17,38 @@ --> + %1$d ホップ先 同意 謝辞 + メッセージをコピー + メッセージを削除 + 絵文字で返信 + デバイスを選択 + メッセージを選択 + ネットワークを選択 + 返信 + メッセージの状態を表示 アクション + ADC倍率のオーバーライド ADC乗算器のオーバーライド率 追加 + QRコードから次のチャンネルが見つかりました。端末に追加したいチャンネルを選択してください。既存のチャンネルは保持されます。 + ネットワークタイルのソースを追加 + お気に入りに追加 + レイヤーを追加 ローカル MBTiles ファイルを追加する 追加 + 手動でデバイスを追加 ネットレイヤーを追加 アドレス 管理者キー + 管理者キー 管理 高度なデバイス GPS + 空気質 空気品質測定モジュールを有効化 過去1時間以内に送信に使用された通信時間の割合。 @@ -51,6 +68,16 @@ 環境照明設定 分析とクラッシュレポートを許可する。 すべて + + チャンネル情報を取得 + デバイスの状態を取得 + メッシュの状態を取得 + ノードの詳細を取得 + ノードリストを取得 + 最近のメッセージを取得 + 未読の概要を取得 + AIへのアクセスを許可 + メッセージを送信 アプリを更新して下さい。 適用 よろしいですか？ @@ -75,6 +102,7 @@ Bluetooth 設定 計算中… + コールサイン キャンセル Cannedメッセージ Cannedメッセージ設定 @@ -187,6 +215,9 @@ 破棄 切断 切断 + + 直接 + メッセージ 表示 表示モード @@ -576,6 +607,7 @@ タイムアウト パケットが大きすぎます RSSI + 受信信号強度インジケーター（RSSI）は、アンテナで受信している電力レベルを測定するための指標です。一般的にRSSI値が高いほど、より強力で安定した接続を示します。 rsyslogサーバー GPS衛星 保存 @@ -623,6 +655,7 @@ 信号品質 スロット SN比 + 信号対ノイズ比（SN比）は、通信において、目的の信号のレベルを背景ノイズのレベルに対して定量化するために使用される尺度です。Meshtasticや他の無線システムでは、SN比が高いほど信号が鮮明であることを示し、データ伝送の信頼性と品質を向上させることができます。 SSID 状態のブロードキャスト間隔 (秒) 対応済み diff --git a/core/resources/src/commonMain/composeResources/values-ko/strings.xml b/core/resources/src/commonMain/composeResources/values-ko/strings.xml index 12c9d732a..cfb9188fc 100644 --- a/core/resources/src/commonMain/composeResources/values-ko/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ko/strings.xml @@ -44,6 +44,7 @@ 고도 조명 조명 설정 + 앱 업데이트가 필요합니다. 적용 확실합니까? @@ -142,6 +143,10 @@ 다이렉트 메시지 연결 끊기 연결 끊김 + + 날짜 + 직접 연결 + 메시지기기 화면 디스플레이 모드 @@ -482,6 +487,7 @@ 시간 초과됨 패킷 이 너무 큽니다 RSSI + 수신 신호 강도 지표 Received Signal Strength Indicator, RSSI는 안테나가 수신하는 신호의 전력 수준을 측정하는 데 사용되는 지표입니다. RSSI 값이 높을수록 일반적으로 더 강력하고 안정적인 연결을 나타냅니다. rsyslog 서버 인공위성 저장 @@ -525,6 +531,7 @@ 신호 감도 슬롯 SNR + 통신에서 원하는 신호의 수준을 배경 잡음의 수준과 비교하여 정량화하는 데 사용되는 신호 대 잡음비 Signal-to-Noise Ratio, SNR는 Meshtastic와 같은 무선 시스템에서 SNR이 높을수록 더 선명한 신호를 나타내어 데이터 전송의 안정성과 품질을 향상시킬 수 있습니다. SSID 상태 전송 간격 (초) 지원됨 diff --git a/core/resources/src/commonMain/composeResources/values-lt/strings.xml b/core/resources/src/commonMain/composeResources/values-lt/strings.xml index 04836b605..972df1da8 100644 --- a/core/resources/src/commonMain/composeResources/values-lt/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-lt/strings.xml @@ -28,6 +28,7 @@ Procentas eterio laiko naudoto perdavimams per pastarąją valandą. Skambučio simbolis! + Reikalingas programos atnaujinimas Taikyti Ar tikrai norite pakeisti į numatytąjį kanalą? @@ -71,6 +72,8 @@ Įrenginys miega Tiesioginė žinutė Atsijungta + + Tiesiogiai Atstumas diff --git a/core/resources/src/commonMain/composeResources/values-nl/strings.xml b/core/resources/src/commonMain/composeResources/values-nl/strings.xml index 6908a2b63..87ebbe8fd 100644 --- a/core/resources/src/commonMain/composeResources/values-nl/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-nl/strings.xml @@ -34,6 +34,7 @@ Alles Alt Sfeerverlichting + Applicatie bijwerken vereist Toepassen Weet u het zeker? @@ -116,6 +117,9 @@ Privébericht Verbinding verbreken Niet verbonden + + Direct + Berichten Weergave Weergavemodus @@ -385,6 +389,7 @@ Time-Out Pakket te groot RSSI + Ontvangen Signal Sterkte Indicator, een meting gebruikt om het stroomniveau te bepalen dat de antenne ontvangt. Een hogere RSSI-waarde geeft een sterkere en stabielere verbinding aan. rsyslog server Sats Opslaan @@ -416,6 +421,7 @@ Signaalkwaliteit Slot SNR + Signal-to-Noise Ratio, een meeting die wordt gebruikt in de communicatie om het niveau van een gewenst signaal tegenover achtergrondlawaai te kwantificeren. In Meshtastische en andere draadloze systemen geeft een hoger SNR een zuiverder signaal aan dat de betrouwbaarheid en kwaliteit van de gegevensoverdracht kan verbeteren. SSID Ondersteund diff --git a/core/resources/src/commonMain/composeResources/values-no/strings.xml b/core/resources/src/commonMain/composeResources/values-no/strings.xml index c23e17a77..b621418e5 100644 --- a/core/resources/src/commonMain/composeResources/values-no/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-no/strings.xml @@ -28,6 +28,7 @@ Prosent av lufttiden brukt i løpet av den siste timen. Varsel, bjellekarakter! + Applikasjon for gammel Bruk Er du sikker på at du vil endre til standardkanalen? @@ -72,6 +73,8 @@ Enhet sover Direktemelding Frakoblet + + Direkte Distanse @@ -245,6 +248,7 @@ Tidsavbrudd Pakken er for stor RSSI + \"Received Signal Strength Indicator\", en måling som brukes til å bestemme strømnivået som mottas av antennen. Høyere RSSI verdi indikerer generelt en sterkere og mer stabil forbindelse. Lagre Lagre @@ -261,6 +265,7 @@ Signal Signalstyrke SNR + Signal-to-Noise Ratio, et mål som brukes i kommunikasjon for å sette nivået av et ønsket signal til bakgrunnstrøynivået. I Meshtastic og andre trådløse systemer tyder et høyere SNR på et klarere signal som kan forbedre påliteligheten og kvaliteten på dataoverføringen. Tema Mørk diff --git a/core/resources/src/commonMain/composeResources/values-pl/strings.xml b/core/resources/src/commonMain/composeResources/values-pl/strings.xml index 7ab7a560b..0c2136d05 100644 --- a/core/resources/src/commonMain/composeResources/values-pl/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-pl/strings.xml @@ -46,6 +46,7 @@ Zawsze wskazywać na północ Oświetlenie otoczenia Zezwalaj na analizę i raportowanie awarii. + Powiadomienia aplikacji Aplikacja Konieczna aktualizacja aplikacji @@ -220,6 +221,12 @@ Odrzuć Rozłącz Rozłączono + + Wykorzystanie kanału + Data + Bezpośrednio + Wiadomości + Wybrane Wyświetlacz Ustawienia wyświetlacza @@ -630,6 +637,7 @@ Metryka urządzenia Metryki środowiskowe Statystyki hosta + Statystyki lokalne Metadane Metryki zasilania Żądanie telemetrii @@ -672,6 +680,7 @@ Upłynął limit czasu Pakiet jest zbyt duży RSSI: + Received Signal Strength Indicator - miara używana do określenia poziomu mocy odbieranej przez antenę. Wyższa wartość RSSI zazwyczaj oznacza silniejsze i bardziej stabilne połączenie. Serwer rsyslog Zapisz Zapisz @@ -725,6 +734,7 @@ Pomiń Inteligentne Pozycjonowanie SNR: + Współczynnik sygnału do szumu (Signal-to-Noise Ratio) - miara stosowana w komunikacji do określania poziomu pożądanego sygnału w stosunku do poziomu szumu tła. W Meshtastic i innych systemach bezprzewodowych wyższy współczynnik SNR oznacza czystszy sygnał, który może zwiększyć niezawodność i jakość transmisji danych. Prędkość SSID Obsługiwane diff --git a/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml b/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml index 162a7fa72..796b8953b 100644 --- a/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml @@ -46,6 +46,7 @@ Alt Luz Ambiente Configuração de Iluminação Ambiente + Notificações do Aplicativo Atualização do aplicativo necessária Aplicar @@ -176,6 +177,10 @@ Desconectar Desconectado Dispositivos de Rede Descobertos + + Data + Direto + Mensagens Disco Livre %1$d Tela @@ -580,6 +585,7 @@ Tempo esgotado Pacote grande demais RSSI + Indicador de Força de Sinal Recebido, uma medida usada para determinar o nível de potência que está sendo recebida pela antena. Um valor maior de RSSI geralmente indica uma conexão mais forte e mais estável. Servidor rsyslog Sats Salvar @@ -643,6 +649,7 @@ Pular Slot SNR + Relação sinal-para-ruído, uma medida utilizada nas comunicações para quantificar o nível de um sinal desejado para o nível de ruído de fundo. Na Meshtastic e outros sistemas sem fios, uma SNR maior indica um sinal mais claro que pode melhorar a confiabilidade e a qualidade da transmissão de dados. Velocidade SSID Transmissão de estado (segundos) diff --git a/core/resources/src/commonMain/composeResources/values-pt/strings.xml b/core/resources/src/commonMain/composeResources/values-pt/strings.xml index 8fe139f92..2fe0923d6 100644 --- a/core/resources/src/commonMain/composeResources/values-pt/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-pt/strings.xml @@ -46,6 +46,7 @@ Altitude Iluminação ambiente Configuração da Iluminação Ambiente + A aplicação é muito antiga Aplicar Confirma? @@ -145,6 +146,9 @@ Mensagem direta Desligar Desconectado + + Direto + Mensagens Ecrã Modo de visualização @@ -469,6 +473,7 @@ Timeout Pacote demasiado grande RSSI + Indicador de Força de Sinal Recebido, uma medida usada para determinar o nível de energia que está a ser recebido pela antena. Um valor mais elevado de RSSI geralmente indica uma conexão mais forte e mais estável. servidor rsyslog Sats Salvar @@ -508,6 +513,7 @@ Slot Posição Inteligente SNR + Relação sinal-para-ruído, uma medida utilizada nas comunicações para quantificar o nível de um sinal desejado com o nível de ruído de fundo. Em Meshtastic e outros sistemas sem fio. Quanto mais alta for a relação sinal-ruído, menor é o efeito do ruído de fundo sobre a deteção ou medição do sinal. SSID Transmissão de estado (segundos) Suportado diff --git a/core/resources/src/commonMain/composeResources/values-ro/strings.xml b/core/resources/src/commonMain/composeResources/values-ro/strings.xml index 5db52da18..dc1f9d56b 100644 --- a/core/resources/src/commonMain/composeResources/values-ro/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ro/strings.xml @@ -67,6 +67,7 @@ Permiteți analiza și raportări de erori. Platforme analitice: Oricare + Notificări aplicații Aplicaţie Aplicație prea veche @@ -288,6 +289,11 @@ Deconectați Deconectat Dispozitive ale rețelei descoperite + + Dată + Direct + Mesaje + Selectat Disc liber %1$d Ecran @@ -946,6 +952,7 @@ Expirat Pachet prea mare RSSI + Indicatorul intensității semnalului recepționat (Received Signal Strength Indicator), o măsurătoare utilizată pentru a determina nivelul de putere recepționat de antenă. O valoare RSSI mai mare indică, în general, o conexiune mai puternică și mai stabilă. server rsyslog Sateliți Salvează @@ -1032,6 +1039,7 @@ Slot Poziție inteligentă SNR + Raportul semnal-zgomot (Signal-to-Noise Ratio), o măsură utilizată în comunicații pentru a cuantifica nivelul unui semnal dorit în raport cu nivelul zgomotului de fond. În Meshtastic și în alte sisteme wireless, un SNR mai mare indică un semnal mai clar, care poate îmbunătăți fiabilitatea și calitatea transmiterii datelor. Umid sol Temp sol Viteza diff --git a/core/resources/src/commonMain/composeResources/values-ru/strings.xml b/core/resources/src/commonMain/composeResources/values-ru/strings.xml index 93bdc8727..a6302b5d7 100644 --- a/core/resources/src/commonMain/composeResources/values-ru/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ru/strings.xml @@ -84,6 +84,7 @@ Разрешить аналитику и отчеты о сбоях. Платформы для аналитики: Любой + Уведомления приложений Приложение Требуется обновление приложения @@ -337,6 +338,12 @@ Отключиться Отключено Найденные сетевые устройства + + Использование канала + Дата + Прямой + Сообщения + Выбрано Свободно на диске %1$d Дисплей @@ -1085,6 +1092,7 @@ Метрики устройства Метрики окружения Метрики хоста + Локальная статистика Метаданные Метрика прохожих Метрики мощности @@ -1136,6 +1144,7 @@ Время ожидания истекло Пакет слишком велик RSSI + Индикатор уровня принимаемого сигнала, измерение, используемое для определения уровня мощности, принимаемой антенной. Более высокое значение RSSI обычно указывает на более сильное и стабильное соединение. Сервер rsyslog Количество спутников Сохранить @@ -1228,6 +1237,7 @@ Слот Умная позиция Сигнал/шум + Соотношение сигнал/шум, мера, используемая в коммуникациях для количественной оценки уровня желаемого сигнала по отношению к уровню фонового шума. В Meshtastic и других беспроводных системах более высокий SNR указывает на более четкий сигнал, который может повысить надежность и качество передачи данных. Влажн почвы Темп почвы Скорость diff --git a/core/resources/src/commonMain/composeResources/values-sk/strings.xml b/core/resources/src/commonMain/composeResources/values-sk/strings.xml index 39834a1e0..961ffe0f4 100644 --- a/core/resources/src/commonMain/composeResources/values-sk/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-sk/strings.xml @@ -34,6 +34,7 @@ Ambientné osvetlenie Nastavenie Ambientného Osvetlenia Povoliť posielanie analytiky a chybových hlásení. + Aplikáciu je potrebné aktualizovať Použiť Si si istý? @@ -128,6 +129,9 @@ Priama správa Vymazať Odpojené + + Priamo + Správy Obrazovka @@ -408,6 +412,7 @@ Časový limit Príliš veľký paket RSSI + Indikátor sily prijímaného signálu (RSSI), meranie používané na určenie úrovne výkonu prijatého skrz anténu. Vyššia hodnota RSSI vo všeobecnosti znamená silnejšie a stabilnejšie pripojenie. Uložiť Uložiť @@ -431,6 +436,7 @@ Kvalita signálu Inteligentná poloha SNR + Pomer signálu od šumu (SNR), miera používaná v komunikácii na kvantifikáciu úrovne požadovaného signálu k úrovni hluku pozadia. V Meshtastic a iných bezdrôtových systémoch znamená vyšší SNR jasnejší signál, ktorý môže zvýšiť spoľahlivosť a kvalitu prenosu údajov. Rýchlosť SSID Podporované diff --git a/core/resources/src/commonMain/composeResources/values-sl/strings.xml b/core/resources/src/commonMain/composeResources/values-sl/strings.xml index c42ec8dc6..4e335fe14 100644 --- a/core/resources/src/commonMain/composeResources/values-sl/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-sl/strings.xml @@ -28,6 +28,7 @@ Odstotek časa oddajanja v zadnji uri. Znak opozorilnega zvonca! + Aplikacija je prestara Uporabi Ali si prepričan spremeni na osnovno? @@ -74,6 +75,8 @@ Naprava je v \"spanju\" Direktno sporočilo Prekinjeno + + Neposreden Razdalja @@ -247,6 +250,7 @@ Časovna omejitev Paketek je prevelik RSSI + Indikator moči sprejetega signala je meritev, ki se uporablja za določanje ravni moči, ki jo sprejema antena. Višja vrednost RSSI na splošno pomeni močnejšo in stabilnejšo povezavo. Shrani Shrani @@ -263,6 +267,7 @@ Signal Kakovost signala SNR + Razmerje med signalom in šumom je merilo, ki se uporablja v komunikacijah za količinsko opredelitev ravni želenega signala glede na raven hrupa v ozadju. V Meshtastic in drugih brezžičnih sistemih višji SNR pomeni jasnejši signal, ki lahko poveča zanesljivost in kakovost prenosa podatkov. Tema Temna tema diff --git a/core/resources/src/commonMain/composeResources/values-sq/strings.xml b/core/resources/src/commonMain/composeResources/values-sq/strings.xml index 67cbf977b..c08557873 100644 --- a/core/resources/src/commonMain/composeResources/values-sq/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-sq/strings.xml @@ -27,6 +27,7 @@ Përqindja e kohës së përdorur për transmetim brenda orës së kaluar. + Përditësimi i aplikacionit kërkohet Apliko A jeni të sigurt se doni të kaloni në kanalin e parazgjedhur? @@ -67,6 +68,9 @@ Pajisja po fle Mesazh i drejtpërdrejtë I shkëputur + + Direkt + 訊息 Distanca @@ -233,6 +237,7 @@ Çelësi publik i panjohur Koha e skaduar Paketa shumë e madhe + Indikatori i Fuqisë së Sinjalit të Marrë, një matje e përdorur për të përcaktuar nivelin e energjisë që po merret nga antena. Një vlerë më e lartë RSSI zakonisht tregon një lidhje më të fortë dhe më të qëndrueshme. Ruaj Ruaj @@ -247,6 +252,7 @@ Fik Sinjal Cilësia e Sinjalit + Raporti i Sinjalit në Zhurmë, një masë e përdorur në komunikime për të kuantifikuar nivelin e një sinjali të dëshiruar ndaj nivelit të zhurmës në background. Në Meshtastic dhe sisteme të tjera pa tel, një SNR më i lartë tregon një sinjal më të pastër që mund të rrisë besueshmërinë dhe cilësinë e transmetimit të të dhënave. Temë Errësirë diff --git a/core/resources/src/commonMain/composeResources/values-sr/strings.xml b/core/resources/src/commonMain/composeResources/values-sr/strings.xml index ca22b7cd8..4852af4ba 100644 --- a/core/resources/src/commonMain/composeResources/values-sr/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-sr/strings.xml @@ -40,6 +40,7 @@ Увек усмеравајте на север Амбијентално осветљење Подешавања амбијенталног осветљења + Nepohodno je ažuriranje aplikacije Примени Да ли сте сигурни? @@ -140,6 +141,10 @@ Директне поруке Прекините везу Raskačeno + + Датум + Direktno + Поруке Приказ @@ -407,6 +412,7 @@ Isteklo vreme Paket prevelik RSSI + Indikator jačine primljenog signala RSSI, merenje koje se koristi za određivanje nivoa snage koji antena prima. Viša vrednost RSSI generalno ukazuje na jaču i stabilniju vezu. Сателита Сачувај Сачувај @@ -435,6 +441,7 @@ Kvalitet signala Паметно позиционирање SNR + Однос сигнал/шум SNR је мера која се користи у комуникацијама за квантитативно одређивање нивоа жељеног сигнала у односу на ниво позадинског шума. У Мештастик и другим бежичним системима, већи SNR указује на јаснији сигнал који може побољшати поузданост и квалитет преноса података. Брзина Фактор ширења Подржан diff --git a/core/resources/src/commonMain/composeResources/values-srp/strings.xml b/core/resources/src/commonMain/composeResources/values-srp/strings.xml index fe3a79090..de13c628c 100644 --- a/core/resources/src/commonMain/composeResources/values-srp/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-srp/strings.xml @@ -40,6 +40,7 @@ Увек усмеравајте на север Амбијентално осветљење Подешавања амбијенталног осветљења + Неопходно је ажурирање апликације Примени Да ли сте сигурни? @@ -140,6 +141,10 @@ Директне поруке Прекините везу Раскачено + + Датум + Директно + Поруке Приказ @@ -407,6 +412,7 @@ Истекло време Пакет превелик RSSI + Индикатор јачине примљеног сигнала RSSI је мера која се користи за одређивање нивоа снаге која се прима преко антене. Виша вредност RSSI генерално указује на јачу и стабилнију везу. Сателита Сачувај Сачувај @@ -435,6 +441,7 @@ Квалитет сигнала Паметно позиционирање SNR + Однос сигнал/шум SNR је мера која се користи у комуникацијама за квантитативно одређивање нивоа жељеног сигнала у односу на ниво позадинског шума. У Мештастик и другим бежичним системима, већи SNR указује на јаснији сигнал који може побољшати поузданост и квалитет преноса података. Брзина Фактор ширења Подржан diff --git a/core/resources/src/commonMain/composeResources/values-sv/strings.xml b/core/resources/src/commonMain/composeResources/values-sv/strings.xml index f1a430875..ad4f61bdc 100644 --- a/core/resources/src/commonMain/composeResources/values-sv/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-sv/strings.xml @@ -79,6 +79,7 @@ Tillåt analys och kraschrapportering. Analysplattformar: Valfri + Appens aviseringar App Applikationen måste uppgraderas @@ -304,6 +305,12 @@ Koppla från Frånkopplad Upptäckta nätverksenheter + + Kanalutnyttjande + Datum + Direkt + Meddelanden + Vald Ledigt lagringutrymme %1$d Display @@ -898,6 +905,7 @@ Enhetens mätvärden Miljövärden Begär värdens värden + Lokal statistik Metadata Strömdata Begär telemetri @@ -944,6 +952,7 @@ Timeout Paket för stort RSSI + Received Signal Strength Indicator, ett mått som används för att avgöra effektnivån som togs emot av antennen. Ett högre RSSI-värde indikerar generellt en starkare och stabilare anslutning. rsyslog-server Sat. Spara @@ -1033,6 +1042,7 @@ Lucka Smart position SNR + Signal-to-Noise Ratio, är ett mått som används inom kommunikation för att kvantifiera nivån av en önskad signal mot nivån av bakgrundsbrus. I Meshtastic och andra trådlösa system indikerar en högre SNR en tydligare signal som kan förbättra tillförlitligheten och kvaliteten på dataöverföringen. Fukthalt i jord Markens temperatur Hastighet diff --git a/core/resources/src/commonMain/composeResources/values-tr/strings.xml b/core/resources/src/commonMain/composeResources/values-tr/strings.xml index 3d8ef9260..5ef5c4798 100644 --- a/core/resources/src/commonMain/composeResources/values-tr/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-tr/strings.xml @@ -49,6 +49,7 @@ Rakım Ortam Işıklandırması Ortam Işıklandırma Ayarı + Uygulama güncellemesi gerekli Uygula Emin misiniz? @@ -151,6 +152,11 @@ Direkt Mesaj Bağlantıyı Kes Bağlantı kesildi + + Tarih + Doğrudan + Amatör Telsiz + Mesajlar Ekran Görüntü Modu @@ -491,6 +497,7 @@ Zaman Aşımı Paket çok büyük RSSI + Alınan Sinyal Gücü Göstergesi, anten tarafından alınan güç seviyesini belirlemek için kullanılan bir ölçüdür. Daha yüksek bir RSSI değeri genellikle daha güçlü ve daha istikrarlı bir bağlantıya işaret eder. rsyslog sunucusu Uydular Kaydet @@ -533,6 +540,7 @@ Atla Yuva SNR + Sinyal-Gürültü Oranı, iletişimde istenen bir sinyalin seviyesini arka plan gürültüsü seviyesine mukayese ölçmek için kullanılan bir ölçüdür. Meshtastic ve diğer kablosuz sistemlerde, daha yüksek bir SNR, veri iletiminin güvenilirliğini ve kalitesini artırabilecek daha net bir sinyale işaret eder. SSID Durum yayını (saniye) Desteklenen diff --git a/core/resources/src/commonMain/composeResources/values-uk/strings.xml b/core/resources/src/commonMain/composeResources/values-uk/strings.xml index e3884cea2..c9b2ed65b 100644 --- a/core/resources/src/commonMain/composeResources/values-uk/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-uk/strings.xml @@ -67,6 +67,7 @@ Дозволити аналітику і звіти про збої Аналітичні платформи: Будь-який + Сповіщення застосунку Застосунок Потрібне оновлення програми @@ -277,6 +278,11 @@ Від'єднатись Відключено Виявлені мережеві пристрої + + Дата + Прямий + Повідомлення + Вибраний Вільне місце %1$d Дисплей @@ -907,6 +913,7 @@ Показники пристрою Екологічні показники Показники хоста + Локальна статистика Метадані Показники Pax Показники живлення @@ -957,6 +964,7 @@ Таймаут Пакет завеликий RSSI + Показник рівня потужності сигналу — вимірювання, що використовується для визначення рівня потужності, що приймається антеною. Вище значення RSSI зазвичай вказує на міцніше та стабільніше з'єднання. rsyslog-сервер Супутники Зберегти diff --git a/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml b/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml index 421bffde3..e957dcdb7 100644 --- a/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml @@ -68,6 +68,7 @@ 报告崩溃信息 分析平台： 任意内容 + 应用通知 App 需要更新应用程序 @@ -290,6 +291,12 @@ 断开 已断开连接 发现的网络设备 + + 频道使用 + 日期 + 直频 + 消息 + 选择 存储空间剩余 %1$d 显示 @@ -888,6 +895,7 @@ 设备指标 传感器指标 主机测量 + 本地统计数据 元数据 Pax 计量 电源计量日志 @@ -935,6 +943,7 @@ 超时 数据包过大 RSSI + 接收信号强度指示（Received Signal Strength Indicator, RSSI）是一种用于测量天线接收到的信号功率的指标。较高的 RSSI 值通常表示更强、更稳定的连接。 rsyslog 服务器 卫星 保存 @@ -1017,6 +1026,7 @@ 槽位 智能位置 SNR + 信噪比（Signal-to-Noise Ratio, SNR）是一种用于通信领域的测量指标，用于量化目标信号与背景噪声的比例。在 Meshtastic 及其他无线系统中，较高的信噪比表示信号更加清晰，从而能够提升数据传输的可靠性和质量。 土壤湿度 土壤温度 速度 diff --git a/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml b/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml index 0f1f7f02a..d8e458410 100644 --- a/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml @@ -86,6 +86,7 @@ 允許傳送分析及崩潰報告。 分析平台： 所有 + 應用程式通知 App 需要應用程式更新 @@ -336,6 +337,13 @@ 中斷連線 已中斷連線 發現的網路裝置 + + 頻道使用率 + 日期 + 直線 + 網狀網路 (Mesh) + 訊息 + 已選取 硬碟可用空間：%1$d 顯示 @@ -1067,6 +1075,7 @@ 裝置計量資料 環境計量資料 主機資訊 + 本機統計資料 中繼資料 人流計量資料 電源計量資料 @@ -1118,6 +1127,7 @@ 逾時 封包過大 RSSI + 接收信號強度指示（RSSI）用於測量天線所接收到信號的功率強度。 RSSI 值越高通常代表連線越強且穩定。 rsyslog伺服器 衛星數 儲存 @@ -1210,6 +1220,7 @@ 時隙 智慧定位 SNR + 信噪比（SNR），用於通訊中量化所需信號與背景噪音水平的指標。在 Meshtastic 及其他無線系統中，信噪比越高表示信號越清晰，可以提高數據傳輸的可靠性和品質。 土壤濕度 土壤溫度 速度 diff --git a/docs/ar-rSA/user/android-auto.md b/docs/ar-rSA/user/android-auto.md new file mode 100644 index 000000000..26aeb6e30 --- /dev/null +++ b/docs/ar-rSA/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## الرسائل + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/ar-rSA/user/app-functions.md b/docs/ar-rSA/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/ar-rSA/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/ar-rSA/user/desktop.md b/docs/ar-rSA/user/desktop.md index 8b20adbd8..718964767 100644 --- a/docs/ar-rSA/user/desktop.md +++ b/docs/ar-rSA/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| الخريطة | ✓ | ✓ | Full parity | -| الإعدادات | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| الخريطة | ✓ | ✓ | Full parity | +| الإعدادات | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/ar-rSA/user/discovery.md b/docs/ar-rSA/user/discovery.md index 1c5d754a9..dd9d2b83d 100644 --- a/docs/ar-rSA/user/discovery.md +++ b/docs/ar-rSA/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/ar-rSA/user/messages-and-channels.md b/docs/ar-rSA/user/messages-and-channels.md index 6a2f1f33a..f50140d44 100644 --- a/docs/ar-rSA/user/messages-and-channels.md +++ b/docs/ar-rSA/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/ar-rSA/user/node-metrics.md b/docs/ar-rSA/user/node-metrics.md index 3382c1c69..bd74015b3 100644 --- a/docs/ar-rSA/user/node-metrics.md +++ b/docs/ar-rSA/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | الوصف | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | الوصف | -| ------------------ | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| مؤشر القوة النسبية | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | مناسب | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/ar-rSA/user/nodes.md b/docs/ar-rSA/user/nodes.md index 072d0429b..ddf7d7232 100644 --- a/docs/ar-rSA/user/nodes.md +++ b/docs/ar-rSA/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | آخر ظهور | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | المسافة | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/ar-rSA/user/telemetry-and-sensors.md b/docs/ar-rSA/user/telemetry-and-sensors.md index 06043670c..0706f75e3 100644 --- a/docs/ar-rSA/user/telemetry-and-sensors.md +++ b/docs/ar-rSA/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/be-rBY/user/android-auto.md b/docs/be-rBY/user/android-auto.md new file mode 100644 index 000000000..c0c7b7903 --- /dev/null +++ b/docs/be-rBY/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Абзор + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Паведамленні + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/be-rBY/user/app-functions.md b/docs/be-rBY/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/be-rBY/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/be-rBY/user/desktop.md b/docs/be-rBY/user/desktop.md index 73b5d6fe1..4d2d32364 100644 --- a/docs/be-rBY/user/desktop.md +++ b/docs/be-rBY/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Налады | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Налады | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/be-rBY/user/discovery.md b/docs/be-rBY/user/discovery.md index 1c5d754a9..3c4c3630b 100644 --- a/docs/be-rBY/user/discovery.md +++ b/docs/be-rBY/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/be-rBY/user/messages-and-channels.md b/docs/be-rBY/user/messages-and-channels.md index a082125f0..2f3af2b19 100644 --- a/docs/be-rBY/user/messages-and-channels.md +++ b/docs/be-rBY/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/be-rBY/user/node-metrics.md b/docs/be-rBY/user/node-metrics.md index 756195a3b..7e1069156 100644 --- a/docs/be-rBY/user/node-metrics.md +++ b/docs/be-rBY/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Апісанне | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Апісанне | -| ------------------- | ----------------------------------------------------------------------------- | -| сігнал-шум | Signal-to-Noise Ratio (higher is better) | -| адносная магутнасць | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Fair | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/be-rBY/user/nodes.md b/docs/be-rBY/user/nodes.md index 370003326..444c3a239 100644 --- a/docs/be-rBY/user/nodes.md +++ b/docs/be-rBY/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Апошні раз пачуты | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Адлегласць | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/be-rBY/user/telemetry-and-sensors.md b/docs/be-rBY/user/telemetry-and-sensors.md index 77ebb485e..6dad0db48 100644 --- a/docs/be-rBY/user/telemetry-and-sensors.md +++ b/docs/be-rBY/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/bg-rBG/user/android-auto.md b/docs/bg-rBG/user/android-auto.md new file mode 100644 index 000000000..d3b1df911 --- /dev/null +++ b/docs/bg-rBG/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: Ръководство за потребители +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Общ преглед + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Съобщения + +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. + +## Възли + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/bg-rBG/user/app-functions.md b/docs/bg-rBG/user/app-functions.md new file mode 100644 index 000000000..c79b5ab60 --- /dev/null +++ b/docs/bg-rBG/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: Ръководство за потребители +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/bg-rBG/user/desktop.md b/docs/bg-rBG/user/desktop.md index b5a248140..e23be99c4 100644 --- a/docs/bg-rBG/user/desktop.md +++ b/docs/bg-rBG/user/desktop.md @@ -2,7 +2,7 @@ title: Настолно приложение parent: Ръководство за потребители nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Бележки | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Карта | ✓ | ✓ | Full parity | -| Настройки | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Известия | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Бележки | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Карта | ✓ | ✓ | Full parity | +| Настройки | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Известия | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/bg-rBG/user/discovery.md b/docs/bg-rBG/user/discovery.md index 1699b5c66..6c17c5806 100644 --- a/docs/bg-rBG/user/discovery.md +++ b/docs/bg-rBG/user/discovery.md @@ -2,8 +2,8 @@ title: Откриване parent: Ръководство за потребители nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Трасиране на маршрут 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. diff --git a/docs/bg-rBG/user/messages-and-channels.md b/docs/bg-rBG/user/messages-and-channels.md index 6595bbc7a..484f0c82a 100644 --- a/docs/bg-rBG/user/messages-and-channels.md +++ b/docs/bg-rBG/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Съобщения & Канали parent: Ръководство за потребители nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - канали - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/bg-rBG/user/node-metrics.md b/docs/bg-rBG/user/node-metrics.md index f2fa3805a..b8ca7963f 100644 --- a/docs/bg-rBG/user/node-metrics.md +++ b/docs/bg-rBG/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: Ръководство за потребители nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Метрични | Unit | Описание | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Метрични | Описание | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| Метрични | Описание | +| ----------- | ------------------------------------------------------------------------------ | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Задоволителен | | < -10 dB | Poor | +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. + ## Показатели на мощност Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/bg-rBG/user/nodes.md b/docs/bg-rBG/user/nodes.md index e5ee164ed..b5123f90d 100644 --- a/docs/bg-rBG/user/nodes.md +++ b/docs/bg-rBG/user/nodes.md @@ -2,7 +2,7 @@ title: Възли parent: Ръководство за потребители nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Последно чут | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Разстояние | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/bg-rBG/user/telemetry-and-sensors.md b/docs/bg-rBG/user/telemetry-and-sensors.md index 66e0908fa..59b3d3b89 100644 --- a/docs/bg-rBG/user/telemetry-and-sensors.md +++ b/docs/bg-rBG/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/ca-rES/user/android-auto.md b/docs/ca-rES/user/android-auto.md new file mode 100644 index 000000000..aeb53435d --- /dev/null +++ b/docs/ca-rES/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Messages + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/ca-rES/user/app-functions.md b/docs/ca-rES/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/ca-rES/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/ca-rES/user/desktop.md b/docs/ca-rES/user/desktop.md index 1af615e66..e69b44554 100644 --- a/docs/ca-rES/user/desktop.md +++ b/docs/ca-rES/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Settings | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Settings | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/ca-rES/user/discovery.md b/docs/ca-rES/user/discovery.md index 29d093e90..7b0d38b0a 100644 --- a/docs/ca-rES/user/discovery.md +++ b/docs/ca-rES/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traçar ruta Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/ca-rES/user/messages-and-channels.md b/docs/ca-rES/user/messages-and-channels.md index db5c65cd5..80abc655c 100644 --- a/docs/ca-rES/user/messages-and-channels.md +++ b/docs/ca-rES/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/ca-rES/user/node-metrics.md b/docs/ca-rES/user/node-metrics.md index f20f2e8d2..125766d97 100644 --- a/docs/ca-rES/user/node-metrics.md +++ b/docs/ca-rES/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | 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 | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Descripció | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Fair | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/ca-rES/user/nodes.md b/docs/ca-rES/user/nodes.md index 2ca75c89a..19e2615bf 100644 --- a/docs/ca-rES/user/nodes.md +++ b/docs/ca-rES/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Última notícia | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distància | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/ca-rES/user/telemetry-and-sensors.md b/docs/ca-rES/user/telemetry-and-sensors.md index 18547239b..cd6266f62 100644 --- a/docs/ca-rES/user/telemetry-and-sensors.md +++ b/docs/ca-rES/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/cs-rCZ/user/android-auto.md b/docs/cs-rCZ/user/android-auto.md new file mode 100644 index 000000000..1fc773832 --- /dev/null +++ b/docs/cs-rCZ/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: Uživatelská příručka +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Zprávy + +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. + +## Uzly + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/cs-rCZ/user/app-functions.md b/docs/cs-rCZ/user/app-functions.md new file mode 100644 index 000000000..9e9270512 --- /dev/null +++ b/docs/cs-rCZ/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: Uživatelská příručka +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/cs-rCZ/user/desktop.md b/docs/cs-rCZ/user/desktop.md index 2b9436f81..190136d53 100644 --- a/docs/cs-rCZ/user/desktop.md +++ b/docs/cs-rCZ/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Poznámka | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Mapa | ✓ | ✓ | Full parity | -| Nastavení | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Poznámka | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Mapa | ✓ | ✓ | Full parity | +| Nastavení | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/cs-rCZ/user/discovery.md b/docs/cs-rCZ/user/discovery.md index ce4b41580..fa769debc 100644 --- a/docs/cs-rCZ/user/discovery.md +++ b/docs/cs-rCZ/user/discovery.md @@ -2,8 +2,8 @@ title: Objevujte parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/cs-rCZ/user/messages-and-channels.md b/docs/cs-rCZ/user/messages-and-channels.md index 0c3d2003b..e180797ed 100644 --- a/docs/cs-rCZ/user/messages-and-channels.md +++ b/docs/cs-rCZ/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/cs-rCZ/user/node-metrics.md b/docs/cs-rCZ/user/node-metrics.md index 874f3e153..20d6ca6a0 100644 --- a/docs/cs-rCZ/user/node-metrics.md +++ b/docs/cs-rCZ/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| 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 | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metrický | Popis | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Slabý | | < -10 dB | Poor | +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. + ## Metriky napájení Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/cs-rCZ/user/nodes.md b/docs/cs-rCZ/user/nodes.md index c440ee1f0..297cf2b51 100644 --- a/docs/cs-rCZ/user/nodes.md +++ b/docs/cs-rCZ/user/nodes.md @@ -2,7 +2,7 @@ title: Uzly parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Naposledy slyšen | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Vzdálenost | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/cs-rCZ/user/telemetry-and-sensors.md b/docs/cs-rCZ/user/telemetry-and-sensors.md index c4d2449e3..814340b0c 100644 --- a/docs/cs-rCZ/user/telemetry-and-sensors.md +++ b/docs/cs-rCZ/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/de-rDE/user/android-auto.md b/docs/de-rDE/user/android-auto.md new file mode 100644 index 000000000..a71bf8bbf --- /dev/null +++ b/docs/de-rDE/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: Benutzerhandbuch +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Übersicht + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Nachrichten + +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. + +## Knoten + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/de-rDE/user/app-functions.md b/docs/de-rDE/user/app-functions.md new file mode 100644 index 000000000..b4f0bb025 --- /dev/null +++ b/docs/de-rDE/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: Benutzerhandbuch +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Datenschutz + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/de-rDE/user/desktop.md b/docs/de-rDE/user/desktop.md index dc8955f4b..1de51c6d1 100644 --- a/docs/de-rDE/user/desktop.md +++ b/docs/de-rDE/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Funktion | Android | Desktop | Knoten | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Karte | ✓ | ✓ | Full parity | -| Einstellungen | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Benachrichtigungen | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Funktion | Android | Desktop | Knoten | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Karte | ✓ | ✓ | Full parity | +| Einstellungen | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/de-rDE/user/discovery.md b/docs/de-rDE/user/discovery.md index 286a28104..2d7887270 100644 --- a/docs/de-rDE/user/discovery.md +++ b/docs/de-rDE/user/discovery.md @@ -2,8 +2,8 @@ title: Entdecken parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/de-rDE/user/messages-and-channels.md b/docs/de-rDE/user/messages-and-channels.md index 6c374f8fd..bab9a9c2b 100644 --- a/docs/de-rDE/user/messages-and-channels.md +++ b/docs/de-rDE/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/de-rDE/user/node-metrics.md b/docs/de-rDE/user/node-metrics.md index a811c35eb..a9420ac1e 100644 --- a/docs/de-rDE/user/node-metrics.md +++ b/docs/de-rDE/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metrisch | Unit | 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 | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | Amber | +| Poor | < 5000 | Orange | +| Unsafe | < 30000 | Rot | +| Evacuate | ≥ 30000 | Dark red | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signaldaten Radio signal quality information: -| Metrisch | Beschreibung | -| ----------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Sprungweite | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Ordentliche Signalstärke | | < -10 dB | Poor | +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. + ## Energiedaten Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/de-rDE/user/nodes.md b/docs/de-rDE/user/nodes.md index e0e1d1aa5..3145daaf3 100644 --- a/docs/de-rDE/user/nodes.md +++ b/docs/de-rDE/user/nodes.md @@ -2,7 +2,7 @@ title: Knoten parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Zuletzt gehört | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distanz | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/de-rDE/user/telemetry-and-sensors.md b/docs/de-rDE/user/telemetry-and-sensors.md index 771918bdd..8a6167f35 100644 --- a/docs/de-rDE/user/telemetry-and-sensors.md +++ b/docs/de-rDE/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +Nodes with particulate matter or CO₂ sensors report air quality data: + +| Metrisch | Unit | 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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/el-rGR/user/android-auto.md b/docs/el-rGR/user/android-auto.md new file mode 100644 index 000000000..183dffb42 --- /dev/null +++ b/docs/el-rGR/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Μηνύματα + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/el-rGR/user/app-functions.md b/docs/el-rGR/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/el-rGR/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/el-rGR/user/desktop.md b/docs/el-rGR/user/desktop.md index 73d263d76..8de4ad29b 100644 --- a/docs/el-rGR/user/desktop.md +++ b/docs/el-rGR/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Χάρτης | ✓ | ✓ | Full parity | -| Ρυθμίσεις | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Χάρτης | ✓ | ✓ | Full parity | +| Ρυθμίσεις | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/el-rGR/user/discovery.md b/docs/el-rGR/user/discovery.md index 1c5d754a9..7532cb52b 100644 --- a/docs/el-rGR/user/discovery.md +++ b/docs/el-rGR/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/el-rGR/user/messages-and-channels.md b/docs/el-rGR/user/messages-and-channels.md index ff219a49b..d4b539a0d 100644 --- a/docs/el-rGR/user/messages-and-channels.md +++ b/docs/el-rGR/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/el-rGR/user/node-metrics.md b/docs/el-rGR/user/node-metrics.md index 7e986cc88..a71230dc1 100644 --- a/docs/el-rGR/user/node-metrics.md +++ b/docs/el-rGR/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Περιγραφή | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Περιγραφή | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Fair | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/el-rGR/user/nodes.md b/docs/el-rGR/user/nodes.md index 59c712bb0..7e392eb0b 100644 --- a/docs/el-rGR/user/nodes.md +++ b/docs/el-rGR/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Last heard | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Απόσταση | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/el-rGR/user/telemetry-and-sensors.md b/docs/el-rGR/user/telemetry-and-sensors.md index 64cf61c5b..9913d614d 100644 --- a/docs/el-rGR/user/telemetry-and-sensors.md +++ b/docs/el-rGR/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/es-rES/user/android-auto.md b/docs/es-rES/user/android-auto.md new file mode 100644 index 000000000..d9da25330 --- /dev/null +++ b/docs/es-rES/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Visión general + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Mensajes + +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. + +## Nodos + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/es-rES/user/app-functions.md b/docs/es-rES/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/es-rES/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/es-rES/user/desktop.md b/docs/es-rES/user/desktop.md index 39277f983..14ab67c08 100644 --- a/docs/es-rES/user/desktop.md +++ b/docs/es-rES/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notas | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Mapa | ✓ | ✓ | Full parity | -| Ajustes | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notas | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Mapa | ✓ | ✓ | Full parity | +| Ajustes | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/es-rES/user/discovery.md b/docs/es-rES/user/discovery.md index dbca366ca..095e74bef 100644 --- a/docs/es-rES/user/discovery.md +++ b/docs/es-rES/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/es-rES/user/messages-and-channels.md b/docs/es-rES/user/messages-and-channels.md index d0d92b53f..f9c7d0859 100644 --- a/docs/es-rES/user/messages-and-channels.md +++ b/docs/es-rES/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/es-rES/user/node-metrics.md b/docs/es-rES/user/node-metrics.md index 6a64d8d66..ded07d961 100644 --- a/docs/es-rES/user/node-metrics.md +++ b/docs/es-rES/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| 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 | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics 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) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Aceptable | | < -10 dB | Poor | +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. + ## Métricas de Energía Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/es-rES/user/nodes.md b/docs/es-rES/user/nodes.md index 2e5a4c340..6bade20db 100644 --- a/docs/es-rES/user/nodes.md +++ b/docs/es-rES/user/nodes.md @@ -2,7 +2,7 @@ title: Nodos parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Última escucha | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distancia | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/es-rES/user/telemetry-and-sensors.md b/docs/es-rES/user/telemetry-and-sensors.md index 387b013a3..438872c9c 100644 --- a/docs/es-rES/user/telemetry-and-sensors.md +++ b/docs/es-rES/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/et-rEE/user/android-auto.md b/docs/et-rEE/user/android-auto.md new file mode 100644 index 000000000..3006e601f --- /dev/null +++ b/docs/et-rEE/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: Kasutaja juhis +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Sõnumid + +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. + +## Sõlmed + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/et-rEE/user/app-functions.md b/docs/et-rEE/user/app-functions.md new file mode 100644 index 000000000..2cbe821be --- /dev/null +++ b/docs/et-rEE/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: Kasutaja juhis +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/et-rEE/user/desktop.md b/docs/et-rEE/user/desktop.md index 2c76cb82f..39c618369 100644 --- a/docs/et-rEE/user/desktop.md +++ b/docs/et-rEE/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Sõnumid | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Kaart | ✓ | ✓ | Full parity | -| Sätted | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Sõnumid | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Kaart | ✓ | ✓ | Full parity | +| Sätted | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/et-rEE/user/discovery.md b/docs/et-rEE/user/discovery.md index 0214bef86..c42ebd247 100644 --- a/docs/et-rEE/user/discovery.md +++ b/docs/et-rEE/user/discovery.md @@ -2,8 +2,8 @@ title: Avastamine parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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 | Kirjeldus | +| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Marsruudi 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. diff --git a/docs/et-rEE/user/messages-and-channels.md b/docs/et-rEE/user/messages-and-channels.md index 22bc92b54..48d345b78 100644 --- a/docs/et-rEE/user/messages-and-channels.md +++ b/docs/et-rEE/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/et-rEE/user/node-metrics.md b/docs/et-rEE/user/node-metrics.md index 2498beab5..0ec83e8a5 100644 --- a/docs/et-rEE/user/node-metrics.md +++ b/docs/et-rEE/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Kirjeldus | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +CO₂ readings are color-coded by severity to make air quality easy to read at a glance: + +| Band | CO₂ Range (ppm) | Color | +| -------- | ---------------------------------- | -------- | +| Hea | < 1000 | Roheline | +| Stuffy | < 2000 | Amber | +| Poor | < 5000 | Oranž | +| Unsafe | < 30000 | Punane | +| Evacuate | ≥ 30000 | Dark red | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signaali mõõdikud Radio signal quality information: -| Metric | Kirjeldus | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| Metric | Kirjeldus | +| ----------- | ------------------------------------------------------------------------------ | +| SNR | Signal-to-Noise Ratio (higher is better) | +| RSSI | Received Signal Strength Indicator (closer to 0 is better) | +| Noise Floor | Local background RF noise in dBm (more negative is quieter) | +| Hop Count | Number of mesh hops for last message | ### Signal Quality Reference @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Rahuldav | | < -10 dB | Poor | +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. + ## Võimsusnäitajad Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/et-rEE/user/nodes.md b/docs/et-rEE/user/nodes.md index 17b59fb3a..4e5c6a07e 100644 --- a/docs/et-rEE/user/nodes.md +++ b/docs/et-rEE/user/nodes.md @@ -2,7 +2,7 @@ title: Sõlmed parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Viimati kuuldud | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Kaugus | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/et-rEE/user/telemetry-and-sensors.md b/docs/et-rEE/user/telemetry-and-sensors.md index 8fc149db5..0c7a33b72 100644 --- a/docs/et-rEE/user/telemetry-and-sensors.md +++ b/docs/et-rEE/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +Nodes with particulate matter or CO₂ sensors report air quality data: + +| Metric | Unit | Kirjeldus | +| --------------------- | ----- | ---------------------------- | +| 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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/fi-rFI/user/android-auto.md b/docs/fi-rFI/user/android-auto.md new file mode 100644 index 000000000..d29592df2 --- /dev/null +++ b/docs/fi-rFI/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: Käyttöopas +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Yleiskatsaus + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Viestit + +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. + +## Laitteet + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/fi-rFI/user/app-functions.md b/docs/fi-rFI/user/app-functions.md new file mode 100644 index 000000000..39952180c --- /dev/null +++ b/docs/fi-rFI/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: Käyttöopas +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/fi-rFI/user/desktop.md b/docs/fi-rFI/user/desktop.md index c329ba115..9c63e02d3 100644 --- a/docs/fi-rFI/user/desktop.md +++ b/docs/fi-rFI/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Viestit | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Kartta | ✓ | ✓ | Full parity | -| Asetukset | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Viestit | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Kartta | ✓ | ✓ | Full parity | +| Asetukset | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/fi-rFI/user/discovery.md b/docs/fi-rFI/user/discovery.md index 99d3eba80..610d9442f 100644 --- a/docs/fi-rFI/user/discovery.md +++ b/docs/fi-rFI/user/discovery.md @@ -2,8 +2,8 @@ title: Haku parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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 | Kuvaus | +| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +Metrics include: + +| Metrijärjestelmä | What it tells you | +| ---------------------------------------- | ---------------------------------------------------------------------------------------------- | +| RF health | Overall quality of the radio environment on that preset. | +| Kanavan käyttöaste | 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. + +--- + +## Manual Exploration + +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. + ## Reitinselvitys 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. diff --git a/docs/fi-rFI/user/messages-and-channels.md b/docs/fi-rFI/user/messages-and-channels.md index 526243aa7..f52ec5fbc 100644 --- a/docs/fi-rFI/user/messages-and-channels.md +++ b/docs/fi-rFI/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/fi-rFI/user/node-metrics.md b/docs/fi-rFI/user/node-metrics.md index e1789b9a7..564d1450d 100644 --- a/docs/fi-rFI/user/node-metrics.md +++ b/docs/fi-rFI/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metrijärjestelmä | Unit | Kuvaus | +| --------------------- | ----- | ---------------------------------------------------- | +| 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 | +| CO₂ | ppm | Carbon dioxide concentration | + +CO₂ readings are color-coded by severity to make air quality easy to read at a glance: + +| Band | CO₂ Range (ppm) | Color | +| -------- | ---------------------------------- | -------- | +| Hyvä | < 1000 | Vihreä | +| Stuffy | < 2000 | Amber | +| Poor | < 5000 | Oranssi | +| Unsafe | < 30000 | Punainen | +| Evacuate | ≥ 30000 | Dark red | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signaalin voimakkuudet Radio signal quality information: -| Metrijärjestelmä | Kuvaus | -| ---------------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| Metrijärjestelmä | Kuvaus | +| ---------------- | ------------------------------------------------------------------------------ | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Kohtalainen | | < -10 dB | Poor | +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. + ## Virranhallinnan arvot Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/fi-rFI/user/nodes.md b/docs/fi-rFI/user/nodes.md index 310f05e44..6db62bd23 100644 --- a/docs/fi-rFI/user/nodes.md +++ b/docs/fi-rFI/user/nodes.md @@ -2,7 +2,7 @@ title: Laitteet parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Viimeksi kuultu | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Etäisyys | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/fi-rFI/user/telemetry-and-sensors.md b/docs/fi-rFI/user/telemetry-and-sensors.md index 613a925e8..0862c7ef7 100644 --- a/docs/fi-rFI/user/telemetry-and-sensors.md +++ b/docs/fi-rFI/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +Nodes with particulate matter or CO₂ sensors report air quality data: + +| Metrijärjestelmä | Unit | Kuvaus | +| --------------------- | ----- | ---------------------------- | +| 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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/fr-rFR/user/android-auto.md b/docs/fr-rFR/user/android-auto.md new file mode 100644 index 000000000..306ffbb8d --- /dev/null +++ b/docs/fr-rFR/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: Guide de l'utilisateur +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Messages + +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. + +## Nœuds + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/fr-rFR/user/app-functions.md b/docs/fr-rFR/user/app-functions.md new file mode 100644 index 000000000..189ce4903 --- /dev/null +++ b/docs/fr-rFR/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: Guide de l'utilisateur +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/fr-rFR/user/desktop.md b/docs/fr-rFR/user/desktop.md index 4c7db28ed..33a9c858c 100644 --- a/docs/fr-rFR/user/desktop.md +++ b/docs/fr-rFR/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Carte | ✓ | ✓ | Full parity | -| Réglages | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Carte | ✓ | ✓ | Full parity | +| Réglages | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/fr-rFR/user/discovery.md b/docs/fr-rFR/user/discovery.md index d2e23cb8d..af6606aa6 100644 --- a/docs/fr-rFR/user/discovery.md +++ b/docs/fr-rFR/user/discovery.md @@ -2,8 +2,8 @@ title: Découverte parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/fr-rFR/user/messages-and-channels.md b/docs/fr-rFR/user/messages-and-channels.md index 7d8c435f3..3ae634abb 100644 --- a/docs/fr-rFR/user/messages-and-channels.md +++ b/docs/fr-rFR/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/fr-rFR/user/node-metrics.md b/docs/fr-rFR/user/node-metrics.md index 9e1cbdb23..be6b92445 100644 --- a/docs/fr-rFR/user/node-metrics.md +++ b/docs/fr-rFR/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Description | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Métriques de Signal Radio signal quality information: -| Metric | Description | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Passable | | < -10 dB | Poor | +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. + ## Métriques d'alimentation Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/fr-rFR/user/nodes.md b/docs/fr-rFR/user/nodes.md index ae4eea7e6..622c405a2 100644 --- a/docs/fr-rFR/user/nodes.md +++ b/docs/fr-rFR/user/nodes.md @@ -2,7 +2,7 @@ title: Nœuds parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Dernière écoute | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distance | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/fr-rFR/user/telemetry-and-sensors.md b/docs/fr-rFR/user/telemetry-and-sensors.md index fea384711..0bdf2c0b2 100644 --- a/docs/fr-rFR/user/telemetry-and-sensors.md +++ b/docs/fr-rFR/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/ga-rIE/user/android-auto.md b/docs/ga-rIE/user/android-auto.md new file mode 100644 index 000000000..aeb53435d --- /dev/null +++ b/docs/ga-rIE/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Messages + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/ga-rIE/user/app-functions.md b/docs/ga-rIE/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/ga-rIE/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/ga-rIE/user/desktop.md b/docs/ga-rIE/user/desktop.md index 1af615e66..e69b44554 100644 --- a/docs/ga-rIE/user/desktop.md +++ b/docs/ga-rIE/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Settings | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Settings | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/ga-rIE/user/discovery.md b/docs/ga-rIE/user/discovery.md index a1110f681..eb2620666 100644 --- a/docs/ga-rIE/user/discovery.md +++ b/docs/ga-rIE/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Céim rianadóireachta Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/ga-rIE/user/messages-and-channels.md b/docs/ga-rIE/user/messages-and-channels.md index f3b93d4d6..bcefc008f 100644 --- a/docs/ga-rIE/user/messages-and-channels.md +++ b/docs/ga-rIE/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/ga-rIE/user/node-metrics.md b/docs/ga-rIE/user/node-metrics.md index ab86a0a50..4c8001b19 100644 --- a/docs/ga-rIE/user/node-metrics.md +++ b/docs/ga-rIE/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Cur síos | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics 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) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Ceart go leor | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/ga-rIE/user/nodes.md b/docs/ga-rIE/user/nodes.md index fe9d10fbd..d143a0df0 100644 --- a/docs/ga-rIE/user/nodes.md +++ b/docs/ga-rIE/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Deiridh chluinmhu | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Sáth | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/ga-rIE/user/telemetry-and-sensors.md b/docs/ga-rIE/user/telemetry-and-sensors.md index 33449f64a..233c4981b 100644 --- a/docs/ga-rIE/user/telemetry-and-sensors.md +++ b/docs/ga-rIE/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/gl-rES/user/android-auto.md b/docs/gl-rES/user/android-auto.md new file mode 100644 index 000000000..aeb53435d --- /dev/null +++ b/docs/gl-rES/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Messages + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/gl-rES/user/app-functions.md b/docs/gl-rES/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/gl-rES/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/gl-rES/user/desktop.md b/docs/gl-rES/user/desktop.md index 1af615e66..e69b44554 100644 --- a/docs/gl-rES/user/desktop.md +++ b/docs/gl-rES/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Settings | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Settings | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/gl-rES/user/discovery.md b/docs/gl-rES/user/discovery.md index a295f6493..a018c98c4 100644 --- a/docs/gl-rES/user/discovery.md +++ b/docs/gl-rES/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traza-ruta Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/gl-rES/user/messages-and-channels.md b/docs/gl-rES/user/messages-and-channels.md index 2502fff27..8639f7403 100644 --- a/docs/gl-rES/user/messages-and-channels.md +++ b/docs/gl-rES/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/gl-rES/user/node-metrics.md b/docs/gl-rES/user/node-metrics.md index 3279af4f5..8eac845d7 100644 --- a/docs/gl-rES/user/node-metrics.md +++ b/docs/gl-rES/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Descrición | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics 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) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Fair | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/gl-rES/user/nodes.md b/docs/gl-rES/user/nodes.md index 996771385..5d1a40bdb 100644 --- a/docs/gl-rES/user/nodes.md +++ b/docs/gl-rES/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Última escoita | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distancia | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/gl-rES/user/telemetry-and-sensors.md b/docs/gl-rES/user/telemetry-and-sensors.md index c5fa8bf04..4190b0243 100644 --- a/docs/gl-rES/user/telemetry-and-sensors.md +++ b/docs/gl-rES/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/hr-rHR/user/android-auto.md b/docs/hr-rHR/user/android-auto.md new file mode 100644 index 000000000..aeb53435d --- /dev/null +++ b/docs/hr-rHR/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Messages + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/hr-rHR/user/app-functions.md b/docs/hr-rHR/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/hr-rHR/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/hr-rHR/user/desktop.md b/docs/hr-rHR/user/desktop.md index 1af615e66..e69b44554 100644 --- a/docs/hr-rHR/user/desktop.md +++ b/docs/hr-rHR/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Settings | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Settings | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/hr-rHR/user/discovery.md b/docs/hr-rHR/user/discovery.md index 1c5d754a9..9f3c97cc4 100644 --- a/docs/hr-rHR/user/discovery.md +++ b/docs/hr-rHR/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/hr-rHR/user/messages-and-channels.md b/docs/hr-rHR/user/messages-and-channels.md index f2e6a86b5..93e145883 100644 --- a/docs/hr-rHR/user/messages-and-channels.md +++ b/docs/hr-rHR/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/hr-rHR/user/node-metrics.md b/docs/hr-rHR/user/node-metrics.md index 79372ee26..b72407908 100644 --- a/docs/hr-rHR/user/node-metrics.md +++ b/docs/hr-rHR/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Opis | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Opis | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Fair | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/hr-rHR/user/nodes.md b/docs/hr-rHR/user/nodes.md index bf71273b7..e9b46b736 100644 --- a/docs/hr-rHR/user/nodes.md +++ b/docs/hr-rHR/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Posljednje čuo | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Udaljenost | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/hr-rHR/user/telemetry-and-sensors.md b/docs/hr-rHR/user/telemetry-and-sensors.md index 0fe2b1e83..bd4bc0002 100644 --- a/docs/hr-rHR/user/telemetry-and-sensors.md +++ b/docs/hr-rHR/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/ht-rHT/user/android-auto.md b/docs/ht-rHT/user/android-auto.md new file mode 100644 index 000000000..aeb53435d --- /dev/null +++ b/docs/ht-rHT/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Messages + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/ht-rHT/user/app-functions.md b/docs/ht-rHT/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/ht-rHT/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/ht-rHT/user/desktop.md b/docs/ht-rHT/user/desktop.md index 1af615e66..e69b44554 100644 --- a/docs/ht-rHT/user/desktop.md +++ b/docs/ht-rHT/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Settings | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Settings | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/ht-rHT/user/discovery.md b/docs/ht-rHT/user/discovery.md index 1c5d754a9..d7899595a 100644 --- a/docs/ht-rHT/user/discovery.md +++ b/docs/ht-rHT/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/ht-rHT/user/messages-and-channels.md b/docs/ht-rHT/user/messages-and-channels.md index 1d3122c09..362068874 100644 --- a/docs/ht-rHT/user/messages-and-channels.md +++ b/docs/ht-rHT/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/ht-rHT/user/node-metrics.md b/docs/ht-rHT/user/node-metrics.md index 433c84399..2403a1fb1 100644 --- a/docs/ht-rHT/user/node-metrics.md +++ b/docs/ht-rHT/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Deskripsyon | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Deskripsyon | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Mwayen | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/ht-rHT/user/nodes.md b/docs/ht-rHT/user/nodes.md index cc498f37a..2d54b6f2c 100644 --- a/docs/ht-rHT/user/nodes.md +++ b/docs/ht-rHT/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Dènye fwa li tande | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distans | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/ht-rHT/user/telemetry-and-sensors.md b/docs/ht-rHT/user/telemetry-and-sensors.md index 75ccf4cd9..7c9411150 100644 --- a/docs/ht-rHT/user/telemetry-and-sensors.md +++ b/docs/ht-rHT/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/hu-rHU/user/android-auto.md b/docs/hu-rHU/user/android-auto.md new file mode 100644 index 000000000..56e8b050e --- /dev/null +++ b/docs/hu-rHU/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Üzenetek + +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. + +## Csomópontok + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/hu-rHU/user/app-functions.md b/docs/hu-rHU/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/hu-rHU/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/hu-rHU/user/desktop.md b/docs/hu-rHU/user/desktop.md index 5a6df9cf6..77e3d29ed 100644 --- a/docs/hu-rHU/user/desktop.md +++ b/docs/hu-rHU/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Jegyzetek | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Térkép | ✓ | ✓ | Full parity | -| Beállítások | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Jegyzetek | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Térkép | ✓ | ✓ | Full parity | +| Beállítások | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/hu-rHU/user/discovery.md b/docs/hu-rHU/user/discovery.md index b91927455..e093caefa 100644 --- a/docs/hu-rHU/user/discovery.md +++ b/docs/hu-rHU/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/hu-rHU/user/messages-and-channels.md b/docs/hu-rHU/user/messages-and-channels.md index 084e96039..060e0a575 100644 --- a/docs/hu-rHU/user/messages-and-channels.md +++ b/docs/hu-rHU/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/hu-rHU/user/node-metrics.md b/docs/hu-rHU/user/node-metrics.md index aa3218fcb..cb8bdaa6e 100644 --- a/docs/hu-rHU/user/node-metrics.md +++ b/docs/hu-rHU/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Leírás | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics 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) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Megfelelő | | < -10 dB | Poor | +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. + ## Tápellátási metrikák Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/hu-rHU/user/nodes.md b/docs/hu-rHU/user/nodes.md index 0ab44f51e..c804b6a39 100644 --- a/docs/hu-rHU/user/nodes.md +++ b/docs/hu-rHU/user/nodes.md @@ -2,7 +2,7 @@ title: Csomópontok parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Utoljára hallott | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Távolság | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/hu-rHU/user/telemetry-and-sensors.md b/docs/hu-rHU/user/telemetry-and-sensors.md index 4e076535f..9e8309646 100644 --- a/docs/hu-rHU/user/telemetry-and-sensors.md +++ b/docs/hu-rHU/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/is-rIS/user/android-auto.md b/docs/is-rIS/user/android-auto.md new file mode 100644 index 000000000..aeb53435d --- /dev/null +++ b/docs/is-rIS/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Messages + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/is-rIS/user/app-functions.md b/docs/is-rIS/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/is-rIS/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/is-rIS/user/desktop.md b/docs/is-rIS/user/desktop.md index 1af615e66..e69b44554 100644 --- a/docs/is-rIS/user/desktop.md +++ b/docs/is-rIS/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Settings | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Settings | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/is-rIS/user/discovery.md b/docs/is-rIS/user/discovery.md index 058739c74..e39f1acc6 100644 --- a/docs/is-rIS/user/discovery.md +++ b/docs/is-rIS/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Ferilkönnun Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/is-rIS/user/messages-and-channels.md b/docs/is-rIS/user/messages-and-channels.md index b38800e03..f27aab449 100644 --- a/docs/is-rIS/user/messages-and-channels.md +++ b/docs/is-rIS/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/is-rIS/user/node-metrics.md b/docs/is-rIS/user/node-metrics.md index 352dfa112..158ffff06 100644 --- a/docs/is-rIS/user/node-metrics.md +++ b/docs/is-rIS/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Lýsing | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics 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) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Fair | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/is-rIS/user/nodes.md b/docs/is-rIS/user/nodes.md index a1224ee9f..2d1640813 100644 --- a/docs/is-rIS/user/nodes.md +++ b/docs/is-rIS/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Last heard | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distance | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/is-rIS/user/telemetry-and-sensors.md b/docs/is-rIS/user/telemetry-and-sensors.md index 3521d1030..6aed6333d 100644 --- a/docs/is-rIS/user/telemetry-and-sensors.md +++ b/docs/is-rIS/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/it-rIT/user/android-auto.md b/docs/it-rIT/user/android-auto.md new file mode 100644 index 000000000..fa3ba9857 --- /dev/null +++ b/docs/it-rIT/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Panoramica + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Messaggi + +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. + +## Nodi + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/it-rIT/user/app-functions.md b/docs/it-rIT/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/it-rIT/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/it-rIT/user/desktop.md b/docs/it-rIT/user/desktop.md index 29f83dff7..eae1617e5 100644 --- a/docs/it-rIT/user/desktop.md +++ b/docs/it-rIT/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Note | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Mappa | ✓ | ✓ | Full parity | -| Impostazioni | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Note | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Mappa | ✓ | ✓ | Full parity | +| Impostazioni | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/it-rIT/user/discovery.md b/docs/it-rIT/user/discovery.md index 43ecdbc5b..53269593b 100644 --- a/docs/it-rIT/user/discovery.md +++ b/docs/it-rIT/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/it-rIT/user/messages-and-channels.md b/docs/it-rIT/user/messages-and-channels.md index a7d31ac06..58baf0a6e 100644 --- a/docs/it-rIT/user/messages-and-channels.md +++ b/docs/it-rIT/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/it-rIT/user/node-metrics.md b/docs/it-rIT/user/node-metrics.md index 0a168659d..880606860 100644 --- a/docs/it-rIT/user/node-metrics.md +++ b/docs/it-rIT/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metrico | Unit | Descrizione | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metrico | Descrizione | -| ------------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Conteggio Hop | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Discreto | | < -10 dB | Poor | +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. + ## Metriche Alimentazione Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/it-rIT/user/nodes.md b/docs/it-rIT/user/nodes.md index b36253040..4a74a73b9 100644 --- a/docs/it-rIT/user/nodes.md +++ b/docs/it-rIT/user/nodes.md @@ -2,7 +2,7 @@ title: Nodi parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Ricevuto più di recente | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distanza | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/it-rIT/user/telemetry-and-sensors.md b/docs/it-rIT/user/telemetry-and-sensors.md index c3b000896..a5ea73c2b 100644 --- a/docs/it-rIT/user/telemetry-and-sensors.md +++ b/docs/it-rIT/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/iw-rIL/user/android-auto.md b/docs/iw-rIL/user/android-auto.md new file mode 100644 index 000000000..c56b0a8d0 --- /dev/null +++ b/docs/iw-rIL/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## הודעות + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/iw-rIL/user/app-functions.md b/docs/iw-rIL/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/iw-rIL/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/iw-rIL/user/desktop.md b/docs/iw-rIL/user/desktop.md index 469ee1635..cad604034 100644 --- a/docs/iw-rIL/user/desktop.md +++ b/docs/iw-rIL/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| מפה | ✓ | ✓ | Full parity | -| הגדרות | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| מפה | ✓ | ✓ | Full parity | +| הגדרות | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/iw-rIL/user/discovery.md b/docs/iw-rIL/user/discovery.md index cae2bcbd1..9be27891b 100644 --- a/docs/iw-rIL/user/discovery.md +++ b/docs/iw-rIL/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## בדיקת מסלול 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. diff --git a/docs/iw-rIL/user/messages-and-channels.md b/docs/iw-rIL/user/messages-and-channels.md index 1f17d42fd..1b66e8541 100644 --- a/docs/iw-rIL/user/messages-and-channels.md +++ b/docs/iw-rIL/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/iw-rIL/user/node-metrics.md b/docs/iw-rIL/user/node-metrics.md index e21ec4640..a9dd965ed 100644 --- a/docs/iw-rIL/user/node-metrics.md +++ b/docs/iw-rIL/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | תיאור | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | תיאור | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Fair | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/iw-rIL/user/nodes.md b/docs/iw-rIL/user/nodes.md index 8ce0c0270..9fb935dcf 100644 --- a/docs/iw-rIL/user/nodes.md +++ b/docs/iw-rIL/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Last heard | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | מרחק | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/iw-rIL/user/telemetry-and-sensors.md b/docs/iw-rIL/user/telemetry-and-sensors.md index 23eb1e983..978c3f72a 100644 --- a/docs/iw-rIL/user/telemetry-and-sensors.md +++ b/docs/iw-rIL/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/ja-rJP/user/android-auto.md b/docs/ja-rJP/user/android-auto.md new file mode 100644 index 000000000..a95d39a87 --- /dev/null +++ b/docs/ja-rJP/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## メッセージ + +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. + +## ノード + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/ja-rJP/user/app-functions.md b/docs/ja-rJP/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/ja-rJP/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/ja-rJP/user/desktop.md b/docs/ja-rJP/user/desktop.md index 3134dec67..f6401df8b 100644 --- a/docs/ja-rJP/user/desktop.md +++ b/docs/ja-rJP/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| 地図 | ✓ | ✓ | Full parity | -| 設定 | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| 地図 | ✓ | ✓ | Full parity | +| 設定 | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/ja-rJP/user/discovery.md b/docs/ja-rJP/user/discovery.md index 0d035e387..8c45d6a8c 100644 --- a/docs/ja-rJP/user/discovery.md +++ b/docs/ja-rJP/user/discovery.md @@ -2,8 +2,8 @@ title: ディスカバリー parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## ルート追跡 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. diff --git a/docs/ja-rJP/user/messages-and-channels.md b/docs/ja-rJP/user/messages-and-channels.md index dc70299e9..1553b976c 100644 --- a/docs/ja-rJP/user/messages-and-channels.md +++ b/docs/ja-rJP/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/ja-rJP/user/node-metrics.md b/docs/ja-rJP/user/node-metrics.md index 8a3ab0ef6..29a5b0490 100644 --- a/docs/ja-rJP/user/node-metrics.md +++ b/docs/ja-rJP/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | 説明 | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | 説明 | -| --------- | ----------------------------------------------------------------------------- | -| SN比 | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| Metric | 説明 | +| ----------- | ------------------------------------------------------------------------------ | +| SN比 | 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | 普通 | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/ja-rJP/user/nodes.md b/docs/ja-rJP/user/nodes.md index 068ba97be..b699eb879 100644 --- a/docs/ja-rJP/user/nodes.md +++ b/docs/ja-rJP/user/nodes.md @@ -2,7 +2,7 @@ title: ノード parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | 最後の通信 | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | 距離 | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/ja-rJP/user/telemetry-and-sensors.md b/docs/ja-rJP/user/telemetry-and-sensors.md index c0ae08175..bdee2e39d 100644 --- a/docs/ja-rJP/user/telemetry-and-sensors.md +++ b/docs/ja-rJP/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/ko-rKR/user/android-auto.md b/docs/ko-rKR/user/android-auto.md new file mode 100644 index 000000000..3c1476086 --- /dev/null +++ b/docs/ko-rKR/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## 메시지기기 + +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. + +## 노드 + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/ko-rKR/user/app-functions.md b/docs/ko-rKR/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/ko-rKR/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/ko-rKR/user/desktop.md b/docs/ko-rKR/user/desktop.md index 0b5aa7033..182554556 100644 --- a/docs/ko-rKR/user/desktop.md +++ b/docs/ko-rKR/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| 지도 | ✓ | ✓ | Full parity | -| 설정 | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| 지도 | ✓ | ✓ | Full parity | +| 설정 | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/ko-rKR/user/discovery.md b/docs/ko-rKR/user/discovery.md index 9b5182384..21beccd98 100644 --- a/docs/ko-rKR/user/discovery.md +++ b/docs/ko-rKR/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## 추적 루트 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. diff --git a/docs/ko-rKR/user/messages-and-channels.md b/docs/ko-rKR/user/messages-and-channels.md index f629c5404..da3f988be 100644 --- a/docs/ko-rKR/user/messages-and-channels.md +++ b/docs/ko-rKR/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/ko-rKR/user/node-metrics.md b/docs/ko-rKR/user/node-metrics.md index 481736f1f..4ea1c8ce4 100644 --- a/docs/ko-rKR/user/node-metrics.md +++ b/docs/ko-rKR/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | 설명 | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | 설명 | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | 보통 | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/ko-rKR/user/nodes.md b/docs/ko-rKR/user/nodes.md index d1f04a122..f6dc7ea32 100644 --- a/docs/ko-rKR/user/nodes.md +++ b/docs/ko-rKR/user/nodes.md @@ -2,7 +2,7 @@ title: 노드 parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | 최근 수신 | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | 거리 | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/ko-rKR/user/telemetry-and-sensors.md b/docs/ko-rKR/user/telemetry-and-sensors.md index 390888685..9f21782d6 100644 --- a/docs/ko-rKR/user/telemetry-and-sensors.md +++ b/docs/ko-rKR/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/lt-rLT/user/android-auto.md b/docs/lt-rLT/user/android-auto.md new file mode 100644 index 000000000..aeb53435d --- /dev/null +++ b/docs/lt-rLT/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Messages + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/lt-rLT/user/app-functions.md b/docs/lt-rLT/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/lt-rLT/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/lt-rLT/user/desktop.md b/docs/lt-rLT/user/desktop.md index 1af615e66..e69b44554 100644 --- a/docs/lt-rLT/user/desktop.md +++ b/docs/lt-rLT/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Settings | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Settings | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/lt-rLT/user/discovery.md b/docs/lt-rLT/user/discovery.md index 5ac719201..8703f9bdf 100644 --- a/docs/lt-rLT/user/discovery.md +++ b/docs/lt-rLT/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Žinutės kelias Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/lt-rLT/user/messages-and-channels.md b/docs/lt-rLT/user/messages-and-channels.md index 39ae06315..2d58efec4 100644 --- a/docs/lt-rLT/user/messages-and-channels.md +++ b/docs/lt-rLT/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/lt-rLT/user/node-metrics.md b/docs/lt-rLT/user/node-metrics.md index 2f20b5c6a..af0863dff 100644 --- a/docs/lt-rLT/user/node-metrics.md +++ b/docs/lt-rLT/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Aprašymas | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics 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) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Pakankamas | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/lt-rLT/user/nodes.md b/docs/lt-rLT/user/nodes.md index bd54a310e..9bf7fe7b0 100644 --- a/docs/lt-rLT/user/nodes.md +++ b/docs/lt-rLT/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Seniausiai girdėtas | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Atstumas | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/lt-rLT/user/telemetry-and-sensors.md b/docs/lt-rLT/user/telemetry-and-sensors.md index 528d9935b..80f329133 100644 --- a/docs/lt-rLT/user/telemetry-and-sensors.md +++ b/docs/lt-rLT/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/nl-rNL/user/android-auto.md b/docs/nl-rNL/user/android-auto.md new file mode 100644 index 000000000..4ba72818a --- /dev/null +++ b/docs/nl-rNL/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Berichten + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/nl-rNL/user/app-functions.md b/docs/nl-rNL/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/nl-rNL/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/nl-rNL/user/desktop.md b/docs/nl-rNL/user/desktop.md index eb06f1034..c469a5fa1 100644 --- a/docs/nl-rNL/user/desktop.md +++ b/docs/nl-rNL/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Kaart | ✓ | ✓ | Full parity | -| Instellingen | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Kaart | ✓ | ✓ | Full parity | +| Instellingen | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/nl-rNL/user/discovery.md b/docs/nl-rNL/user/discovery.md index 1c5d754a9..da2b83f90 100644 --- a/docs/nl-rNL/user/discovery.md +++ b/docs/nl-rNL/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/nl-rNL/user/messages-and-channels.md b/docs/nl-rNL/user/messages-and-channels.md index df770a68b..364afc768 100644 --- a/docs/nl-rNL/user/messages-and-channels.md +++ b/docs/nl-rNL/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/nl-rNL/user/node-metrics.md b/docs/nl-rNL/user/node-metrics.md index fe9485f62..854988de9 100644 --- a/docs/nl-rNL/user/node-metrics.md +++ b/docs/nl-rNL/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Beschrijving | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Beschrijving | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Matig | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/nl-rNL/user/nodes.md b/docs/nl-rNL/user/nodes.md index de8fba247..40a0a5fad 100644 --- a/docs/nl-rNL/user/nodes.md +++ b/docs/nl-rNL/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Laatst gehoord | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Afstand | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/nl-rNL/user/telemetry-and-sensors.md b/docs/nl-rNL/user/telemetry-and-sensors.md index 742d78f75..eaa232776 100644 --- a/docs/nl-rNL/user/telemetry-and-sensors.md +++ b/docs/nl-rNL/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/no-rNO/user/android-auto.md b/docs/no-rNO/user/android-auto.md new file mode 100644 index 000000000..aeb53435d --- /dev/null +++ b/docs/no-rNO/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Messages + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/no-rNO/user/app-functions.md b/docs/no-rNO/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/no-rNO/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/no-rNO/user/desktop.md b/docs/no-rNO/user/desktop.md index 1af615e66..e69b44554 100644 --- a/docs/no-rNO/user/desktop.md +++ b/docs/no-rNO/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Settings | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Settings | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/no-rNO/user/discovery.md b/docs/no-rNO/user/discovery.md index 1c5d754a9..3f3a1d194 100644 --- a/docs/no-rNO/user/discovery.md +++ b/docs/no-rNO/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/no-rNO/user/messages-and-channels.md b/docs/no-rNO/user/messages-and-channels.md index 80d48ef26..bcc9ab965 100644 --- a/docs/no-rNO/user/messages-and-channels.md +++ b/docs/no-rNO/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/no-rNO/user/node-metrics.md b/docs/no-rNO/user/node-metrics.md index 658cf1dfe..31bc503db 100644 --- a/docs/no-rNO/user/node-metrics.md +++ b/docs/no-rNO/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Beskrivelse | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Beskrivelse | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Middelmådig | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/no-rNO/user/nodes.md b/docs/no-rNO/user/nodes.md index 56852384c..961eb160a 100644 --- a/docs/no-rNO/user/nodes.md +++ b/docs/no-rNO/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Sist hørt | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distanse | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/no-rNO/user/telemetry-and-sensors.md b/docs/no-rNO/user/telemetry-and-sensors.md index af062749e..aee614c0d 100644 --- a/docs/no-rNO/user/telemetry-and-sensors.md +++ b/docs/no-rNO/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/pl-rPL/user/android-auto.md b/docs/pl-rPL/user/android-auto.md new file mode 100644 index 000000000..df413309e --- /dev/null +++ b/docs/pl-rPL/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Wiadomości + +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. + +## Węzły + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/pl-rPL/user/app-functions.md b/docs/pl-rPL/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/pl-rPL/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/pl-rPL/user/desktop.md b/docs/pl-rPL/user/desktop.md index b35d3f35d..22ddb8d68 100644 --- a/docs/pl-rPL/user/desktop.md +++ b/docs/pl-rPL/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notatki | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Mapa | ✓ | ✓ | Full parity | -| Ustawienia | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notatki | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Mapa | ✓ | ✓ | Full parity | +| Ustawienia | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/pl-rPL/user/discovery.md b/docs/pl-rPL/user/discovery.md index 74678ec4d..97fa109dc 100644 --- a/docs/pl-rPL/user/discovery.md +++ b/docs/pl-rPL/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Pokaż trasę Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/pl-rPL/user/messages-and-channels.md b/docs/pl-rPL/user/messages-and-channels.md index 3ec443400..0b2663482 100644 --- a/docs/pl-rPL/user/messages-and-channels.md +++ b/docs/pl-rPL/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/pl-rPL/user/node-metrics.md b/docs/pl-rPL/user/node-metrics.md index a6a5d4550..e74208fc3 100644 --- a/docs/pl-rPL/user/node-metrics.md +++ b/docs/pl-rPL/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Opis | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Opis | -| --------------------- | ----------------------------------------------------------------------------- | -| SNR: | Signal-to-Noise Ratio (higher is better) | -| RSSI: | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | wystarczający | | < -10 dB | Poor | +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. + ## Metryki zasilania Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/pl-rPL/user/nodes.md b/docs/pl-rPL/user/nodes.md index 6c9acd715..d31a4a841 100644 --- a/docs/pl-rPL/user/nodes.md +++ b/docs/pl-rPL/user/nodes.md @@ -2,7 +2,7 @@ title: Węzły parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Aktywność | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Odległość | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/pl-rPL/user/telemetry-and-sensors.md b/docs/pl-rPL/user/telemetry-and-sensors.md index f66b6f1d1..b0fb67c17 100644 --- a/docs/pl-rPL/user/telemetry-and-sensors.md +++ b/docs/pl-rPL/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/pt-rBR/user/android-auto.md b/docs/pt-rBR/user/android-auto.md new file mode 100644 index 000000000..c29a6075e --- /dev/null +++ b/docs/pt-rBR/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Mensagens + +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. + +## Nós + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/pt-rBR/user/app-functions.md b/docs/pt-rBR/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/pt-rBR/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/pt-rBR/user/desktop.md b/docs/pt-rBR/user/desktop.md index 21bc02227..944d898c8 100644 --- a/docs/pt-rBR/user/desktop.md +++ b/docs/pt-rBR/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Mapa | ✓ | ✓ | Full parity | -| Configurações | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Mapa | ✓ | ✓ | Full parity | +| Configurações | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/pt-rBR/user/discovery.md b/docs/pt-rBR/user/discovery.md index f158666b8..26fcdd78d 100644 --- a/docs/pt-rBR/user/discovery.md +++ b/docs/pt-rBR/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traçar rota Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/pt-rBR/user/messages-and-channels.md b/docs/pt-rBR/user/messages-and-channels.md index c0e3a7c93..0b2e46b55 100644 --- a/docs/pt-rBR/user/messages-and-channels.md +++ b/docs/pt-rBR/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/pt-rBR/user/node-metrics.md b/docs/pt-rBR/user/node-metrics.md index 1f328fe1f..b41290bda 100644 --- a/docs/pt-rBR/user/node-metrics.md +++ b/docs/pt-rBR/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Descrição | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics 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) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Média | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/pt-rBR/user/nodes.md b/docs/pt-rBR/user/nodes.md index df855bc1c..988d713e4 100644 --- a/docs/pt-rBR/user/nodes.md +++ b/docs/pt-rBR/user/nodes.md @@ -2,7 +2,7 @@ title: Nós parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Visto pela última vez | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distância | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/pt-rBR/user/telemetry-and-sensors.md b/docs/pt-rBR/user/telemetry-and-sensors.md index 00414dfc4..caedaa4a8 100644 --- a/docs/pt-rBR/user/telemetry-and-sensors.md +++ b/docs/pt-rBR/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/pt-rPT/user/android-auto.md b/docs/pt-rPT/user/android-auto.md new file mode 100644 index 000000000..aa03f2a18 --- /dev/null +++ b/docs/pt-rPT/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Mensagens + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/pt-rPT/user/app-functions.md b/docs/pt-rPT/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/pt-rPT/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/pt-rPT/user/desktop.md b/docs/pt-rPT/user/desktop.md index e1404b718..8d1a1ead1 100644 --- a/docs/pt-rPT/user/desktop.md +++ b/docs/pt-rPT/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Mapa | ✓ | ✓ | Full parity | -| Definições | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Mapa | ✓ | ✓ | Full parity | +| Definições | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/pt-rPT/user/discovery.md b/docs/pt-rPT/user/discovery.md index f6e1b6341..49576f33b 100644 --- a/docs/pt-rPT/user/discovery.md +++ b/docs/pt-rPT/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traçar rota Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/pt-rPT/user/messages-and-channels.md b/docs/pt-rPT/user/messages-and-channels.md index 305e206d6..afe31527a 100644 --- a/docs/pt-rPT/user/messages-and-channels.md +++ b/docs/pt-rPT/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/pt-rPT/user/node-metrics.md b/docs/pt-rPT/user/node-metrics.md index 8b9124801..730d873bf 100644 --- a/docs/pt-rPT/user/node-metrics.md +++ b/docs/pt-rPT/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Descrição | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics 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) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Razoável | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/pt-rPT/user/nodes.md b/docs/pt-rPT/user/nodes.md index 58f86064c..c66073c36 100644 --- a/docs/pt-rPT/user/nodes.md +++ b/docs/pt-rPT/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Último recebido | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distância | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/pt-rPT/user/telemetry-and-sensors.md b/docs/pt-rPT/user/telemetry-and-sensors.md index 4ad2cfa4e..aa28c3f41 100644 --- a/docs/pt-rPT/user/telemetry-and-sensors.md +++ b/docs/pt-rPT/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/ro-rRO/user/android-auto.md b/docs/ro-rRO/user/android-auto.md new file mode 100644 index 000000000..275ebc22e --- /dev/null +++ b/docs/ro-rRO/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Mesaje + +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. + +## Noduri + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/ro-rRO/user/app-functions.md b/docs/ro-rRO/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/ro-rRO/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/ro-rRO/user/desktop.md b/docs/ro-rRO/user/desktop.md index 3e6c1faf8..f1db6316c 100644 --- a/docs/ro-rRO/user/desktop.md +++ b/docs/ro-rRO/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notițe | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Setări | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notițe | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Setări | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/ro-rRO/user/discovery.md b/docs/ro-rRO/user/discovery.md index d79bdc5de..393038e44 100644 --- a/docs/ro-rRO/user/discovery.md +++ b/docs/ro-rRO/user/discovery.md @@ -2,8 +2,8 @@ title: Descoperiți parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Trasare traseu Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/ro-rRO/user/messages-and-channels.md b/docs/ro-rRO/user/messages-and-channels.md index 97d164e87..cd8660531 100644 --- a/docs/ro-rRO/user/messages-and-channels.md +++ b/docs/ro-rRO/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/ro-rRO/user/node-metrics.md b/docs/ro-rRO/user/node-metrics.md index 3ebfede1b..462bcec7e 100644 --- a/docs/ro-rRO/user/node-metrics.md +++ b/docs/ro-rRO/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Descriere | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Descriere | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Acceptabil | | < -10 dB | Poor | +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. + ## Valori putere Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/ro-rRO/user/nodes.md b/docs/ro-rRO/user/nodes.md index 097a27a52..17a438c38 100644 --- a/docs/ro-rRO/user/nodes.md +++ b/docs/ro-rRO/user/nodes.md @@ -2,7 +2,7 @@ title: Noduri parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Ultima recepție | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distanță | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/ro-rRO/user/telemetry-and-sensors.md b/docs/ro-rRO/user/telemetry-and-sensors.md index 9ea9e4cd3..7a845ebe2 100644 --- a/docs/ro-rRO/user/telemetry-and-sensors.md +++ b/docs/ro-rRO/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/ru-rRU/user/android-auto.md b/docs/ru-rRU/user/android-auto.md new file mode 100644 index 000000000..4d310ba5e --- /dev/null +++ b/docs/ru-rRU/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: Руководство пользователя +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Обзор + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Сообщения + +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. + +## Ноды + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Связанные темы + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/ru-rRU/user/app-functions.md b/docs/ru-rRU/user/app-functions.md new file mode 100644 index 000000000..7f0564d7d --- /dev/null +++ b/docs/ru-rRU/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: Руководство пользователя +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Связанные темы + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/ru-rRU/user/desktop.md b/docs/ru-rRU/user/desktop.md index d3816ed37..a6bfe8627 100644 --- a/docs/ru-rRU/user/desktop.md +++ b/docs/ru-rRU/user/desktop.md @@ -2,7 +2,7 @@ title: Настольное приложение parent: Руководство пользователя nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Заметки | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Обмен сообщениями | ✓ | ✓ | Полное равенство | -| Список узлов | ✓ | ✓ | Полное равенство | -| Карта | ✓ | ✓ | Полное равенство | -| Настройки | ✓ | ✓ | Полное равенство | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Виджеты | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Заметки | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Обмен сообщениями | ✓ | ✓ | Полное равенство | +| Список узлов | ✓ | ✓ | Полное равенство | +| Карта | ✓ | ✓ | Полное равенство | +| Настройки | ✓ | ✓ | Полное равенство | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Виджеты | ✓ | ✗ | 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/ru-rRU/user/discovery.md b/docs/ru-rRU/user/discovery.md index bc316cd08..92c568a30 100644 --- a/docs/ru-rRU/user/discovery.md +++ b/docs/ru-rRU/user/discovery.md @@ -2,8 +2,8 @@ title: Обнаружение parent: Руководство пользователя nav_order: 12 -last_updated: 2026-05-13 -description: Исследуйте вашу mesh-сеть — трассировка, карты соседей и инструменты обнаружения нод. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Инструменты обнаружения помогают понять, **как** твоя 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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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: + +| Управление | Описание | +| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Чтение результатов + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Трассировка маршрута Трассировка показывает точный путь, который сообщение проходит от твоей ноды до любой другой ноды в сети. Это самый полезный инструмент для отладки проблем с подключением. diff --git a/docs/ru-rRU/user/messages-and-channels.md b/docs/ru-rRU/user/messages-and-channels.md index 6e8e3ceeb..ff87111be 100644 --- a/docs/ru-rRU/user/messages-and-channels.md +++ b/docs/ru-rRU/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: Руководство пользователя nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/ru-rRU/user/node-metrics.md b/docs/ru-rRU/user/node-metrics.md index 5c8d165dc..95a7d8e36 100644 --- a/docs/ru-rRU/user/node-metrics.md +++ b/docs/ru-rRU/user/node-metrics.md @@ -2,8 +2,8 @@ title: Метрики ноды parent: Руководство пользователя nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Единица | Описание | +| --------------------- | ------- | ---------------------------------------------------- | +| 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 | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Показатели сигнала Radio signal quality information: -| Metric | Описание | -| ---------- | ----------------------------------------------------------------------------- | -| Сигнал/шум | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| Metric | Описание | +| ----------- | ------------------------------------------------------------------------------ | +| Сигнал/шум | 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 @@ -64,13 +97,15 @@ Radio signal quality information: | > 10 dB | Excellent | | 0 to 10 dB | Хороший | | -10 to 0 dB | Средний | -| < -10 dB | Poor | +| < -10 dB | Слабо | + +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. ## Метрики питания Power management telemetry (requires INA sensor or compatible hardware): -| Metric | Описание | +| Метрическая | Описание | | ----------- | ----------------------- | | Bus Voltage | Supply voltage | | Ток | Power draw in milliamps | @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/ru-rRU/user/nodes.md b/docs/ru-rRU/user/nodes.md index 83e3d7771..8814804c2 100644 --- a/docs/ru-rRU/user/nodes.md +++ b/docs/ru-rRU/user/nodes.md @@ -2,7 +2,7 @@ title: Ноды parent: Руководство пользователя nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Просматривайте, фильтруйте и сортируйте ноды сети — просматривайте подробности, качество сигнала, роли и быстрые действия. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Последний раз слышен | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Расстояние | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/ru-rRU/user/telemetry-and-sensors.md b/docs/ru-rRU/user/telemetry-and-sensors.md index a6de0cf32..b94295a7a 100644 --- a/docs/ru-rRU/user/telemetry-and-sensors.md +++ b/docs/ru-rRU/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/sk-rSK/user/android-auto.md b/docs/sk-rSK/user/android-auto.md new file mode 100644 index 000000000..ffd44b406 --- /dev/null +++ b/docs/sk-rSK/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Správy + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/sk-rSK/user/app-functions.md b/docs/sk-rSK/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/sk-rSK/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/sk-rSK/user/desktop.md b/docs/sk-rSK/user/desktop.md index 5e3586d9a..9905478b3 100644 --- a/docs/sk-rSK/user/desktop.md +++ b/docs/sk-rSK/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Mapa | ✓ | ✓ | Full parity | -| Nastavenia | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Mapa | ✓ | ✓ | Full parity | +| Nastavenia | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/sk-rSK/user/discovery.md b/docs/sk-rSK/user/discovery.md index b5555a7ef..ff58020c2 100644 --- a/docs/sk-rSK/user/discovery.md +++ b/docs/sk-rSK/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Trasovanie Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/sk-rSK/user/messages-and-channels.md b/docs/sk-rSK/user/messages-and-channels.md index 14fdbd570..0734650a5 100644 --- a/docs/sk-rSK/user/messages-and-channels.md +++ b/docs/sk-rSK/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/sk-rSK/user/node-metrics.md b/docs/sk-rSK/user/node-metrics.md index b82f2cd81..68502f83d 100644 --- a/docs/sk-rSK/user/node-metrics.md +++ b/docs/sk-rSK/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Popis | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Popis | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Primeraný | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/sk-rSK/user/nodes.md b/docs/sk-rSK/user/nodes.md index 0cb5135d9..610ca2264 100644 --- a/docs/sk-rSK/user/nodes.md +++ b/docs/sk-rSK/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Posledný príjem | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Vzdialenosť | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/sk-rSK/user/telemetry-and-sensors.md b/docs/sk-rSK/user/telemetry-and-sensors.md index f57726bed..3699eef83 100644 --- a/docs/sk-rSK/user/telemetry-and-sensors.md +++ b/docs/sk-rSK/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/sl-rSI/user/android-auto.md b/docs/sl-rSI/user/android-auto.md new file mode 100644 index 000000000..aeb53435d --- /dev/null +++ b/docs/sl-rSI/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Messages + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/sl-rSI/user/app-functions.md b/docs/sl-rSI/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/sl-rSI/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/sl-rSI/user/desktop.md b/docs/sl-rSI/user/desktop.md index 1af615e66..e69b44554 100644 --- a/docs/sl-rSI/user/desktop.md +++ b/docs/sl-rSI/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Settings | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Settings | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/sl-rSI/user/discovery.md b/docs/sl-rSI/user/discovery.md index 4105c3028..025717517 100644 --- a/docs/sl-rSI/user/discovery.md +++ b/docs/sl-rSI/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Pot Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/sl-rSI/user/messages-and-channels.md b/docs/sl-rSI/user/messages-and-channels.md index dd877b94c..db9772a1e 100644 --- a/docs/sl-rSI/user/messages-and-channels.md +++ b/docs/sl-rSI/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/sl-rSI/user/node-metrics.md b/docs/sl-rSI/user/node-metrics.md index 93c7c192f..9fcf82ec9 100644 --- a/docs/sl-rSI/user/node-metrics.md +++ b/docs/sl-rSI/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Opis | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Opis | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Precejšen | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/sl-rSI/user/nodes.md b/docs/sl-rSI/user/nodes.md index e8ff8cb87..2cdc25337 100644 --- a/docs/sl-rSI/user/nodes.md +++ b/docs/sl-rSI/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Nazadnje slišano | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Razdalja | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/sl-rSI/user/telemetry-and-sensors.md b/docs/sl-rSI/user/telemetry-and-sensors.md index c25adb884..bddc244fd 100644 --- a/docs/sl-rSI/user/telemetry-and-sensors.md +++ b/docs/sl-rSI/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/sq-rAL/user/android-auto.md b/docs/sq-rAL/user/android-auto.md new file mode 100644 index 000000000..c2e9aa1b8 --- /dev/null +++ b/docs/sq-rAL/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## 訊息 + +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. + +## Nodes + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/sq-rAL/user/app-functions.md b/docs/sq-rAL/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/sq-rAL/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/sq-rAL/user/desktop.md b/docs/sq-rAL/user/desktop.md index 1af615e66..e69b44554 100644 --- a/docs/sq-rAL/user/desktop.md +++ b/docs/sq-rAL/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Map | ✓ | ✓ | Full parity | -| Settings | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Map | ✓ | ✓ | Full parity | +| Settings | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| Notifications | ✓ | ✓ | Native OS notifications | +| Widgets | ✓ | ✗ | Android-only | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/sq-rAL/user/discovery.md b/docs/sq-rAL/user/discovery.md index 1c5d754a9..bd19c10ac 100644 --- a/docs/sq-rAL/user/discovery.md +++ b/docs/sq-rAL/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/sq-rAL/user/messages-and-channels.md b/docs/sq-rAL/user/messages-and-channels.md index e766755b7..e90d48d1e 100644 --- a/docs/sq-rAL/user/messages-and-channels.md +++ b/docs/sq-rAL/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/sq-rAL/user/node-metrics.md b/docs/sq-rAL/user/node-metrics.md index 36b3a13c8..654097288 100644 --- a/docs/sq-rAL/user/node-metrics.md +++ b/docs/sq-rAL/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Përshkrimi | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics 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) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Mesatar | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/sq-rAL/user/nodes.md b/docs/sq-rAL/user/nodes.md index 242ac35b5..92f1cf2e9 100644 --- a/docs/sq-rAL/user/nodes.md +++ b/docs/sq-rAL/user/nodes.md @@ -2,7 +2,7 @@ title: Nodes parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | I fundit që u dëgjua | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Distanca | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/sq-rAL/user/telemetry-and-sensors.md b/docs/sq-rAL/user/telemetry-and-sensors.md index 0290e914e..48f202fa1 100644 --- a/docs/sq-rAL/user/telemetry-and-sensors.md +++ b/docs/sq-rAL/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/sr-rLatn/user/android-auto.md b/docs/sr-rLatn/user/android-auto.md new file mode 100644 index 000000000..19fdfefe9 --- /dev/null +++ b/docs/sr-rLatn/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Поруке + +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. + +## Чворови + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/sr-rLatn/user/app-functions.md b/docs/sr-rLatn/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/sr-rLatn/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/sr-rLatn/user/desktop.md b/docs/sr-rLatn/user/desktop.md index 54239c550..8af92eb4b 100644 --- a/docs/sr-rLatn/user/desktop.md +++ b/docs/sr-rLatn/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Белешке | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Мапа | ✓ | ✓ | Full parity | -| Подешавања | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Белешке | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Мапа | ✓ | ✓ | Full parity | +| Подешавања | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/sr-rLatn/user/discovery.md b/docs/sr-rLatn/user/discovery.md index 7c49eda7d..8911fe79a 100644 --- a/docs/sr-rLatn/user/discovery.md +++ b/docs/sr-rLatn/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Праћење руте 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. diff --git a/docs/sr-rLatn/user/messages-and-channels.md b/docs/sr-rLatn/user/messages-and-channels.md index 0286ce57e..7cfd6834c 100644 --- a/docs/sr-rLatn/user/messages-and-channels.md +++ b/docs/sr-rLatn/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/sr-rLatn/user/node-metrics.md b/docs/sr-rLatn/user/node-metrics.md index 8042e9e12..b17a30a28 100644 --- a/docs/sr-rLatn/user/node-metrics.md +++ b/docs/sr-rLatn/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Метрика | Unit | Опис | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Метрика | Опис | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| Метрика | Опис | +| ----------- | ------------------------------------------------------------------------------ | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Prihvatljiv | | < -10 dB | Poor | +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. + ## Мерни подаци о снази Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/sr-rLatn/user/nodes.md b/docs/sr-rLatn/user/nodes.md index b7ee642ad..488771943 100644 --- a/docs/sr-rLatn/user/nodes.md +++ b/docs/sr-rLatn/user/nodes.md @@ -2,7 +2,7 @@ title: Чворови parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Poslednji put viđeno | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Udaljenost | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/sr-rLatn/user/telemetry-and-sensors.md b/docs/sr-rLatn/user/telemetry-and-sensors.md index a0c23c9c8..53e949576 100644 --- a/docs/sr-rLatn/user/telemetry-and-sensors.md +++ b/docs/sr-rLatn/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/srp/user/android-auto.md b/docs/srp/user/android-auto.md new file mode 100644 index 000000000..19fdfefe9 --- /dev/null +++ b/docs/srp/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Поруке + +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. + +## Чворови + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/srp/user/app-functions.md b/docs/srp/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/srp/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/srp/user/desktop.md b/docs/srp/user/desktop.md index 54239c550..8af92eb4b 100644 --- a/docs/srp/user/desktop.md +++ b/docs/srp/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Белешке | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Мапа | ✓ | ✓ | Full parity | -| Подешавања | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Белешке | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Мапа | ✓ | ✓ | Full parity | +| Подешавања | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/srp/user/discovery.md b/docs/srp/user/discovery.md index 7c49eda7d..8911fe79a 100644 --- a/docs/srp/user/discovery.md +++ b/docs/srp/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Праћење руте 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. diff --git a/docs/srp/user/messages-and-channels.md b/docs/srp/user/messages-and-channels.md index f8395a86f..d89e7de6c 100644 --- a/docs/srp/user/messages-and-channels.md +++ b/docs/srp/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/srp/user/node-metrics.md b/docs/srp/user/node-metrics.md index bd7e35939..e794b47e6 100644 --- a/docs/srp/user/node-metrics.md +++ b/docs/srp/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Метрика | Unit | Опис | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Метрика | Опис | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| Метрика | Опис | +| ----------- | ------------------------------------------------------------------------------ | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Прихватљив | | < -10 dB | Poor | +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. + ## Мерни подаци о снази Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/srp/user/nodes.md b/docs/srp/user/nodes.md index 9f938e874..0fef4de05 100644 --- a/docs/srp/user/nodes.md +++ b/docs/srp/user/nodes.md @@ -2,7 +2,7 @@ title: Чворови parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Последње откривање | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Раздаљина | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/srp/user/telemetry-and-sensors.md b/docs/srp/user/telemetry-and-sensors.md index a0c23c9c8..53e949576 100644 --- a/docs/srp/user/telemetry-and-sensors.md +++ b/docs/srp/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/sv-rSE/user/android-auto.md b/docs/sv-rSE/user/android-auto.md new file mode 100644 index 000000000..b15a05d75 --- /dev/null +++ b/docs/sv-rSE/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: Användarguide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Meddelanden + +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. + +## Noder + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/sv-rSE/user/app-functions.md b/docs/sv-rSE/user/app-functions.md new file mode 100644 index 000000000..06d602741 --- /dev/null +++ b/docs/sv-rSE/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: Användarguide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/sv-rSE/user/desktop.md b/docs/sv-rSE/user/desktop.md index 46443c090..957b0674e 100644 --- a/docs/sv-rSE/user/desktop.md +++ b/docs/sv-rSE/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Anteckningar | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Karta | ✓ | ✓ | Full parity | -| Inställningar | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Anteckningar | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Karta | ✓ | ✓ | Full parity | +| Inställningar | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/sv-rSE/user/discovery.md b/docs/sv-rSE/user/discovery.md index ebc2e4fcf..9f9e2b921 100644 --- a/docs/sv-rSE/user/discovery.md +++ b/docs/sv-rSE/user/discovery.md @@ -2,8 +2,8 @@ title: Upptäckt parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Traceroute (spåra rutt) Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/sv-rSE/user/messages-and-channels.md b/docs/sv-rSE/user/messages-and-channels.md index 344af7507..dd21a081d 100644 --- a/docs/sv-rSE/user/messages-and-channels.md +++ b/docs/sv-rSE/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/sv-rSE/user/node-metrics.md b/docs/sv-rSE/user/node-metrics.md index fa06389f7..d0e01d50f 100644 --- a/docs/sv-rSE/user/node-metrics.md +++ b/docs/sv-rSE/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Beskrivning | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Beskrivning | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Ok | | < -10 dB | Poor | +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. + ## Strömdata Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/sv-rSE/user/nodes.md b/docs/sv-rSE/user/nodes.md index f5849e292..734fca704 100644 --- a/docs/sv-rSE/user/nodes.md +++ b/docs/sv-rSE/user/nodes.md @@ -2,7 +2,7 @@ title: Noder parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Senast hörd | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Avstånd | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/sv-rSE/user/telemetry-and-sensors.md b/docs/sv-rSE/user/telemetry-and-sensors.md index 8af95345a..c90a506a1 100644 --- a/docs/sv-rSE/user/telemetry-and-sensors.md +++ b/docs/sv-rSE/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/tr-rTR/user/android-auto.md b/docs/tr-rTR/user/android-auto.md new file mode 100644 index 000000000..e7bb3395c --- /dev/null +++ b/docs/tr-rTR/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Genel Bakış + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Mesajlar + +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. + +## Nodelar + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/tr-rTR/user/app-functions.md b/docs/tr-rTR/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/tr-rTR/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/tr-rTR/user/desktop.md b/docs/tr-rTR/user/desktop.md index 8e398aef9..247380c59 100644 --- a/docs/tr-rTR/user/desktop.md +++ b/docs/tr-rTR/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Notes | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Harita | ✓ | ✓ | Full parity | -| Ayarlar | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Notes | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Harita | ✓ | ✓ | Full parity | +| Ayarlar | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/tr-rTR/user/discovery.md b/docs/tr-rTR/user/discovery.md index 1e7753b3d..b9c442616 100644 --- a/docs/tr-rTR/user/discovery.md +++ b/docs/tr-rTR/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Yol izle Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems. diff --git a/docs/tr-rTR/user/messages-and-channels.md b/docs/tr-rTR/user/messages-and-channels.md index b7b90be13..0b31e2b32 100644 --- a/docs/tr-rTR/user/messages-and-channels.md +++ b/docs/tr-rTR/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/tr-rTR/user/node-metrics.md b/docs/tr-rTR/user/node-metrics.md index 8966da463..3c98dd65a 100644 --- a/docs/tr-rTR/user/node-metrics.md +++ b/docs/tr-rTR/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Açıklaması | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics 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) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | İdare Eder | | < -10 dB | Poor | +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. + ## Power Metrics Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/tr-rTR/user/nodes.md b/docs/tr-rTR/user/nodes.md index 6cecdc988..8e7bcd1e4 100644 --- a/docs/tr-rTR/user/nodes.md +++ b/docs/tr-rTR/user/nodes.md @@ -2,7 +2,7 @@ title: Nodelar parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Son duyulma | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Mesafe | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/tr-rTR/user/telemetry-and-sensors.md b/docs/tr-rTR/user/telemetry-and-sensors.md index ddb97c824..c8191f967 100644 --- a/docs/tr-rTR/user/telemetry-and-sensors.md +++ b/docs/tr-rTR/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/uk-rUA/user/android-auto.md b/docs/uk-rUA/user/android-auto.md new file mode 100644 index 000000000..a5726b5ae --- /dev/null +++ b/docs/uk-rUA/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## Overview + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## Повідомлення + +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. + +## Вузли + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/uk-rUA/user/app-functions.md b/docs/uk-rUA/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/uk-rUA/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/uk-rUA/user/desktop.md b/docs/uk-rUA/user/desktop.md index 54ad85ca5..2e2b9f694 100644 --- a/docs/uk-rUA/user/desktop.md +++ b/docs/uk-rUA/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | Нотатки | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| Мапа | ✓ | ✓ | Full parity | -| Налаштування | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | Нотатки | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| Мапа | ✓ | ✓ | Full parity | +| Налаштування | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/uk-rUA/user/discovery.md b/docs/uk-rUA/user/discovery.md index 1d648c907..6c186b7a8 100644 --- a/docs/uk-rUA/user/discovery.md +++ b/docs/uk-rUA/user/discovery.md @@ -2,8 +2,8 @@ title: Discovery parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## Маршрут 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. diff --git a/docs/uk-rUA/user/messages-and-channels.md b/docs/uk-rUA/user/messages-and-channels.md index 63015c2d0..aa7a6b827 100644 --- a/docs/uk-rUA/user/messages-and-channels.md +++ b/docs/uk-rUA/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/uk-rUA/user/node-metrics.md b/docs/uk-rUA/user/node-metrics.md index 8023baa46..142180552 100644 --- a/docs/uk-rUA/user/node-metrics.md +++ b/docs/uk-rUA/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| Metric | Unit | Опис | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| Metric | Опис | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | Задовільний | | < -10 dB | Poor | +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. + ## Показники живлення Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/uk-rUA/user/nodes.md b/docs/uk-rUA/user/nodes.md index 4a066be98..da60dbfc4 100644 --- a/docs/uk-rUA/user/nodes.md +++ b/docs/uk-rUA/user/nodes.md @@ -2,7 +2,7 @@ title: Вузли parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | Востаннє в мережі | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | Відстань | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/uk-rUA/user/telemetry-and-sensors.md b/docs/uk-rUA/user/telemetry-and-sensors.md index e6ebfe8b9..52e39f5b6 100644 --- a/docs/uk-rUA/user/telemetry-and-sensors.md +++ b/docs/uk-rUA/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/zh-rCN/user/android-auto.md b/docs/zh-rCN/user/android-auto.md new file mode 100644 index 000000000..6ea2e7f08 --- /dev/null +++ b/docs/zh-rCN/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## 总览 + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## 消息 + +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. + +## 节点 + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/zh-rCN/user/app-functions.md b/docs/zh-rCN/user/app-functions.md new file mode 100644 index 000000000..373b6bd35 --- /dev/null +++ b/docs/zh-rCN/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## Privacy + +> 🔒 **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. + +## Related Topics + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/zh-rCN/user/desktop.md b/docs/zh-rCN/user/desktop.md index f91df6f9c..c81541b15 100644 --- a/docs/zh-rCN/user/desktop.md +++ b/docs/zh-rCN/user/desktop.md @@ -2,7 +2,7 @@ title: Desktop App parent: User Guide nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts. aliases: - desktop @@ -60,20 +60,24 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/ ## Feature Parity -| Feature | Android | Desktop | 注 | -| ---------------------------------------- | ------- | ------- | -------------------------- | -| Messaging | ✓ | ✓ | Full parity | -| Node List | ✓ | ✓ | Full parity | -| 地图 | ✓ | ✓ | Full parity | -| 设置 | ✓ | ✓ | Full parity | -| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | -| Firmware Update OTA | ✓ | ✗ | Use web flasher | -| Notifications | ✓ | ✓ | Native OS notifications | -| Widgets | ✓ | ✗ | Android-only | -| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only | +| Feature | Android | Desktop | 注 | +| -------------------------------------------- | ------- | ------- | ---------------------------------------------- | +| Messaging | ✓ | ✓ | Full parity | +| Node List | ✓ | ✓ | Full parity | +| 地图 | ✓ | ✓ | Full parity | +| 设置 | ✓ | ✓ | Full parity | +| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | +| Firmware Update OTA | ✓ | ✗ | Use web flasher | +| 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](app-functions). + ## UI Differences The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. diff --git a/docs/zh-rCN/user/discovery.md b/docs/zh-rCN/user/discovery.md index 587dd90b2..f90e79d40 100644 --- a/docs/zh-rCN/user/discovery.md +++ b/docs/zh-rCN/user/discovery.md @@ -2,8 +2,8 @@ title: 发现 parent: User Guide nav_order: 12 -last_updated: 2026-05-13 -description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools. +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-discovery - local-discovery @@ -16,10 +16,83 @@ aliases: Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist. -> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens. +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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### Reading the Results + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## 追踪器 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. diff --git a/docs/zh-rCN/user/messages-and-channels.md b/docs/zh-rCN/user/messages-and-channels.md index 229cbdcd3..4e306094c 100644 --- a/docs/zh-rCN/user/messages-and-channels.md +++ b/docs/zh-rCN/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: Messages & Channels parent: User Guide nav_order: 3 -last_updated: 2026-05-13 -description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions. +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - channels - direct-messages @@ -101,6 +101,19 @@ Pre-configured messages for rapid communication: 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: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 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. diff --git a/docs/zh-rCN/user/node-metrics.md b/docs/zh-rCN/user/node-metrics.md index 91f24c6fd..624bfeaf9 100644 --- a/docs/zh-rCN/user/node-metrics.md +++ b/docs/zh-rCN/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - telemetry @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| 公制 | Unit | 说明 | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## 信号强度 Radio signal quality information: -| 公制 | 说明 | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| Hop Count | Number of mesh hops for last message | +| 公制 | 说明 | +| ----------- | ------------------------------------------------------------------------------ | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | 一般 | | < -10 dB | Poor | +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. + ## 电源计量 Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/zh-rCN/user/nodes.md b/docs/zh-rCN/user/nodes.md index ee088ad02..129d647ac 100644 --- a/docs/zh-rCN/user/nodes.md +++ b/docs/zh-rCN/user/nodes.md @@ -2,7 +2,7 @@ title: 节点 parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | 最后听到 | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | 距离 | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/zh-rCN/user/telemetry-and-sensors.md b/docs/zh-rCN/user/telemetry-and-sensors.md index 46e473270..73b13a438 100644 --- a/docs/zh-rCN/user/telemetry-and-sensors.md +++ b/docs/zh-rCN/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png) diff --git a/docs/zh-rTW/user/android-auto.md b/docs/zh-rTW/user/android-auto.md new file mode 100644 index 000000000..15888b2e8 --- /dev/null +++ b/docs/zh-rTW/user/android-auto.md @@ -0,0 +1,54 @@ +--- +title: Android Auto +parent: User Guide +nav_order: 18 +last_updated: 2026-06-11 +description: Use Meshtastic hands-free on an Android Auto head unit — read messages aloud, reply by voice, and check nodes and mesh status while driving. +aliases: + - android-auto + - car + - head-unit + - auto +--- + +# Android Auto + +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. + +## 總覽 + +When your phone is connected to an Android Auto head unit (or the Desktop Head Unit emulator used for development), Meshtastic appears as a messaging app built with the Android Car App Library. The car interface presents 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. + +## 訊息 + +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. + +## 節點 + +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](nodes) for the full meaning of the information shown. + +## Status + +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. + +## 相關主題 + +- [Messages & Channels](messages-and-channels) — full messaging features on your phone +- [Nodes](nodes) — detailed node list and node-detail information +- [Connections](connections) — how the app connects to your radio + +--- + diff --git a/docs/zh-rTW/user/app-functions.md b/docs/zh-rTW/user/app-functions.md new file mode 100644 index 000000000..92dc6c576 --- /dev/null +++ b/docs/zh-rTW/user/app-functions.md @@ -0,0 +1,63 @@ +--- +title: App Functions +parent: User Guide +nav_order: 19 +last_updated: 2026-06-11 +description: Expose mesh capabilities to the Android system and on-device AI assistants (e.g. Gemini) so they can run mesh workflows without opening the app. +aliases: + - app-functions + - system-ai + - gemini + - assistant-functions +--- + +# App Functions + +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. + +## Enabling App Functions + +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). + +![App Functions screen with master and per-function toggles](../../assets/screenshots/app-functions_settings.png) + +### 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. | + +## 隱私 + +> 🔒 **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. + +## 相關主題 + +- [Messages & Channels](messages-and-channels) — sending messages directly in the app +- [Nodes](nodes) — the node list the read functions draw from +- [Node Metrics](node-metrics) — the telemetry behind Get Mesh Metrics + +--- + diff --git a/docs/zh-rTW/user/desktop.md b/docs/zh-rTW/user/desktop.md index 37fb740ce..e19482298 100644 --- a/docs/zh-rTW/user/desktop.md +++ b/docs/zh-rTW/user/desktop.md @@ -2,7 +2,7 @@ title: 桌面版應用程式 parent: 使用者指南 nav_order: 14 -last_updated: 2026-05-20 +last_updated: 2026-06-11 description: 在 Linux、macOS 及 Windows 上安裝並使用 Meshtastic 桌面版應用程式——涵蓋連線方式、功能對等性與鍵盤快速鍵。 aliases: - 桌面 @@ -60,20 +60,24 @@ Meshtastic 桌面版應用程式透過 Kotlin Multiplatform 與 Android 版共 ## 功能對等性 -| 功能 | Android | 桌面版 | 備註 | -| ------------- | ------- | --- | ------------------- | -| 訊息傳送 | ✓ | ✓ | 完全對等 | -| 節點清單 | ✓ | ✓ | 完全對等 | -| 地圖 | ✓ | ✓ | 完全對等 | -| 設定 | ✓ | ✓ | 完全對等 | -| 藍牙（BLE） | ✓ | ✓ | 桌面版透過 Kable 支援 | -| 韌體 OTA 更新 | ✓ | ✗ | 使用網頁燒錄工具 | -| 通知 | ✓ | ✓ | 原生作業系統通知 | -| 小工具 | ✓ | ✗ | 僅限 Android | -| AI 助理（Chirpy） | ✓\* | ✗ | 僅限 Google 版 Android | +| 功能 | Android | 桌面版 | 備註 | +| -------------------------------------------- | ------- | --- | ---------------------------------------------- | +| 訊息傳送 | ✓ | ✓ | 完全對等 | +| 節點清單 | ✓ | ✓ | 完全對等 | +| 地圖 | ✓ | ✓ | 完全對等 | +| 設定 | ✓ | ✓ | 完全對等 | +| 藍牙（BLE） | ✓ | ✓ | 桌面版透過 Kable 支援 | +| 韌體 OTA 更新 | ✓ | ✗ | 使用網頁燒錄工具 | +| 通知 | ✓ | ✓ | 原生作業系統通知 | +| 小工具 | ✓ | ✗ | 僅限 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](app-functions). + ## 介面差異 桌面版應用程式採用相同的 Compose Multiplatform 介面，並針對較大螢幕與桌面操作方式進行調整。 diff --git a/docs/zh-rTW/user/discovery.md b/docs/zh-rTW/user/discovery.md index c68a58bdb..73e987672 100644 --- a/docs/zh-rTW/user/discovery.md +++ b/docs/zh-rTW/user/discovery.md @@ -2,8 +2,8 @@ title: 尋找 parent: 使用者指南 nav_order: 12 -last_updated: 2026-05-13 -description: 探索您的 mesh 網路——追蹤路由路徑、鄰近節點地圖與節點探索工具。 +last_updated: 2026-06-11 +description: Explore your mesh network — the Local Mesh Discovery scanner, traceroute paths, neighbor maps, and node discovery tools. aliases: - mesh-探索 - 本地-探索 @@ -16,10 +16,83 @@ aliases: 探索工具可協助您了解 mesh 網路的連線方式——哪些節點彼此可以收到訊號、訊息所經過的路徑，以及哪裡存在瓶頸或訊號薄弱的連結。 -> 💡 提示：您不需要專屬的「探索模式」即可開始探索 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. --- +## Local Mesh Discovery (Scanner) + +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 → Local Mesh Discovery**. + +> ⚠️ **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**. +- The current channel is using the **default channel key** (use a unique key first — see [Messages & Channels](messages-and-channels)). +- **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 \** | 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. | + +![Dwell countdown showing time remaining on the current preset](../../assets/screenshots/discovery_dwell_progress.png) + +### 解讀結果 + +When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. + +![Per-preset result card with ranking and collected metrics](../../assets/screenshots/discovery_preset_result.png) + +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. + +--- + +## Manual Exploration + +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. + ## 路由追蹤 路由追蹤可顯示訊息從您的節點到 mesh 網路上任一節點所經過的確切路徑。 這是診斷連線問題最有效的工具。 diff --git a/docs/zh-rTW/user/messages-and-channels.md b/docs/zh-rTW/user/messages-and-channels.md index 5a2bed356..7951a24f0 100644 --- a/docs/zh-rTW/user/messages-and-channels.md +++ b/docs/zh-rTW/user/messages-and-channels.md @@ -2,8 +2,8 @@ title: 訊息與頻道 parent: 使用者指南 nav_order: 3 -last_updated: 2026-05-13 -description: 傳送與接收訊息、管理頻道、設定加密，以及使用快速聊天、訊息回應與訊息動作。 +last_updated: 2026-06-11 +description: Send and receive messages, manage channels, configure encryption, search conversations, and use quick chat, reactions, and message actions. aliases: - 頻道 - direct-messages @@ -101,6 +101,19 @@ Meshtastic 支援兩種通訊模式：頻道廣播與私訊。 頻道清單會顯示每個頻道及其最新訊息預覽。 +### Searching Messages + +You can search the full history of any conversation directly from the chat screen: + +1. Open a conversation (a channel or a direct message). +2. Tap the **search icon** in the top bar. +3. Type into the **Search messages…** field. The search runs as you type, across all stored messages in that conversation. +4. Use the **N / M** result counter and the **previous / next arrows** to jump between matches, which are highlighted in the conversation. + +![Message search bar with result counter and previous/next arrows](../../assets/screenshots/messages_search_bar.png) + +> 💡 **Tip:** Search is full-text and stays within the conversation you opened it from — it doesn't search across other channels or contacts. Matching is fast even on long histories because messages are indexed locally. + ### 訊息泡泡 訊息以對話泡泡的形式顯示 — 已傳送的訊息在右側，收到的訊息在左側。 每個泡泡顯示傳送者、時間戳記及傳遞狀態。 含有回覆的訊息，會在回覆內容上方顯示原始訊息的引用預覽。 diff --git a/docs/zh-rTW/user/node-metrics.md b/docs/zh-rTW/user/node-metrics.md index cedab9a8b..060785dd9 100644 --- a/docs/zh-rTW/user/node-metrics.md +++ b/docs/zh-rTW/user/node-metrics.md @@ -2,8 +2,8 @@ title: Node Metrics parent: User Guide nav_order: 5 -last_updated: 2026-05-13 -description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history. +last_updated: 2026-06-16 +description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics - 遙測 @@ -47,15 +47,48 @@ Environment metrics are charted over time for easy trend analysis — temperatur > 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors. +## Air Quality Metrics + +Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is **separate from the BME680 IAQ reading** listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. + +| 公制（公里/公尺） | 單位 | 描述說明 | +| --------------------- | ----- | ---------------------------------------------------- | +| PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | +| PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | +| PM10 | µg/m³ | Particulate matter up to 10 microns | +| CO₂ | ppm | Carbon dioxide concentration | + +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 | + +![Air quality readings with color-coded CO₂ severity](../../assets/screenshots/node-metrics_air_quality.png) + +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](telemetry-and-sensors) for supported hardware. + ## Signal Metrics Radio signal quality information: -| 公制（公里/公尺） | 描述說明 | -| --------- | ----------------------------------------------------------------------------- | -| SNR | Signal-to-Noise Ratio (higher is better) | -| RSSI | Received Signal Strength Indicator (closer to 0 is better) | -| 跳躍次數 | Number of mesh hops for last message | +| 公制（公里/公尺） | 描述說明 | +| ----------- | ------------------------------------------------------------------------------ | +| 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 @@ -66,6 +99,8 @@ Radio signal quality information: | -10 to 0 dB | 普通 | | < -10 dB | Poor | +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. + ## 電源計量資料 Power management telemetry (requires INA sensor or compatible hardware): @@ -128,4 +163,3 @@ The position tab shows location data for nodes that share GPS: - [Units & Locale](units-and-locale) — temperature, distance, and speed display formats --- - diff --git a/docs/zh-rTW/user/nodes.md b/docs/zh-rTW/user/nodes.md index 9426083f1..959e98caa 100644 --- a/docs/zh-rTW/user/nodes.md +++ b/docs/zh-rTW/user/nodes.md @@ -2,7 +2,7 @@ title: 節點 parent: User Guide nav_order: 4 -last_updated: 2026-05-20 +last_updated: 2026-06-02 description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. aliases: - node-list @@ -142,6 +142,12 @@ Inline status indicators show key metrics at a glance: | 最近一次收到排序 | ![Last heard](../../assets/screenshots/nodes_last_heard.png) | | 距離 | ![Distance](../../assets/screenshots/nodes_distance_info.png) | +### 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 → Device Links**. + ## Related Topics - [Node Metrics](node-metrics) — detailed telemetry dashboards for each node diff --git a/docs/zh-rTW/user/telemetry-and-sensors.md b/docs/zh-rTW/user/telemetry-and-sensors.md index cc2f009d1..097b6e292 100644 --- a/docs/zh-rTW/user/telemetry-and-sensors.md +++ b/docs/zh-rTW/user/telemetry-and-sensors.md @@ -92,6 +92,26 @@ Useful for monitoring solar charging or battery health on remote nodes. > ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh. +## Air Quality Metrics + +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 | + +The CO₂ reading is color-coded by severity: + +- 🟢 **Good** (< 1000 ppm) — normal indoor levels +- 🟡 **Moderate** (1000–2000 ppm) — elevated, consider ventilation +- 🟠 **Poor** (2000–5000 ppm) — drowsiness, poor concentration +- 🔴 **Hazardous** (≥ 5000 ppm) — immediate health concern + +Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV. + ## Viewing Telemetry 1. Navigate to **Nodes** and select a node. @@ -99,6 +119,7 @@ Useful for monitoring solar charging or battery health on remote nodes. - Device Metrics (always available) - Environment Metrics (if sensors present) - Power Metrics (if INA sensor present) + - Air Quality Metrics (if PM/CO₂ sensor present) 3. Historical graphs show trends over time. ![Telemetry actions](../../assets/screenshots/node-metrics_telemetric_actions.png)