Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Build telemetry chart UI for Environment/Power metrics (currently raw JSON only)

Aperta
  • Qualcosa non va?
#1,244 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Hunter275 ci sta già lavorando.

Dal 24/7/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

feature request help wanted parity

Background

Per meshtastic/design#53, sensor/telemetry display should be aligned across clients. Web is furthest behind of the three — it has no dedicated UI for Environment or Power metrics at all, only a raw dump.

Current state

NodeDetailsDialog.tsx:171-200,447-475 only surfaces 4 raw deviceMetrics fields (airUtilTx, channelUtilization, batteryLevel, voltage) as a plain table. Environment and Power telemetry have no dedicated UI at all — the only place any of it is visible is a JSON.stringify(node, null, 2) dump inside an "All Raw Metrics" accordion (NodeDetailsDialog.tsx:478-493). The useTelemetry hook (packages/sdk-react/src/hooks/useTelemetry.ts) exists but isn't consumed by any app component — it appears to be dead/unused code.

(Air Quality is being handled separately per design#54 — this issue is Environment + Power only.)

What to build

Bring Web up to feature parity with iOS/Android's charting, using their approach as reference:

  1. Environment metrics chart: temperature, humidity, dew point, barometric pressure, IAQ, lux as timeseries. Give barometric pressure its own axis with a fixed sea-level-relative domain (e.g. ~950–1050 hPa) rather than sharing an autoscaled axis with the other metrics — a small real pressure change looks huge or invisible otherwise depending on sample range. (iOS: Views/Nodes/EnvironmentMetricsLog.swift; Android already separates pressure onto its own axis: feature/node/.../metrics/EnvironmentMetricsState.kt:57-58,118-119,206-212, though even Android's isn't on a fixed domain yet.)
  2. Power metrics chart: per-channel voltage/current timeseries. Both iOS and Android currently only label channels generically ("Channel 1/2/3") with no way to identify a channel's role (solar panel / battery / load) — worth starting Web with at least a user-editable per-channel label from day one rather than inheriting that same gap.
  3. Wire up (or replace) useTelemetry so this data actually reaches a UI component — right now it's unused.

Reference

Cross-platform alignment tracking issue: meshtastic/design#53.

Lingua principale
TypeScript
Stelle
861
Fork
316
Merge medio
18m
PR unite (30g)
1

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di meshtastic/web

Tutte le issue di meshtastic/web

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.