Meshtastic part 3: turn a mesh node into a sensor station
Beginner to intermediate · Learn by measuring something real
Meshtastic is useful for more than short text messages. With the appropriate hardware, it can broadcast device health and environmental sensor readings over LoRa, without relying on the Internet for the local radio exchange.
For people who like building weather stations, monitoring remote equipment, recording temperatures or learning how sensors work, this is an especially practical project.
What does “telemetry” actually mean?
simply means measurements reported from one device or location to another.
Meshtastic has a built-in telemetry module with several categories:
| Kind of measurement | Examples | Where it comes from |
|---|---|---|
| Device metrics | Battery level, voltage, channel use, radio airtime | Supported measurements from the node itself |
| Environment metrics | Temperature, humidity, barometric pressure, light or other supported readings | Attached or built-in compatible sensors |
| Air-quality metrics | Particulate concentration or supported gas-related measurements | Appropriate supported air-quality sensors |
| Other specialized metrics | Selected health/monitoring measurements | Device, sensor and firmware support vary; some require custom firmware builds |
The official Meshtastic telemetry documentation lists current supported sensors and options. A device showing battery voltage does not prove it has a temperature, humidity or pressure sensor.
A very approachable example: BME280
A BME280 is a compact environmental sensor that can provide:
- Temperature — ambient temperature near the actual sensing element.
- Relative humidity — moisture in the surrounding air expressed as a percentage of saturation at that temperature.
- Barometric pressure — atmospheric pressure at the sensor.
Many BME280 breakout boards communicate using —a common short-distance connection between a microcontroller and sensors.
A BME280 does not measure wind speed, rainfall, GPS position or air pollution. A BME680/BME68x family sensor supports a gas-resistance measurement as well, but interpreting air quality requires care; a gas reading alone is not automatically an accurate pollutant concentration.
What parts of the project do different jobs?
The sensor measures physical conditions. The microcontroller and firmware read it. The LoRa transceiver and antenna send selected measurements over RF. Other Meshtastic nodes can receive or relay the telemetry if settings and radio links permit. An optional MQTT gateway can forward copies to an Internet-connected dashboard.
This separation is important: local sensor-to-radio telemetry doesn't need MQTT, and a broker dashboard cannot substitute for a working radio path.
How I²C connects a sensor
Typical I²C sensor wiring uses:
| Connection | Purpose |
|---|---|
| VCC / VIN | Power supply to the sensor breakout, at a voltage compatible with the board |
| GND | Electrical ground reference |
| SDA | Serial data signal |
| SCL | Serial clock signal |
Do not assume all radio boards use the same GPIO pins or voltage. A board might provide 3.3 V logic, while a particular breakout might have its own regulator or level shifting. Check the exact hardware's pinout and supply limits. Some development boards use different I²C buses or require firmware pin assignments, and nearby sensors can share addresses—check for conflicts.
I²C is intended for short, well-designed electrical connections. Long cables or outdoor wiring can introduce signal and lightning protection problems. For a sensor mounted far from the node, use a communication interface designed for that distance or locate the radio closer to the sensor.
A starter sensor experiment
Goal: read an environmental measurement on your own node, then let a second Meshtastic radio receive it.
- Identify your exact Meshtastic radio hardware and its supported sensor pins. Confirm that the firmware supports the proposed sensor.
- With power off, connect a supported BME280 or another documented compatible sensor using the correct power and I²C connections.
- Power the device and check whether the firmware detects the sensor. The official sensor list includes I²C addresses and supported readings.
- Open your node's Telemetry / Sensors module settings and enable the applicable environmental measurement feature. UI wording varies with app and firmware.
- Check that a reasonable reading appears locally. Compare it with another thermometer or pressure source, noting that perfect agreement isn't expected.
- Set a conservative transmission interval. Make sure the device has sufficient battery or power budget.
- On a second compatible node, observe whether a telemetry packet or reading arrives over LoRa, with MQTT off for this first test.
- Record the time, sensor type, RF conditions and any missed reports.
If you cannot see readings locally, focus on power, I²C pins, sensor address, firmware support and actual detection before blaming mesh propagation.
Local reading, RF transmission, and Internet dashboard are three different steps
| Step | Requires Internet? | What it proves |
|---|---|---|
| Node reads BME280 locally | No | Sensor/firmware path is working |
| Second node receives environmental telemetry by LoRa | No | Radio telemetry delivery works over that path |
| Home Assistant / MQTT dashboard updates | Maybe | The gateway, MQTT and dashboard integration are functioning |
| Public map displays a telemetry-enabled node | Usually Internet for that map | Reporting service received data, not necessarily that your distant radio did |
Meshtastic has MQTT integrations that can be used with Home Assistant, Node-RED and other systems. These require their own setup, permissions and connectivity; a particular dashboard may support only some packet types.
How frequently should telemetry be transmitted?
Imagine a hundred nodes each transmitting a measurement every few seconds. Even if the measurements are small, all those packets compete for shared airtime, increase collision risk and may consume battery power.
The current telemetry module includes update interval settings, and the mesh firmware may adjust broadcast behavior as a network gets busy. The official documentation currently describes a 30-minute default setting for environmental update intervals, but defaults can change by firmware and role.
Ask these questions before selecting an interval:
- How fast does the underlying measurement really change? Atmospheric pressure and outdoor temperature typically don't need multiple reports per second.
- What problem are you trying to solve? A battery health trend needs different reporting from a rapid event detector.
- How much battery life do you need? GPS, sensors, displays, power-saving behavior and radio transmissions all affect consumption.
- Is the mesh congested? More RF updates may make messaging worse for others.
- Is the node's role appropriate? A dedicated sensor node behaves differently from a normal message client.
One useful principle: don't transmit a new radio packet every time a sensor could technically be read. Measure locally as needed, and send only as often as the application requires.
Should I set my node to SENSOR?
Meshtastic has a SENSOR role intended for telemetry-focused deployments. It affects broadcast priorities and, depending on settings and platform, power-saving/sleep behavior.
But SENSOR is not universally the right role just because an ordinary Meshtastic client has a BME280 attached. If you still want a phone-connected station that exchanges messages, start by understanding the normal CLIENT role and the device role documentation.
Dedicated solar or battery sensor deployments should be designed around power and wakeup requirements, not merely a role name.
Good measurements depend on mounting
A BME280 inside a hot enclosure may measure the enclosure, not outdoor air temperature. Direct sunlight, heat from the processor, wet electronics, poor airflow and pressure enclosure design can distort readings.
For an outdoor station:
- Use an appropriate ventilated radiation shield for temperature/humidity sensing.
- Keep the sensor away from processor heat, power supplies and direct sunlight.
- Consider condensation, weatherproofing, insects and sensor access for maintenance.
- Verify that pressure readings are interpreted appropriately for altitude and local conditions.
- Keep antenna placement and safe lightning/grounding practices separate from the sensor calibration problem.
A pressure reading at a mountain site isn't automatically directly comparable to a station's sea-level-adjusted weather report.
Troubleshooting telemetry
| Symptom | Investigate |
|---|---|
| “No sensor detected” | Power/voltage, SDA/SCL, wrong address, incorrect breakout wiring, unsupported firmware |
| Temperature too high | Sensor too close to the radio's processor or inside a warm enclosure |
| Local readings work, but remote node sees nothing | RF settings, channel, reception, airtime, telemetry enabled, role and transmit intervals |
| MQTT dashboard updates, but local radio test fails | MQTT may be carrying the reporting path; inspect actual local RF reception |
| Air-quality display looks implausible | Sensor type, calibration/warmup, housing and interpretation of raw measurements |
| Battery drains faster after adding a sensor | Sensor power draw, broadcast frequency, always-on interfaces and sleep behavior |
Beyond the BME280
The official sensor list includes more than temperature/humidity/pressure chips. Depending on firmware and hardware, supported classes include light, UV, particulate matter, CO₂, voltage/current, rain and other specialized measurements.
Those are opportunities for weather monitoring, experimentation and equipment maintenance. Do not assume a listed sensor measures everything, and verify supported outputs and installation requirements before buying parts.
If your actual goal is just weather data, a simple node with a suitable sensor and reliable antenna may be more useful than a large, expensive repeater project.
Primary sources and next steps
- Official Meshtastic Telemetry Module and supported sensors
- Official Meshtastic device roles, including SENSOR
- Meshtastic mesh broadcast behavior
- Meshtastic MQTT integrations
Next: GPS, location and privacy or MQTT and off-grid reliability.