Skip to content

Dashboard Guide

Once the monitor is connected to the receiver and sensor nodes are active, the dashboard populates automatically. This page walks through each section of the dashboard from top to bottom.

Full Monitoring Dashboard

The colored bar at the top of the dashboard summarizes the overall network health at a glance.

ColorMeaning
GreenEverything is nominal. All nodes are online and readings are within normal ranges.
AmberSomething needs attention. A node may be stale (not heard recently) or signal quality is weak.
RedA critical condition has been detected. A node is offline, a sensor is overheating, or another threshold has been exceeded.

The banner text describes the specific condition that triggered the warning or error.

A visual strip showing the five conceptual stages your data passes through:

  1. Capture — Sensor reads a physical measurement.
  2. Represent — The reading is encoded into a protobuf message.
  3. Transmit — The message is sent over LoRa radio.
  4. Transform — The monitor processes and analyzes the data.
  5. Present — Results are displayed on the dashboard.

Stages illuminate as data moves through the system, providing a real-time visual of the data pipeline. This maps directly to the Information Internetworks thread concepts.

Pipeline

Four summary metrics are displayed in card format:

CardDescription
Total ReportsThe total number of sensor reports received since the app started (or since connecting).
Nodes OnlineHow many distinct sensor nodes have sent data recently.
Average RSSIThe average signal strength across all recent packets (in dBm).
Network HealthA composite health score computed from node connectivity, signal quality, and sensor readings.

Two line charts display sensor data over time:

  • Temperature Chart — One colored line per temperature node, plotting readings over time.
  • Pressure Chart — One colored line per pressure node, plotting readings over time.

Each node’s line is labeled with the node ID. If enough data points exist, a trend badge appears next to each node name indicating the current trend direction:

BadgeMeaning
Up arrowRising trend
Down arrowFalling trend
Right arrowStable (no significant change)

Trend detection requires at least 3 data points before it activates (configurable via MIN_POINTS_FOR_TREND in the Analytics Thresholds).

Sensor Charts

This section shows what the data means beyond raw numbers. For each node and sensor type, you can see:

  • Current reading — The latest value from this sensor.
  • Trend direction — Rising, falling, or stable.
  • Rate of change — How fast the value is changing (e.g., +1.2 degrees C/min).
  • Anomaly flags — Alerts for conditions like overheating (temperature above threshold) or rapid pressure drops.

Anomaly thresholds are configurable. See Analytics Thresholds for the full list.

Derived Insights

One card is displayed per active node, showing detailed connectivity information:

FieldDescription
Signal QualityDescriptive label (Excellent, Good, Fair, Weak, Offline)
RSSIMost recent signal strength in dBm
SNRMost recent signal-to-noise ratio in dB
Hop CountHow many relay hops the last packet from this node took
UptimeHow long the node has been running since its last boot
Last SeenHow recently the last packet was received from this node

A table showing the last 20 received packets in a format inspired by network protocol analyzers. Each row shows:

ColumnDescription
Message IDThe unique packet identifier in hexadecimal
Source NodeThe originating node’s ID
Sensor TypeTemperature or pressure
HopsNumber of mesh relay hops
RSSISignal strength of the received packet
SNRSignal-to-noise ratio
ValueThe sensor reading with its unit

This view is useful for debugging mesh behavior — you can see which packets were relayed and how signal quality varies per packet.

Packet Inspector

A scrollable table showing the last 30 raw reports stored in the database. Each row displays the unprocessed field values exactly as they were stored. This is useful for verifying that data is being parsed and stored correctly.

The bottom of the dashboard shows the raw serial output from the receiver node, line by line. This is the unprocessed text received from the USB serial port.

Lines that contain valid [REPORT] data are highlighted in green. All other log lines (startup messages, radio status, etc.) are displayed in the default color.

The log console is useful for debugging — if the receiver is printing data but the dashboard is not updating, you can check here to see whether the lines are being parsed correctly.

Console

To learn how to modify the monitor application’s code, see Extending the App.