Background
Per meshtastic/design#53, sensor/telemetry display should be aligned across clients. The AQI slice of this already spun off into its own tracked work (design#54 → Meshtastic-Apple#2040) — this issue covers the other two gaps found on iOS: Power channel semantics, and Environment chart axis scaling.
1. Power channels have no identity/role
Views/Nodes/PowerMetricsLog.swift:57-60,119,137,155 only labels channels generically ("Channel 1/2/3") — there's no way to mark a channel as e.g. solar panel, battery, or load, so a user can't tell which line is which without knowing their own wiring by heart. Add a way to assign a role/label per power channel (even a simple user-editable text label per channel would resolve the core ambiguity, before any fancier per-role icon/color treatment).
2. Environment charts share one autoscaled Y axis
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)). Wildly different-range metrics squashed onto one shared autoscaled axis make small real changes in one metric invisible next to a large-range metric. At minimum, barometric pressure should get a fixed axis domain (e.g. ~950–1050 hPa sea-level range, per EnvironmentDefaultSeries.swift:116-139 which currently has no fixed domain) rather than autoscaling with the rest.
Soil/device-thermal fields (radiation, soilMoisture, soilTemperature, windSpeed/windDirection — Model/TelemetryEntity.swift:44-61) also render as plain timeseries with no sensor-identity distinction (e.g. multiple soil probes on one node would be indistinguishable) — worth the same treatment if/when multi-sensor nodes are common enough to matter.
Reference
Cross-platform alignment tracking issue: meshtastic/design#53.
Background
Per meshtastic/design#53, sensor/telemetry display should be aligned across clients. The AQI slice of this already spun off into its own tracked work (design#54 → Meshtastic-Apple#2040) — this issue covers the other two gaps found on iOS: Power channel semantics, and Environment chart axis scaling.
1. Power channels have no identity/role
Views/Nodes/PowerMetricsLog.swift:57-60,119,137,155only labels channels generically ("Channel 1/2/3") — there's no way to mark a channel as e.g. solar panel, battery, or load, so a user can't tell which line is which without knowing their own wiring by heart. Add a way to assign a role/label per power channel (even a simple user-editable text label per channel would resolve the core ambiguity, before any fancier per-role icon/color treatment).2. Environment charts share one autoscaled Y axis
Views/Nodes/EnvironmentMetricsLog.swift:35-46draws temperature, humidity, dew point, barometric pressure, IAQ, and lux all on one shared, autoscaled Y axis (chartYScale(domain: chartRange)). Wildly different-range metrics squashed onto one shared autoscaled axis make small real changes in one metric invisible next to a large-range metric. At minimum, barometric pressure should get a fixed axis domain (e.g. ~950–1050 hPa sea-level range, perEnvironmentDefaultSeries.swift:116-139which currently has no fixed domain) rather than autoscaling with the rest.Soil/device-thermal fields (
radiation,soilMoisture,soilTemperature,windSpeed/windDirection—Model/TelemetryEntity.swift:44-61) also render as plain timeseries with no sensor-identity distinction (e.g. multiple soil probes on one node would be indistinguishable) — worth the same treatment if/when multi-sensor nodes are common enough to matter.Reference
Cross-platform alignment tracking issue: meshtastic/design#53.