How device, power, weather and air-quality measurements travel through a Meshtastic network.
The Telemetry module can report the health of the radio itself and measurements from attached sensors. On infrastructure, its greatest value is often unglamorous: battery level, voltage, channel utilization and airtime can reveal a weak power system or an overloaded site before the node disappears. Environmental sensing is a second use case, not a requirement for every relay.
Four telemetry families
| Family | Examples | Typical use |
|---|---|---|
| Device | Battery level, voltage, channel utilization, airtime | Node health and congestion |
| Environment | Temperature, humidity, pressure, light, wind, rain | Weather and enclosure monitoring |
| Air quality | Particulates and CO₂ on supported sensors | Local environmental observations |
| Power and health | Current, power, heart rate, SpO₂, body temperature | Specialized projects; health support may require a custom build |
The current Telemetry documentation lists supported I²C devices including BME280/BME68x environmental sensors, SHT temperature and humidity sensors, INA219/226/260 power monitors, light and UV sensors, particulate sensors, wind and rain hardware and selected health sensors. Supported I²C sensors are detected at startup, but the relevant telemetry type must still be enabled before readings are sent.
Design the measurement before wiring the sensor
Define what decision the value will support. Outdoor temperature measured inside a sun-heated enclosure is not weather-station temperature. Humidity inside the box may be excellent for detecting condensation risk, but it should be labeled as enclosure humidity. Battery voltage alone may not show solar charge current or load; an INA-family monitor can provide a more useful power picture when installed correctly.
Record sensor model, address, placement, enclosure ventilation, calibration notes and units. A precise-looking number without installation context can be misleading. If MeshAtlas displays public sensor data, the listing should distinguish operational telemetry from calibrated environmental observations.
Choose conservative intervals
The documented default for device, environment, air-quality and health update intervals is generally 1,800 seconds when the configured value is zero. A connected client may receive local device metrics more frequently, but that does not mean the node must broadcast them over LoRa every minute. For a solar relay, thirty to sixty minutes is often enough to observe trends. Slowly changing pressure or enclosure humidity can use similarly long intervals.
Calculate total traffic across all telemetry categories and all relays. Ten nodes sending four independent reports every five minutes do not create “ten small packets”; they create repeated transmissions that may be rebroadcast across the mesh. During diagnosis, temporarily shorten an interval only on the node being tested, then restore it.
Public, private or internet-backed collection
Public device health can help community operators, but exact power behavior may reveal when a remote site is unattended or failing. Environmental data may be harmless in one setting and sensitive in another. Put operational measurements on a controlled channel when necessary. If a gateway and broker already exist, MQTT can collect higher-resolution readings without forcing every sample through the radio mesh, but the local RF link remains the limiting segment for remote sensors.
Installation checklist
- Verify the sensor and its voltage level are supported by the board and firmware.
- Connect power off; confirm pinout, I²C address and pull-ups.
- Boot locally and verify detection before installing the node remotely.
- Compare readings with a trusted reference and label the measurement location.
- Enable only the required telemetry family and set a restrained interval.
- Observe channel utilization before and after deployment.
- Document sensor replacement and recalibration procedures.
What telemetry cannot prove
A recently received battery packet proves that one packet reached one observer. It does not prove continuous availability, bidirectional reachability or full coverage. Missing telemetry may mean a failed node, but it may also mean changed routing, an offline observer, a configuration change or packet loss. Combine telemetry with direct tests, independent observers and maintainer knowledge.
Telemetry is most valuable when treated as a trend rather than an isolated number. Store timestamps, preserve gaps, avoid inventing values between reports and define alert thresholds based on the specific battery chemistry and installation. For broader operational interpretation, see Detecting failed or degraded nodes.