MeshMonitor

Appearance

GitHub Stars

Analysis & Reports ​

The Analysis & Reports workspace is a global, cross-source analytics page that runs analytical reports against the telemetry, position, and routing data MeshMonitor has collected from every source you can read. It lives at /reports and is linked from the bottom of the dashboard sidebar (right under Map Analysis).

The first report bundled with the workspace is Solar Monitoring Analysis — see below. The card-grid landing page is designed to host additional reports over time without changing the routing or navigation surface.

Solar Monitoring Analysis ​

Identifies solar-powered nodes by analyzing battery and voltage telemetry over a configurable lookback window and looking for the characteristic morning-low → afternoon-peak charging curve, followed by overnight discharge. Ports the proven detection algorithm from MeshManager.

What gets analyzed ​

For every node in your permitted sources, the report scans the following telemetry types over the lookback window:

  • batteryLevel (preferred when ≥ 3 readings/day are present)
  • voltage
  • ch1Voltage, ch2Voltage, ch3Voltage (INA voltage channels)

A daily pattern is recorded when the metric shows:

  • A morning low (06:00–10:00 UTC) and an afternoon peak (12:00–18:00 UTC)
  • Sufficient daily variance (≥ 10% for battery, ≥ 0.3 V for voltage) or a "high-efficiency" candidate that stays above 90% / 4.1 V with smaller swings
  • A peak hour between 10:00 and 18:00 UTC and a sunrise hour ≤ 12:00 UTC

A node becomes a solar candidate when at least 50% of its analyzed days show a pattern (33% for high-efficiency candidates that consistently stay above 98%).

Running the report ​

  1. Open the dashboard, click Analysis & Reports in the sidebar.
  2. Click the Solar Monitoring Analysis card.
  3. Set the Lookback (days) between 1 and 90 (default 7) and click Run analysis.
  4. (Optional) Click Run forecast to project battery state across the next several days using the forecast.solar production estimates.

The summary row shows the lookback window, total nodes analyzed, solar nodes detected, average charging hours per day, and average overnight discharge hours per day.

Per-node card ​

Each detected node renders an expandable card with:

  • Solar score (% of analyzed days that showed a clear pattern)
  • Average charge / discharge rates (per hour)
  • Detected metrics (battery, voltage, INA channel names)
  • Insufficient solar warning when projected daily charging cannot keep up with overnight discharge
  • A Recharts time-series chart showing:
    • Battery / voltage line
    • Solar production area overlay (Wh, right axis) when forecast.solar data is available
    • Reference levels: green at 100% / 4.2 V (full), yellow at 50% / 3.7 V (nominal), red at 20% / 3.3 V (low)
    • Forecast simulation as a mauve dashed extension when Run forecast has been triggered
  • A Recent daily patterns table (date, sunrise / peak / sunset times and values, rise, fall, charge rate /h, discharge rate /h)

Forecast simulation ​

The forecast endpoint compares projected daily Wh totals from forecast.solar to the lookback's historical average. Each day is flagged Low if it falls below 75% of the historical average. For every solar candidate, the report simulates the next ~5 days of battery state by running the node's measured charge and discharge rates against the forecast factor for each day:

  • Sunrise point: battery after the overnight discharge
  • Peak point: battery after the daylight charge (modulated by forecast_factor = forecast_wh / avg_historical_wh, clamped 0–1.5)
  • Sunset point: battery after a small afternoon drain

Nodes whose simulated minimum drops below 50% (battery) or 3.5 V (voltage) are listed as Nodes predicted at risk so operators can intervene before they go offline.

Solar production must already be configured under Settings → Solar Monitoring for the forecast to produce useful output. See the Solar Monitoring guide for set-up details.

Permissions ​

Both endpoints behind the workspace are scoped to the requesting user's permitted source IDs:

  • Admins see all enabled sources
  • Non-admin users see sources where they hold nodes:read
  • An optional ?sources=id1,id2 query param restricts the analysis further (intersected with permitted IDs)

The page itself is publicly routable; only the data is gated.

API ​

The Reports workspace surfaces two endpoints under the existing /api/analysis/* namespace:

  • GET /api/analysis/solar-nodes?lookback_days=N&sources=…
  • GET /api/analysis/solar-forecast?lookback_days=N&sources=…

See the REST API reference for the full request/response shapes.

  • Solar Monitoring — configuration of the forecast.solar integration that powers the production curve and forecast factor
  • Map Analysis — cross-source map / coverage workspace at /analysis
  • Analytics — analytics dashboards in the per-source view