Field Sensor Deployment Guide
Site Selection
Place sensors where you need data - not where it is convenient to access. Ideal sites are often inconvenient: a peak for a weather station, a stream bank for water level, a crop row for soil temperature. Choose the site first, then engineer the power and connectivity to support it.
Weatherproofing Sensors
Temperature and humidity sensors require a radiation shield
(white louvered housing) for accurate readings. DirectIn direct sunlight on a bare
sensorsensor's willerror readcan exceed 10 -°C, 20sometimes °Cmuch high.more, depending on wind and
the sensor (see weather-station siting references). Heat trapped inside a
sealed enclosure will do the same. Rules:
- Never seal a BME280 or BME680 inside a closed waterproof enclosure - humidity will read 100 % and temperature will reflect enclosure heat, not ambient air.
- Mount the sensor in a
Stevenson screenor alouvered radiation shield. A hobby plastic louvered shield(widelyrunsavailable from weather station suppliers for underroughly $15).10-25 (price varies; check a current product listing), while a full traditional Stevenson screen is considerably more expensive. - If you cannot use a radiation shield, at minimum shade the sensor from direct sun and allow free airflow.
Enclosure Strategy
Keep electronics and sensors in separate compartments:
- Main board, battery, and solar charge controller in an IP67 sealed enclosure (ABS or polycarbonate, UV-rated).
- Run sensor wiring through a cable gland or a small hole sealed with self-amalgamating tape.
- BME280 / BME680: mount in the radiation shield outside the enclosure
and run I2C wiring inside.
LimitKeep I2C cablelengthrunstoshort - under ~50cm;cm is a useful rule of thumb, ultimately governed by the 400 pF total bus-capacitance limit in the I2C specification (NXP UM10204). For longer runs useaanlevel-shiftedactive I2Cbufferbusforextender/repeaterlongerratherruns.than a simple buffer. - For insect protection, cover any ventilation holes with fine stainless mesh - spiders love warm enclosures.
Power Sizing
Sensor node consumption is extremely low with the right hardware and firmware:firmware. The
figures below are an idealized best case (they exclude regulator quiescent
draw and wake/active current); real nodes often run somewhat higher:
| Component | Average current (10-min TX interval) |
|---|---|
| nRF52840 MCU (sleep) | ~2 µA |
| BME280 ( | ~0.1 µA sleep; ~3.6 µA active at 1 Hz |
| LoRa TX burst (10 s/day total) | ~0.1 mA averaged (TX current × airtime ÷ 86400 s; e.g. ~118 mA at +22 dBm × ~10 s/day ÷ 86400 s ≈ 0.014 mA — adjust for your actual TX power and airtime) |
| Total daily | < 5 mAh/day (idealized best case; excludes regulator quiescent and wake/active current) |
- Battery-only: 3 000 mAh LiPo → ~600
days.days as a theoretical maximum. Derate for LiPo self-discharge and regulator quiescent draw - real runtime will be shorter. - Solar-maintained: a 1 W (6 V) panel
incanany climate with 4+ hours of peak sun keepskeep a 3 000 mAh packfulltoppedindefinitely.up at sites that reliably get ~4+ peak-sun-hours, but this does not hold in every climate - high-latitude winters and shaded/canopy sites can fall short for extended periods. Size conservatively for worst-case winter insolation rather than assuming indefinite operation. Also ensure the battery is not charged below 0 °C: use a charge controller with a low-temperature charge cutoff (charging any lithium cell, including LiFePO4, below freezing causes plating and permanent damage). - For critical sensors in low-light environments (north-facing, dense canopy), upsize to 2 - 3 W and add a 5 000 - 6 000 mAh pack. Tie panel/battery sizing to your actual load budget and local peak-sun-hours (e.g. via PVWatts/ NREL insolation data) rather than fixed numbers.
Connectivity Range
Sensor nodes use the same LoRa mesh relay infrastructure as every other node.
A sensor 20 km from the nearest internet gateway can still deliver data inwith low
latency when the relay path is healthy, but mesh delivery is best-effort:
expect dropped readings and gaps whenever any hop fails (see Data Gaps below).
Do not rely on near-real-time ifdelivery thefor meshtime-critical hasor relaysafety-of-life
coverage along the path.monitoring. When planning a sensor deployment, map out the relay chain first:
- Identify the target sensor location.
- Verify line-of-sight or near-LOS to at least one repeater.
- Trace that repeater's path to a node with internet/MQTT uplink.
- Add intermediate repeaters if any hop is marginal.
Data Gaps and Local Storage
If the mesh path to a gateway is down, sensor readings are lost - sensor nodes have no local storage. Mitigation options:
- Store-and-Forward (Meshtastic):
nearbythenodesStore & Forward module requires a dedicated ESP32 node with PSRAM acting as a S&Fenabledserver on a private channel, and it primarily re-serves text-message history on request. It is not a transparent telemetry bufferpacketsthatandautomaticallydeliverbackfillsthemsensorwhendatatheacross gatewayreturns.outages.SuitableForforsensor-datashortgapoutagesrecovery, prefer local SD logging (hours)below). - MeshCore room servers:
cana Room Server is a store-and-forward BBS that holds room chat history for clients on request - it is not a sensor-telemetry buffermessagesthatwhenflushes accumulated readings across a gatewayisoutage.temporarilySeeoffline,MeshCorethendocs;flushdowhennotreconnected.rely on it to recover lost telemetry. - Local SD card logging: for critical sensors add an SD card module and log locally in CSV format. This is the recommended way to recover from gateway outages. A recovery script can push historical data to InfluxDB when connectivity is restored.
Maintenance Planning
Remote sensor nodes require infrequent but non-zero maintenance:
- BME280 radiation shield accumulates dust, pollen, and spider webs over time - clean annually or after wildfire smoke events.