Author SHA1 Message Date
Pablo Revilla fbbc5a73d6 Revert "feat(node): add power metrics chart (#190)"
This reverts commit a298347f14.
2026-11-09 13:57:08 -08:00
Óscar García Amor a298347f14 feat(node): add power metrics chart (#190)
* fix(node): read telemetry fields from their block

The telemetry charts matched fields with unanchored regexes over the
whole payload, so "voltage:" also matched "ch1_voltage:" (power_metrics)
and environment_metrics voltage, plotting them as the device voltage.
The same applied to "temperature:" and other shared field names.

Parse each value only inside its own metrics block (device_metrics or
environment_metrics), match the exact field name and accept negative
values (e.g. temperatures below zero).

* feat(node): add power metrics chart

Plot power_metrics telemetry (ch1..ch8 voltage and current) on the node
page. Each channel that reported data gets a voltage series on the left
axis (V) and a dashed current series on the right axis (mA).

The legacy voltage/current fields of environment_metrics, reported by INA
sensors and to be deprecated in favor of PowerMetrics, are shown in the
same chart as "Environment" series.

The chart is hidden when the node sends no power data and supports the
usual expand and CSV export actions. Translations added for en, es, ru.
2026-11-09 13:54:22 -08:00
2 changed files with 0 additions and 1 deletions

No files matched your search

-1
View File
@@ -14,7 +14,6 @@ The project serves as a real-time monitoring and diagnostic tool for the Meshtas
- Browser assets: serve pinned JavaScript and CSS libraries locally, including Leaflet, ECharts, Bootstrap, and QRCode.js, instead of loading them from CDNs. Map tiles still require access to their providers.
- Reliability and privacy: improved handling of malformed packets, unknown protobuf enums, invalid numeric API parameters, and secondary MQTT decryption keys; bounded traceroute rendering; escaped chart and telemetry content; and hardened CSV exports.
- Meshtastic and API: refreshed the protobuf definitions, included available public keys in shared-contact QR codes, and updated the API documentation and generated browser reference.
- Contributors: thanks to Nathan ([nullrouten0](https://github.com/nullrouten0)) for packet handling, security, CSV export, API validation, logging, and traceroute improvements ([#176](https://github.com/pablorevilla-meshtastic/meshview/pull/176)–[#182](https://github.com/pablorevilla-meshtastic/meshview/pull/182)), and Mike Benner for shared-contact public-key support ([#185](https://github.com/pablorevilla-meshtastic/meshview/pull/185)) and the Leaflet heatmap compatibility fix ([#188](https://github.com/pablorevilla-meshtastic/meshview/pull/188)).
**Upgrading:** Back up your database, update the application and dependencies, then restart both the database writer and web server (or use `mvrun.py`). The writer applies the new altitude-column and packet-index migrations automatically. Reload browser pages to load the updated assets. See [the migration guide](docs/Database-Changes-With-Alembic.md) and [Docker instructions](README-Docker.md) for your installation.
Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.8 MiB

After

Width:  |  Height:  |  Size: 804 KiB