Selecting Wireless Environmental Monitoring Hardware: Parameters, Backhaul, Power and Protection

Rework on environmental monitoring projects usually happens after the hardware is on site: the probe measures, but the data never reaches the platform; or the device is installed, but its power supply cannot sustain it. The usual cause is three conditions that were not confirmed together at selection time — which parameters to measure, how the data travels back, and whether the site has power. A correct probe paired with the wrong backhaul or power option means the whole sensing point has to be reconfigured.

This article sets out a four-step selection method, with range, interface, power and protection specifications for weather stations, air and soil sensors, water-quality probes, data loggers and gateways. All figures are nominal datasheet values, not field measurements — the measurement basis is at the end.

Quick answer

A summary of what the rest of the article derives, organised by site condition.

Reference prices are per-unit prices at the time of lookup and exclude the gateway (M2 indoor gateway ~$99) and probes; the product page is authoritative when ordering.

Three conditions change the table above:

• The probe needs 12 V — dissolved oxygen, turbidity and liquid level probes have a nominal input of 12 V or higher, and the S2100 battery supplies only 3 V / 5 V to a probe, so it cannot drive them. These points need an external 12 V source and cannot be planned as battery-only points
• Data must stay on site — the LoRaWAN path can run its network server locally (ChirpStack built into the M2 gateway, or a self-hosted The Things Stack); the 4G path depends on the cloud, so choose LoRaWAN
• Frequency band — LoRaWAN nodes and gateways must be ordered for the same regional band (EU868, US915, AS923 and so on); the band cannot be changed by configuration after ordering

The page configurator builds a device list from three questions: scenario, communication and power. If you already know the monitoring target, the backhaul and the power conditions, use the configurator below; to see the reasoning behind each choice first, read the four steps.

---

Why wireless low-power sensing

Battery-powered LoRaWAN sensors are not tied to cable runs or power outlets

The four steps below assume the sensors report wirelessly. Compared with running RS485 bus or Ethernet back to a control room, wireless sensing differs in three ways.

Sensing points are not constrained by cabling. Fields, rivers, towers and street poles are often hundreds of metres or more from the control room, and cabling cost grows with distance. LoRaWAN sensors need no cable to the gateway; 4G data loggers use the cellular network.

Points without mains power can run long term. The S210x series and the S2100 data logger carry a lithium thionyl chloride battery with a nominal life of up to 10 years; higher-power devices can pair with a solar panel. Actual life depends on reporting interval, distance and ambient temperature.

Data can go to your own platform. Readings can be forwarded to your own system through the SenseCAP platform's API / MQTT; on the LoRaWAN path the network server can also run on a local server, so data never crosses the public internet.

---

System anatomy and three monitoring targets

Three backhaul paths: native LoRaWAN, RS485 to LoRaWAN, RS485 to 4G

A wireless environmental monitoring system has four roles:

• Sensors — measure physical quantities. Either native LoRaWAN sensors (own radio and battery) or RS485 / analogue industrial probes (need a data logger to go wireless)
• Data loggers — convert RS485 or analogue signals to wireless. The S2100 converts to LoRaWAN; the Sensor Hub 4G converts to cellular
• Gateways — receive LoRaWAN traffic and connect it to the internet or a local network. The 4G path needs no gateway
• Platform — the SenseCAP cloud, a self-hosted LoRaWAN network server, or your own system via API / MQTT

By monitoring target, requirements fall into three groups.

Outdoor weather: landing sites, transmission towers, city streets

A weather station combines wind speed and direction, temperature and humidity, pressure, rainfall and light in one pole-mounted unit. There are two kinds by backhaul: the S2120 is a native LoRaWAN battery device; the S500 to S1000 series output RS485 / SDI-12 only, need external DC power, and report through an S2100 or a Sensor Hub 4G.

Air and soil: livestock ventilation, building fresh air, greenhouse irrigation

CO₂, temperature, humidity and ammonia readings drive ventilation control; soil moisture, electrical conductivity (EC) and pH readings inform irrigation and fertigation. The S210x series covers most air and soil parameters on battery, and clustered points share one gateway.

Water quality: aquaculture, river sections, wastewater treatment

Dissolved oxygen, turbidity, pH, EC/TDS and liquid level are measured with RS485 industrial probes and sent back through an S2100 or a Sensor Hub 4G. Supply voltage varies widely across water-quality probes and is the first specification to check for these points (see Step 3).

---

Step 1: Fix the parameters and ranges

Selection starts from the parameter list. Find the model for each parameter first, then check its interface — the interface decides the backhaul path in Step 2.

Weather stations, by number of measurements:

The S700 is also available with radar rainfall (S700-A) and with solar radiation plus radar rainfall (S700-C). The S2120 protection rating is not listed on its specification page; confirm it with sales before ordering.

Air, soil and water-quality parameters:

Four rules:

1. Every item on the parameter list is a LoRaWAN model: no data logger is needed, only a gateway
2. Any RS485 device appears (S500–S1000 weather stations, water-quality probes, S-Soil soil probe): give it a data logger and check its supply in Step 3
3. Several RS485 probes at one point: the S2100 supports one protocol channel at a time; choose the Sensor Hub 4G (4 RS485 channels)
4. A greenhouse or shed needs only temperature, humidity, pressure, light and CO₂, and has cellular coverage: choose the SenseCAP Combo, all-in-one 4G with no data logger or gateway; add soil probes on its RS485 port

Scope. Ranges in the tables are rated values for checking whether a model covers the parameters you need; accuracy, response time and maintenance requirements are on each model's product page.

Step 2: Choose the backhaul

Backhaul is decided by how the points are distributed and what networks are available. The first question is whether the points sit within one gateway's coverage.

The two data loggers compared:

LoRaWAN gateways, by installation location:

Prices are reference prices at the time of lookup, for order of magnitude only; the product page is authoritative when ordering.

Four rules:

1. Points sit within one gateway's coverage: choose LoRaWAN. S210x and S2120 report directly; RS485 probes connect through an S2100
2. Points are scattered, a gateway is impractical, and there is cellular coverage: choose the Sensor Hub 4G. The S500–S1000 weather stations have no 4G of their own; cellular backhaul requires a Sensor Hub 4G
3. Data must stay on site: choose LoRaWAN and run the network server on the ChirpStack built into the M2 gateway or on your own server
4. Gateway location: indoors, the M2; on an outdoor pole, the outdoor gateway; inside a control cabinet with RS485 devices wired directly, the reComputer R1225

Scope. The S210x and S2100 list a nominal range of 2 km urban and 10 km line of sight; the S2120 lists 2–10 km line of sight, typically 1–3 km in real installations. Buildings, terrain and gateway height all change the result, so test the signal on site before fixing gateway positions. For points out of coverage, add a gateway or switch that point to 4G.

Step 3: Decide the power supply

There are three options: battery, solar and DC mains. The deciding factor is the nominal input voltage of the device and its probes, not whether the site has power.

Three rules:

1. Battery points: use native LoRaWAN sensors only, or probes powered at 3 V / 5 V through an S2100. The S2100 periodic power mode switches the probe on only before each reading to reduce consumption
2. Probes that need 12 V (dissolved oxygen, turbidity, liquid level): the S2100 battery cannot drive them; an external 12 V supply is required, so plan these as powered points. Aquaculture and wastewater points usually fall into this group
3. DC devices without mains: RS485 weather stations and the Sensor Hub 4G pair with the PV-12W waterproof solar panel (mounting bracket included)

Battery life. The S210x series and the S2100 list a nominal battery life of up to 10 years. This is the datasheet maximum; the actual figure depends on reporting interval, distance and ambient temperature, and with RS485 probes also on probe consumption. The S2120 specification gives no figure in years; its battery life depends on frequency band, distance to the gateway and ambient temperature. For project planning, estimate with the battery life calculator using the actual reporting interval.

Step 4: Match the installation environment

The site decides protection rating and mounting. The first question is whether the device is submerged; the second is whether it is exposed outdoors.

• Submerged in water or buried in soil (ponds, rivers, wastewater tanks, fields) → IP68 probes: dissolved oxygen, turbidity, liquid level, S-Soil MTEC-02
• Exposed outdoors, not submerged (poles, towers, rooftops) → IP65 / IP66 devices: weather stations, S210x, S2100, Sensor Hub 4G, outdoor gateway
• Hung inside a greenhouse or shed → SenseCAP Combo (IPX5, UV-resistant housing)
• Indoors or inside a control cabinet → M2 gateway (desktop), reComputer R1225 (IP40, DIN rail)

When installing the S2120, align the pole base to true north (compass or GPS); otherwise wind direction carries a fixed offset. Operating temperatures for the S2106 and the water-quality probes are not listed on their specification pages; check the product pages.

---

For solution providers and system integrators: from proof to delivery

If this setup is delivered to downstream customers, confirm the following three items at selection time.

Proof path. The agricultural environment monitoring reference design shows three ways to bring SenseCAP S210x nodes and the S2100 data logger into Home Assistant: through the SenseCAP cloud, through the local ChirpStack built into the M2 gateway, or through The Things Stack self-hosted on a reComputer R12 Series gateway. That design provides the integration configuration and data format; it gives no figures for range, nodes per gateway, packet loss or battery life. Estimate those from datasheets and confirm them on your own site.

Data integration. Readings reach your own platform through the SenseCAP API / MQTT; where data must stay on site, run a LoRaWAN network server locally. A self-hosted network server needs each node's join keys entered and the SenseCAP decoder installed; without them data cannot be decoded into measurements.

Hardware customisation and volume supply. The Seeed devices in this setup support custom logo, enclosure, packaging and pre-installed firmware, and interface configurations can be adjusted on existing models. Scope, certification coverage and lead times are on the ODM/OEM customisation service page.