Repository navigation
Description
[PARENT] [ALIGNMENT]: Sensor Telemetry UI/UX
Decision
A given sensor reading shows with the same category, unit, precision, chart scale and color band on every client. The rules below are what Android and Apple shipped through Meshtastic-Android#6099, #6092 and Meshtastic-Apple#2046, #2040, with the places they disagree settled one way. Where neither shipped what this thread asked for, the rule says so and the gap is tracked per platform.
Context
Meshtastic supports a wide range of sensors, and the clients presented them inconsistently. @oscgonfer's breakdown at the top of this thread is the basis for the rules: categories, a fixed-scale pressure axis, separate temperature and humidity scales, zero-based particulate axes, and CO2 bands.
Air quality display and calculation was settled in #54, raw particulate data in #51 and wind speed units in #87. Units follow design#99.
The categories stay as Device, Environment, Air Quality, Power and Host rather than splitting Environment into Weather and Soil. The firmware packs weather, soil and in-box readings into one EnvironmentMetrics message without saying which sensor took them, so a split would be guesswork until protobufs name the sensor.
#84 asked for SI prefixes on large values. Neither client uses them, and the values Meshtastic reports today (lux, ppm, µg/m³) read fine as whole numbers, so this spec doesn't require them.
An audit of both clients on 2026-11-09 found the gaps listed under Platform Tracking.
Required Client Behavior
-
Group telemetry by message: Device, Environment, Air Quality, Power and Host. Soil temperature, soil moisture, wind, rain and radiation belong to Environment. A client may also show the Soil & Water message as its own group.
-
Pick units from the locale, per design#99: temperature in °C or °F, wind in km/h or mph, rain in mm or inches, weight in kg or lb. Pressure is always hPa. Particulates are µg/m³, CO2 is ppm, radiation is µR/h, voltage is V and current is mA. Convert the chart the same way as the text, so the axis and the reading agree.
-
Use the same precision everywhere a value appears. In logs and chart markers: temperature, wind, rain, radiation and pressure to 1 decimal, voltage to 2, current to 1. On summary tiles and cards: temperature and pressure as whole numbers. Humidity, soil moisture, particulates, CO2, AQI, IAQ and lux are always whole numbers.
-
Give barometric pressure its own axis, a fixed 100 hPa window that defaults to 950–1050 hPa and slides down or up so no reading is cut off. Widen it to the data only when the readings span more than 100 hPa. Never start it at zero.
-
Don't let metrics with different units share one axis in a way that flattens them. Temperature and humidity get separate scales. Humidity runs 0–100 %. Temperature is padded around its data and doesn't start at zero. Lux, radiation and wind don't share the temperature axis.
-
Draw particulate charts on an axis that starts at zero with a small offset, so a zero reading isn't on the bottom edge. Put CO2 on its own axis, or show it in its own chart, so it doesn't flatten the particulate lines. Each series can be shown or hidden.
-
Compute AQI with US EPA NowCast from standard PM2.5, using the 2024 breakpoints and EPA's minimum-data rule. Show the category name with the number: Good, Moderate, Unhealthy for Sensitive Groups, Unhealthy, Very Unhealthy, Hazardous. Show nothing until there's enough history to compute it.
-
Color CO2 by these bands: Good under 1000 ppm, Stuffy under 2000, Poor under 5000, Unsafe under 30000, Evacuate at 30000 and above.
-
Color IAQ by the Bosch scale: Excellent 0–50, Good 51–100, Lightly Polluted 101–150, Moderately Polluted 151–200, Heavily Polluted 201–250, Severely Polluted 251–350, Extremely Polluted above 350.
-
Let the user label each power channel with free text such as Solar, Battery or Load. Labels live on the phone only, per node, and are never written to the radio. A blank label shows as Channel N. Use the label everywhere the channel appears, including node detail.
-
Hide a metric the device doesn't report. A reported zero is a real reading and shows; a missing value never shows as zero. Chart series and legend entries appear only for metrics with data.
Acceptance Criteria
- The same reading shows the same category, unit, precision and color band on Android and Apple, in node details, logs and charts.
- A node at altitude shows its pressure trend without clipping, and a pressure change of a given size draws the same height on both clients.
- A device without a sensor shows no empty tile, zero value or empty chart series for it.
- Each client's tracker lists its gaps against these rules, and is closed with screenshots in light and dark.
Platform Tracking
- Android: [ALIGNMENT]: Sensor telemetry display rules (design#53) Meshtastic-Android#7976, shipped in fix(node): follow the design#53 telemetry display rules Meshtastic-Android#7995; the IAQ band color and label on the tile shipped in fix(node): show the IAQ band color and label on the node detail tile Meshtastic-Android#8071, and reported zero humidity and radiation (requirement 11) in fix(node): plot and show a reported 0 for humidity and radiation Meshtastic-Android#8067
- Apple: [ALIGNMENT]: Sensor telemetry display rules (design#53) Meshtastic-Apple#2958, shipped in Chart each unit on its own axis, add CO2 and eight power channels Meshtastic-Apple#2959
- Web: Build telemetry chart UI for Environment/Power metrics (currently raw JSON only) web#1244, which first has to build telemetry charts
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsIn Progress
Activity
[-][ALIGNMENT]: [ALIGNMENT]: Sensor Telemetry UI/UX[/-][+][ALIGNMENT]: Sensor Telemetry UI/UX[/+]oscgonfer commentedon Mar 14, 2026
This issue requires a lot of unpacking. I would try to categorise the metrics that meshtastic currently collects, which I believe are somewhat reflected on the firmware, with some nuances:
EnvironmentTelemetrymodule.Warning
Note that, with the exception to AQ, all the other ones:
Weather,Device,Soilare now packed intoEnvironmentTelemetry, with the issue being that only one of the metrics is being sent over (for multiple temperature sensors, you only get one temperature). This last issue will be solved by changing how protobufs are described (explicitely mention which sensor collected the metric).Power
This is largely done in
PowerTelemetry, although there is little to show for people that don't know what is connected where. I believe there is a representation gap in how this data makes it to the client and how it's shown at the moment, largely because most current/voltage meters provide several channels, but at the moment there is no way to say "this is the channel that actually means something". I am not sure how the power metrics are used, but it'd make sense to have the metrics coming from the PV panel, and load at least.My suggestion here would be to:
Overview (Battery, Panel power, Load power):
Panel power metrics (power = voltage * current) and load power metrics:

Note
Note: This could be combined with temperature data (if it existed) inside the device.
Weather
Caution
A lot regarding weather was unpacked in meshtastic/Meshtastic-Apple#308
Similar to
PowerTelemetry, forEnvironmentTelemetrytemperature, RH and barometric pressure sensors in this category we don't have a way to know if they are measuring theweather, or the box in which the device is, or something else. For that, I would simply represent those metrics as timeseries.. Note that:Note
One comment for all timeseries: IMHO, timeseries charts with "big dots" are a problem if they become too cluttered. I'd aim to either have thin lines, and maybe a dot where the cursor is (see an example below).
Adding here an example which probably overuses the color scales.
Air quality
AQI
I'll unpack this in #54.
CO2
We now support many CO2 sensors. There is no guidance on how to report it in a general sense. There are some regulations for work environments, but nothing really on households. However, some basic recommendations are:
If we want to add more colors:
Device metrics
Again, the issue here is to be able to know if these metrics are something or not. In any case, the current timeseries do the job.
Soil & water
I don't know if this is really an interesting topic to unpack. For now, simple timeseries can be used as probably this is not really a big use case.
b8b8 commentedon Apr 3, 2026
My comment is on air quality. I think it should be renamed "Hazards".
Hazards should include:
https://climateguard.info/radsens/
UV readings can in a separate section.
oscgonfer commentedon Apr 3, 2026
I think Air Quality is the accepted term for it in most disciplines. Hazards feels too extreme for me, especially since Good Air Quality is no hazard.
[-][ALIGNMENT]: Sensor Telemetry UI/UX[/-][+][PARENT] [ALIGNMENT]: Sensor Telemetry UI/UX[/+]garthvh commentedon Jul 5, 2026
Current state
Spot-checked the current cross-platform rendering of the metric families this issue raises (Power, Weather/Environment, Air Quality, Device thermal), since the discussion above is a design proposal rather than a status report.
iOS (Meshtastic-Apple) — ◐ basic timeseries only, none of the proposed distinctions
Views/Nodes/EnvironmentMetricsLog.swift:35-46) draws temperature, humidity, dew point, barometric pressure, IAQ, and lux all on one shared, autoscaled Y axis (chartYScale(domain: chartRange)), not the separate/fixed scales suggested above (EnvironmentDefaultSeries.swift:116-139— pressure has no fixed 70–120 kPa domain).Views/Nodes/PowerMetricsLog.swift:57-60,119,137,155) only labels sources "Channel 1/2/3" — no way to mark a channel as panel/load/battery, exactly the gap oscgonfer describes.pm25/pm10/co2fields inModel/TelemetryEntity.swift; tracked separately as open Meshtastic-Apple#2040 ("Ingest PM2.5/PM10 telemetry and compute NowCast AQI").radiation,soilMoisture,soilTemperature,windSpeed/Direction—TelemetryEntity.swift:44-61) exist as plain timeseries with no sensor-identity distinction, matching the "which sensor measured this" ambiguity called out above.Android (Meshtastic-Android) — ◐ furthest along, still missing thresholds/labeling
feature/node/.../metrics/EnvironmentMetricsState.kt:57-58,118-119,206-212) already puts barometric pressure on its own left axis vs. a combined right axis for temp/humidity/IAQ — partial alignment with the "separate scales" ask — but the pressure axis is autoscaled from data min/max, not a fixed sea-level range.feature/node/.../metrics/PowerMetrics.kt:82-90,109-144) has the same generic-channel gap as iOS, just with up to 8 channels instead of 3 — still no panel/load/battery semantics.feature/node/.../metrics/AirQualityMetrics.kt:79-96) plots raw PM1.0/PM2.5/PM10/CO2 values with no color bands or AQI category — tracked as open Meshtastic-Android#6092 ("Compute NowCast AQI from PM2.5 history and show an AQI category display"), consistent with the CO2-threshold suggestion above not being applied yet.Web (meshtastic/web) — ❌ no charts for any of these metric families
NodeDetailsDialog.tsx:171-200,447-475only surfaces 4 rawdeviceMetricsfields (airUtilTx, channelUtilization, batteryLevel, voltage) as a plain table. Environment, Power, and Air Quality metrics have no dedicated UI at all — the only place they're visible is aJSON.stringify(node, null, 2)dump inside an "All Raw Metrics" accordion (NodeDetailsDialog.tsx:478-493). TheuseTelemetryhook inpackages/sdk-react/src/hooks/useTelemetry.tsdoesn't appear to be consumed by any app component (no references found outside its own file).Checklist
The three "Create Android/iOS/Web alignment issue" sub-tasks are unchecked and, as far as I can find, none have been opened yet for the general topic — that's accurate, not stale. The AQI-specific offshoot did already happen though: this thread spun into #54, which in turn produced concrete per-platform work (Meshtastic-Apple#2040, Meshtastic-Android#6092). Might be worth using that AQI slice as the template for splitting off Power and Weather/Environment alignment issues too, since those have the same "no shared vocabulary for channels/sensors" problem across all three clients today.
garthvh commentedon Jul 5, 2026
Implementation issues opened for the remaining gaps (Power channel semantics + Environment/pressure axis scaling — AQI is already tracked separately via #54): meshtastic/Meshtastic-Apple#2046 (iOS) · meshtastic/Meshtastic-Android#6099 (Android) · meshtastic/web#1244 (Web, which needs the underlying chart UI built from scratch).
feat(node): label power channels and fix pressure axis scale (#6099)
jamesarich commentedon Jul 6, 2026
Android implementation notes (meshtastic/Meshtastic-Android#6099 → PR #6111)
Documenting the concrete approach Android took for the two non-AQI gaps, so iOS (Meshtastic-Apple#2046) and Web (meshtastic/web#1244) can align on vocabulary and behavior rather than each inventing its own.
1. Power channel identity → per-channel user label
PowerMetricsmessage has no label field). Persisted in the app's node DB and preserved across device syncs (an incoming telemetry/NodeInfo packet, which never carries labels, must not wipe a user's labels).2. Barometric pressure axis → fixed-width window that slides to elevation
Android already had pressure on its own axis (separate from the temp/humidity/IAQ axis). The remaining issue was that the pressure axis autoscaled from data min/max, so a few-hPa weather swing looked huge or invisible depending on the sampled range — not comparable across sessions/nodes.
Rather than a hard clamp (e.g. a static 950–1050 hPa), Android uses a fixed-width window (100 hPa) that slides to the node's elevation:
The key invariant is fixed width → consistent scale: a given pressure change always renders the same height, which is what this issue asked for, while never clipping high-altitude station-pressure readings. The trade-off is that absolute position isn't identical across nodes at different elevations (1013 isn't always at the same pixel) — but scale comparability, the meaningful one for spotting trends, is preserved.
Note: Meshtastic's
barometric_pressureis raw station pressure (not sea-level-corrected), which is exactly why a static sea-level clamp would hide altitude readings and the sliding window is needed.Happy to adjust naming/shape if iOS/Web want to converge on something different before this becomes the de-facto reference.
feat(node): label power channels + fixed-scale pressure axis (meshtas…
oscgonfer commentedon Jul 30, 2026
Small feedback.
Weather metrics
AQ Telemetry
garthvh commentedon Aug 11, 2026
Status update (August 2026): the iOS and Web alignment sub-issues still haven't been opened (Android's exists). The chart-scale feedback above (separate scales for temperature/RH, zero-based PM axes with offset, an AQ grid mirroring environment telemetry) is exactly the kind of decision the eventual spec should ratify — suggest capturing those as the first concrete standards in this parent, then opening the per-client issues against them.
Chart each unit on its own axis, add CO2 and eight power channels (#2959