From d450660cd26597524dea91a22ae77d5a4e5f124c Mon Sep 17 00:00:00 2001 From: James Rich <2199651+jamesarich@users.noreply.github.com> Date: Tue, 29 Sep 2026 13:24:43 +0000 Subject: [PATCH] chore: Scheduled updates (Firmware, Hardware, Translations) (#7443) Co-authored-by: github-merge-queue[bot] <118344674+github-merge-queue[bot]@users.noreply.github.com> --- docs/ar-rSA/user/node-metrics.md | 4 ++-- docs/be-rBY/user/node-metrics.md | 4 ++-- docs/bg-rBG/user/node-metrics.md | 4 ++-- docs/ca-rES/user/node-metrics.md | 4 ++-- docs/cs-rCZ/user/node-metrics.md | 4 ++-- docs/de-rDE/user/node-metrics.md | 4 ++-- docs/el-rGR/user/node-metrics.md | 4 ++-- docs/es-rES/user/node-metrics.md | 4 ++-- docs/et-rEE/user/node-metrics.md | 4 ++-- docs/fi-rFI/user/node-metrics.md | 4 ++-- docs/fr-rCA/user/node-metrics.md | 4 ++-- docs/fr-rFR/user/node-metrics.md | 4 ++-- docs/ga-rIE/user/node-metrics.md | 4 ++-- docs/gl-rES/user/node-metrics.md | 4 ++-- docs/hr-rHR/user/node-metrics.md | 4 ++-- docs/ht-rHT/user/node-metrics.md | 4 ++-- docs/hu-rHU/user/node-metrics.md | 4 ++-- docs/is-rIS/user/node-metrics.md | 4 ++-- docs/it-rIT/user/node-metrics.md | 4 ++-- docs/iw-rIL/user/node-metrics.md | 4 ++-- docs/ja-rJP/user/node-metrics.md | 4 ++-- docs/ko-rKR/user/node-metrics.md | 4 ++-- docs/lt-rLT/user/node-metrics.md | 4 ++-- docs/nl-rNL/user/node-metrics.md | 4 ++-- docs/no-rNO/user/node-metrics.md | 4 ++-- docs/pl-rPL/user/node-metrics.md | 4 ++-- docs/pt-rBR/user/node-metrics.md | 4 ++-- docs/pt-rPT/user/node-metrics.md | 4 ++-- docs/ro-rRO/user/node-metrics.md | 4 ++-- docs/ru-rRU/user/node-metrics.md | 4 ++-- docs/sk-rSK/user/node-metrics.md | 4 ++-- docs/sl-rSI/user/node-metrics.md | 4 ++-- docs/sq-rAL/user/node-metrics.md | 4 ++-- docs/sr-rLatn/user/node-metrics.md | 4 ++-- docs/srp/user/node-metrics.md | 4 ++-- docs/sv-rSE/user/node-metrics.md | 4 ++-- docs/tr-rTR/user/node-metrics.md | 4 ++-- docs/uk-rUA/user/node-metrics.md | 4 ++-- docs/zh-rCN/user/node-metrics.md | 4 ++-- docs/zh-rTW/user/node-metrics.md | 4 ++-- 40 files changed, 80 insertions(+), 80 deletions(-) diff --git a/docs/ar-rSA/user/node-metrics.md b/docs/ar-rSA/user/node-metrics.md index 70c99569a8..1730816b1e 100644 --- a/docs/ar-rSA/user/node-metrics.md +++ b/docs/ar-rSA/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/be-rBY/user/node-metrics.md b/docs/be-rBY/user/node-metrics.md index 614e966a08..bb24a8720b 100644 --- a/docs/be-rBY/user/node-metrics.md +++ b/docs/be-rBY/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/bg-rBG/user/node-metrics.md b/docs/bg-rBG/user/node-metrics.md index da0db79748..dc999ada4e 100644 --- a/docs/bg-rBG/user/node-metrics.md +++ b/docs/bg-rBG/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/ca-rES/user/node-metrics.md b/docs/ca-rES/user/node-metrics.md index 4663c41a46..ae5ac9244f 100644 --- a/docs/ca-rES/user/node-metrics.md +++ b/docs/ca-rES/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/cs-rCZ/user/node-metrics.md b/docs/cs-rCZ/user/node-metrics.md index 39c7e1f9fc..3933fdf3a7 100644 --- a/docs/cs-rCZ/user/node-metrics.md +++ b/docs/cs-rCZ/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/de-rDE/user/node-metrics.md b/docs/de-rDE/user/node-metrics.md index 5735904679..c2b7ce61b5 100644 --- a/docs/de-rDE/user/node-metrics.md +++ b/docs/de-rDE/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/el-rGR/user/node-metrics.md b/docs/el-rGR/user/node-metrics.md index ed5589479e..b8b301fbae 100644 --- a/docs/el-rGR/user/node-metrics.md +++ b/docs/el-rGR/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/es-rES/user/node-metrics.md b/docs/es-rES/user/node-metrics.md index 831a596ec7..0d4cc76689 100644 --- a/docs/es-rES/user/node-metrics.md +++ b/docs/es-rES/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/et-rEE/user/node-metrics.md b/docs/et-rEE/user/node-metrics.md index c4b60741f5..cdb84dd98f 100644 --- a/docs/et-rEE/user/node-metrics.md +++ b/docs/et-rEE/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Sõlme mõõdikud nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemeetria armatuurlauad iga võrgusõlme kohta – seadme tervis, keskkonnaandurid, õhu kvaliteet, signaali kvaliteet, võimsus, marsruut ja asukoha ajalugu. aliases: - meetriline @@ -151,7 +151,7 @@ Traceroute näitab sõnumi teed läbi kärgvõrgu: ### Traceroute'i tulemuste lugemine -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/fi-rFI/user/node-metrics.md b/docs/fi-rFI/user/node-metrics.md index 5c88945586..e4bebfe9e7 100644 --- a/docs/fi-rFI/user/node-metrics.md +++ b/docs/fi-rFI/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Radion mittarit nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetrianäkymät jokaiselle verkon radiolle — laitteen kunto, ympäristöanturit, ilmanlaatu, signaalin laatu, virta, reitinselvitys ja sijaintihistoria. aliases: - mittarit @@ -151,7 +151,7 @@ Reitinselvitys näyttää viestin kulkeman reitin verkossa: ### Reitinselvityksen tulosten lukeminen -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/fr-rCA/user/node-metrics.md b/docs/fr-rCA/user/node-metrics.md index 2342654488..d1d3339058 100644 --- a/docs/fr-rCA/user/node-metrics.md +++ b/docs/fr-rCA/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/fr-rFR/user/node-metrics.md b/docs/fr-rFR/user/node-metrics.md index 2342654488..d1d3339058 100644 --- a/docs/fr-rFR/user/node-metrics.md +++ b/docs/fr-rFR/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/ga-rIE/user/node-metrics.md b/docs/ga-rIE/user/node-metrics.md index 970f303dcf..7dc3079999 100644 --- a/docs/ga-rIE/user/node-metrics.md +++ b/docs/ga-rIE/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/gl-rES/user/node-metrics.md b/docs/gl-rES/user/node-metrics.md index eb44d49e05..4380811e55 100644 --- a/docs/gl-rES/user/node-metrics.md +++ b/docs/gl-rES/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/hr-rHR/user/node-metrics.md b/docs/hr-rHR/user/node-metrics.md index b7ae58fe92..1326df7308 100644 --- a/docs/hr-rHR/user/node-metrics.md +++ b/docs/hr-rHR/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/ht-rHT/user/node-metrics.md b/docs/ht-rHT/user/node-metrics.md index 88e58faa8f..5e5711d74d 100644 --- a/docs/ht-rHT/user/node-metrics.md +++ b/docs/ht-rHT/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/hu-rHU/user/node-metrics.md b/docs/hu-rHU/user/node-metrics.md index c9dabf58b2..81790f95cd 100644 --- a/docs/hu-rHU/user/node-metrics.md +++ b/docs/hu-rHU/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/is-rIS/user/node-metrics.md b/docs/is-rIS/user/node-metrics.md index 726f96513f..ad6766fabd 100644 --- a/docs/is-rIS/user/node-metrics.md +++ b/docs/is-rIS/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/it-rIT/user/node-metrics.md b/docs/it-rIT/user/node-metrics.md index e26a97ced8..e0aea97171 100644 --- a/docs/it-rIT/user/node-metrics.md +++ b/docs/it-rIT/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/iw-rIL/user/node-metrics.md b/docs/iw-rIL/user/node-metrics.md index 0d6b51ec54..32d0631b5c 100644 --- a/docs/iw-rIL/user/node-metrics.md +++ b/docs/iw-rIL/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/ja-rJP/user/node-metrics.md b/docs/ja-rJP/user/node-metrics.md index e266a4bba0..2231795bce 100644 --- a/docs/ja-rJP/user/node-metrics.md +++ b/docs/ja-rJP/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: ノードメトリクス nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: 各メッシュノードのテレメトリダッシュボード。デバイスの状態、環境センサー、大気質、信号品質、電力、ルート追跡、位置履歴を表示します。 aliases: - metrics @@ -151,7 +151,7 @@ The node detail screen shows cards for channels 1 to 3. Use the chart button on ### ルート追跡の結果の見方 -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/ko-rKR/user/node-metrics.md b/docs/ko-rKR/user/node-metrics.md index f167c4b194..2b556b3056 100644 --- a/docs/ko-rKR/user/node-metrics.md +++ b/docs/ko-rKR/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/lt-rLT/user/node-metrics.md b/docs/lt-rLT/user/node-metrics.md index 282c86fa06..07067c570d 100644 --- a/docs/lt-rLT/user/node-metrics.md +++ b/docs/lt-rLT/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/nl-rNL/user/node-metrics.md b/docs/nl-rNL/user/node-metrics.md index 68d17205ea..bedf1be6a4 100644 --- a/docs/nl-rNL/user/node-metrics.md +++ b/docs/nl-rNL/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/no-rNO/user/node-metrics.md b/docs/no-rNO/user/node-metrics.md index 65df40f059..31961d7ed7 100644 --- a/docs/no-rNO/user/node-metrics.md +++ b/docs/no-rNO/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/pl-rPL/user/node-metrics.md b/docs/pl-rPL/user/node-metrics.md index e7dd538525..ca848ab0d0 100644 --- a/docs/pl-rPL/user/node-metrics.md +++ b/docs/pl-rPL/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/pt-rBR/user/node-metrics.md b/docs/pt-rBR/user/node-metrics.md index d63f9dae4a..d41d541648 100644 --- a/docs/pt-rBR/user/node-metrics.md +++ b/docs/pt-rBR/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/pt-rPT/user/node-metrics.md b/docs/pt-rPT/user/node-metrics.md index 0090ff6d55..749f632705 100644 --- a/docs/pt-rPT/user/node-metrics.md +++ b/docs/pt-rPT/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/ro-rRO/user/node-metrics.md b/docs/ro-rRO/user/node-metrics.md index 8df0e077df..5526e4e249 100644 --- a/docs/ro-rRO/user/node-metrics.md +++ b/docs/ro-rRO/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/ru-rRU/user/node-metrics.md b/docs/ru-rRU/user/node-metrics.md index e4b9ea8e62..c85e95fd3a 100644 --- a/docs/ru-rRU/user/node-metrics.md +++ b/docs/ru-rRU/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Метрики ноды nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Панели телеметрии для каждой ноды mesh-сети — состояние устройства, датчики окружающей среды, качество воздуха, качество сигнала, питание, трассировка и история местоположения. aliases: - metrics @@ -151,7 +151,7 @@ The node detail screen shows cards for channels 1 to 3. Use the chart button on ### Чтение результатов трассировки -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/sk-rSK/user/node-metrics.md b/docs/sk-rSK/user/node-metrics.md index 7e0ae8df8d..64af5c3626 100644 --- a/docs/sk-rSK/user/node-metrics.md +++ b/docs/sk-rSK/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/sl-rSI/user/node-metrics.md b/docs/sl-rSI/user/node-metrics.md index 95d18ed760..8625592c72 100644 --- a/docs/sl-rSI/user/node-metrics.md +++ b/docs/sl-rSI/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/sq-rAL/user/node-metrics.md b/docs/sq-rAL/user/node-metrics.md index ffe56e6e86..6a57fe01c9 100644 --- a/docs/sq-rAL/user/node-metrics.md +++ b/docs/sq-rAL/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/sr-rLatn/user/node-metrics.md b/docs/sr-rLatn/user/node-metrics.md index b4010b08b8..fcfac86ea3 100644 --- a/docs/sr-rLatn/user/node-metrics.md +++ b/docs/sr-rLatn/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/srp/user/node-metrics.md b/docs/srp/user/node-metrics.md index 7a431cb990..27cee4bf56 100644 --- a/docs/srp/user/node-metrics.md +++ b/docs/srp/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/sv-rSE/user/node-metrics.md b/docs/sv-rSE/user/node-metrics.md index 6ed622096e..7d7cc2b5f5 100644 --- a/docs/sv-rSE/user/node-metrics.md +++ b/docs/sv-rSE/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/tr-rTR/user/node-metrics.md b/docs/tr-rTR/user/node-metrics.md index 29b75403c1..7ffb3ed980 100644 --- a/docs/tr-rTR/user/node-metrics.md +++ b/docs/tr-rTR/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/uk-rUA/user/node-metrics.md b/docs/uk-rUA/user/node-metrics.md index 9ad5b8de79..aa7488848b 100644 --- a/docs/uk-rUA/user/node-metrics.md +++ b/docs/uk-rUA/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/zh-rCN/user/node-metrics.md b/docs/zh-rCN/user/node-metrics.md index 69fdb7666b..c7aa9e1f39 100644 --- a/docs/zh-rCN/user/node-metrics.md +++ b/docs/zh-rCN/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. diff --git a/docs/zh-rTW/user/node-metrics.md b/docs/zh-rTW/user/node-metrics.md index 539d19f9de..47ccff45e1 100644 --- a/docs/zh-rTW/user/node-metrics.md +++ b/docs/zh-rTW/user/node-metrics.md @@ -1,7 +1,7 @@ --- title: Node Metrics nav_order: 5 -last_updated: 2026-09-09 +last_updated: 2026-09-28 description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history. aliases: - metrics @@ -151,7 +151,7 @@ Traceroute shows the path a message takes through the mesh: ### Reading Traceroute Results -A traceroute is a round trip, so each saved result carries a hop count in each direction — **Forward Hops** and **Return Hops** — and the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. +A traceroute is a round trip, so each saved result carries a hop count in each direction, **Forward Hops** and **Return Hops**, plus the **Round Trip** time in seconds. A result marked **Direct** reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. That view offers **View on map**, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked **No Response** means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.