OEM LoRaWAN Leaf Wetness Sensor Manufacturer for Smart Agriculture

2026-09-28 09:07:50 · Views 11

Fungal, bacterial and oomycete crop diseases frequently depend on a combination of moisture, temperature and time.

A crop canopy may remain wet after rain, dew, fog or overhead irrigation even when the nearest weather station reports no current rainfall. These local wet periods can create conditions associated with disease development.

A LoRaWAN leaf wetness sensor detects moisture on a surface designed to imitate some of the wetting and drying behavior of a leaf. It sends wetness, temperature and device-health data through a long-range wireless network to an agricultural platform.

The resulting data can support disease-risk models, spray-timing decisions, irrigation assessment and microclimate monitoring. However, the sensor does not directly detect a fungus, identify a pathogen or prove that disease is present.

Reliable monitoring depends on sensor technology, canopy placement, installation angle, crop type, local microclimate, maintenance and the selected agronomic model.

What Is a LoRaWAN Leaf Wetness Sensor?

A LoRaWAN leaf wetness sensor is an agricultural IoT endpoint that detects water or moisture on a simulated leaf surface and transmits the result through a LoRaWAN network.

A typical architecture is:

Leaf Wetness Probe → LoRaWAN Endpoint → Gateway → Network Server → Agricultural Platform → Disease-Risk or Farm-Management Tool

Depending on the design, the device may report:

Wet or dry state
Leaf wetness index
Wetness percentage
Leaf wetness duration
Probe-surface temperature
Air temperature
Relative humidity
Dew-point-related information
Rainfall input
Sensor contamination warning
Probe communication fault
Battery voltage
Low-battery alarm
Historical-record flag
Firmware and protocol versions

Some products integrate the sensing surface and radio enclosure. Others connect an external wetness probe to a LoRaWAN data logger through an analog, digital, SDI-12 or RS485 interface.

Leaf Wetness Is Not Soil Moisture

Leaf wetness and soil moisture answer different agricultural questions.

Soil Moisture

Soil moisture measurement describes water conditions around crop roots.

It can support:

Irrigation scheduling
Root-zone monitoring
Water-stress management
Drainage evaluation
Irrigation-zone comparison

The sensing technologies, soil installation and calibration considerations are discussed in the LoRaWAN soil moisture sensor guide.

Leaf Wetness

Leaf wetness describes water present on the crop surface or on a representative artificial sensing surface.

It can result from:

Rain
Dew
Fog
Overhead irrigation
Condensation
Splashing
High-humidity microclimates

A field may have dry soil and wet leaves after dew. It may also have moist soil and dry foliage after drip irrigation.

Both measurements can be useful, but one cannot replace the other.

Leaf Wetness Versus Plant Water Content

The term “leaf moisture sensor” can create confusion.

A conventional leaf wetness sensor normally detects water on the outside surface of a simulated leaf. It does not directly measure the water stored inside living plant tissue.

Internal plant-water status may require other methods, such as:

Leaf water potential measurement
Stem water potential
Sap-flow monitoring
Dendrometers
Infrared canopy temperature
Specialized spectroscopy
Laboratory analysis

An OEM product page should clearly state whether the device measures surface wetness or internal plant-water condition.

Why Leaf Wetness Duration Matters

Leaf wetness duration, often abbreviated as LWD, is the length of time that a sensor or crop surface remains wet.

It may be calculated as:

Wetness Duration = Time of Dry-to-Wet Transition Until Wet-to-Dry Transition

For example, a platform may record:

Wetness started at 21:40.
The canopy remained wet overnight.
The sensor became dry at 08:10.
Total detected wetness duration was 10 hours and 30 minutes.

The agronomic significance depends on:

Crop
Pathogen
Temperature
Crop growth stage
Humidity
Wetness duration
Previous infection conditions
Fungicide protection
Local disease model

There is no universal wetness duration that indicates disease for every crop.

How Leaf Wetness Supports Disease-Risk Monitoring

Many crop-disease models use environmental conditions associated with infection or sporulation.

Possible inputs include:

Leaf wetness state
Wetness duration
Air temperature
Leaf temperature
Relative humidity
Rainfall
Wind
Crop growth stage
Previous disease observations
Spray history

The model may produce:

Low-risk category
Moderate-risk category
High-risk category
Infection-period notification
Scouting recommendation
Spray-window reminder
Data-quality warning

These outputs are decision-support information rather than laboratory diagnosis.

A high-risk result means that environmental conditions may have favored a defined disease process. It does not prove that the pathogen was present or that infection occurred.

Typical Applications

Vineyards

Vineyards may use leaf wetness monitoring to support management of diseases influenced by canopy moisture.

Monitoring locations may include:

Different vineyard blocks
Low and high elevations
Dense and open canopies
Irrigated and non-irrigated areas
Different grape varieties
Wind-exposed and protected zones

A weather station outside the vineyard may not reproduce the microclimate inside a dense canopy.

Apple, Pear and Stone-Fruit Orchards

Orchard monitoring may help evaluate:

Overnight dew
Rain-wetting periods
Canopy drying
Differences between rows
Irrigation influence
Microclimates within tree blocks
Conditions used by crop-specific risk models

Sensor height and orientation should represent the fruiting canopy rather than the ground or the top of a weather-station mast.

Vegetable Crops

Possible applications include:

Tomatoes
Potatoes
Peppers
Cucurbits
Leafy vegetables
Beans
Onions
Brassicas

Several diseases can be influenced by prolonged wet foliage, but each crop-pathogen combination requires its own interpretation.

Greenhouses

A greenhouse can develop wet foliage through:

Condensation
High nighttime humidity
Low air movement
Overhead misting
Irrigation splash
Temperature differences
Roof dripping

Sensors can help compare:

Center and perimeter zones
Upper and lower canopy
Ventilated and stagnant areas
Heated and unheated sections
Different irrigation schedules

Greenhouse sensors should not be installed where roof drips fall directly on them unless the objective is to monitor that exact location.

Nurseries

Dense plant spacing and frequent irrigation can produce localized wetness conditions.

Monitoring may support:

Irrigation evaluation
Ventilation management
Disease-risk alerts
Comparison between plant benches
Propagation-area monitoring
Overnight condensation assessment

Field Crops

Leaf wetness data may be combined with weather and crop models for:

Cereals
Oilseeds
Legumes
Seed-production fields
Research plots
Specialty crops

Large fields may require several sensor locations because elevation, wind exposure, irrigation and canopy density can vary.

Agricultural Research

Research applications may require:

Raw sensor output
High-resolution timestamps
Configurable sampling
Local data storage
Calibration records
API access
Exportable quality flags
Multiple sensors per plot
Firmware-version traceability

The research protocol should define how wet and dry states are derived before data collection begins.

Resistance-Grid Leaf Wetness Sensors

A resistance sensor commonly uses two interleaved conductive traces on a flat or leaf-shaped surface.

When water bridges the traces, electrical resistance changes.

Potential Advantages

Resistance sensing may offer:

Simple electronics
Clear wet and dry response
Low component cost
Compatibility with external data loggers
Adjustable threshold logic
Compact artificial-leaf design

Important Limitations

Performance may be affected by:

Trace corrosion
Fertilizer salts
Pesticide residues
Dust
Bird droppings
Biofilm
Water conductivity
Surface coating
Excitation method
Installation angle
Droplet distribution

Direct-current excitation can contribute to electrode degradation in unsuitable designs. Alternating or controlled excitation may be considered according to the probe architecture.

A resistance probe must be tested with the intended surface material, coating and excitation circuit.

Capacitive and Dielectric Leaf Wetness Sensors

A capacitive or dielectric sensor detects changes in the electrical properties of its sensing surface when water is present.

Potential Advantages

Depending on the design, it may provide:

Sensitivity to small droplets
Continuous wetness index
No exposed conductive grid
Improved corrosion resistance
Detection of water or ice
Stable digital processing

Important Limitations

Performance may still be influenced by:

Surface contamination
Condensation pattern
Temperature
Cable capacitance
Mounting hardware
Nearby foliage
Coating properties
Water-film distribution
Firmware thresholds

A numerical wetness index is not automatically equivalent to the percentage of a natural leaf that is wet.

The manufacturer must define how the raw response is converted into dry, wet or fully wet categories.

Artificial Leaf Design

Most electronic leaf wetness sensors do not measure every crop leaf directly. They use an artificial surface designed to approximate selected wetting and drying characteristics.

Design variables include:

Shape
Thickness
Color
Surface texture
Thermal mass
Hydrophobic or hydrophilic behavior
Trace pattern
Surface coating
Sensor orientation
Edge drainage

An artificial surface cannot perfectly reproduce every crop.

A waxy grape leaf, hairy tomato leaf and broad vegetable leaf can collect and release water differently.

The sensor should therefore be treated as a repeatable reference surface rather than an exact electronic copy of every leaf.

Wetness Index, Percentage and Binary State

Different sensors may report different outputs.

Binary Wet or Dry State

The simplest output is:

This may be sufficient for calculating wetness duration.

Wetness Index

A continuous index can show how the sensor response changes between dry and heavily wetted conditions.

The documentation should define:

Index range
Dry threshold
Wet threshold
Saturation value
Hysteresis
Invalid state
Temperature compensation

Percentage Wetness

A percentage may describe a normalized sensor response.

It should not automatically be interpreted as the exact percentage of real crop leaves covered by water.

Raw Electrical Value

Research or OEM platforms may retain the raw resistance, voltage, capacitance or digital sensor value.

This allows later algorithm improvement but requires careful documentation and version control.

Wet and Dry Thresholds

The firmware must decide when the surface changes between dry and wet.

Possible logic includes:

Fixed threshold
Separate wet and dry thresholds
Temperature-dependent threshold
Adaptive baseline
Multiple consecutive samples
Minimum persistence time

Using separate transition values creates hysteresis and helps prevent rapid switching near the threshold.

For example:

Enter wet state above the defined wet threshold.
Remain wet until the response falls below a lower dry threshold.
Require the condition to persist for several measurements.

Thresholds must be validated with the final probe and intended installation.

Leaf Temperature

Some probes also measure surface temperature.

Leaf or probe temperature can help interpret:

Dew formation
Frost conditions
Wetness duration
Disease-model temperature bands
Canopy microclimate
Drying rate

An electronic sensing plate is not necessarily at exactly the same temperature as a living leaf.

Differences can result from:

Solar radiation
Surface color
Thermal mass
Airflow
Mounting bracket
Night-sky radiation
Water coverage

The platform should label the measurement correctly as probe temperature if that is what the device measures.

Dew, Rain, Fog and Irrigation

A wetness sensor may respond to moisture from several sources.

Dew

Dew can develop when a surface cools sufficiently for water vapor to condense.

A sensor inside the canopy may remain wet longer than an exposed weather-station sensor.

Rain

Rain can wet the sensor quickly, but wind direction and canopy shielding affect droplet interception.

Fog

Fog can deposit small droplets without producing measurable rainfall in a tipping-bucket gauge.

Overhead Irrigation

Sprinklers or misting systems may produce wetness events that resemble rain.

Drip Irrigation

Drip irrigation can increase soil moisture while leaving foliage dry, unless water splashes or humidity causes condensation.

The platform may combine wetness data with rainfall, irrigation-valve state and flow measurements to help classify events.

Sensor Placement Inside the Canopy

Placement is one of the most important sources of measurement variation.

The installation should consider:

Crop type
Canopy density
Row direction
Sensor height
Prevailing wind
Sun exposure
Irrigation layout
Slope
Nearby trees or buildings
Disease model
Maintenance access

Representative Canopy Position

For crop-disease monitoring, the sensor is often positioned where it experiences wetting and drying conditions representative of the crop canopy.

It should not automatically be mounted on top of a weather-station mast.

Sensor Angle

The angle affects:

Water collection
Droplet runoff
Drying rate
Solar exposure
Debris accumulation

The selected angle should follow the probe manufacturer’s instructions or the project’s validated installation protocol.

Orientation

Orientation relative to the crop row, sun and prevailing weather can influence results.

Every sensor in a comparative project should be installed consistently unless the objective is to study orientation differences.

Avoiding Contact

Leaves touching the sensing surface can:

Hold water against the probe
Shade the probe
Transfer residues
Change airflow
Produce unusually long wet periods

The mounting system should preserve the intended position as the crop grows.

How Many Sensors Does a Field Need?

One sensor may not represent an entire farm.

Additional monitoring points may be required where there are differences in:

Crop variety
Canopy structure
Elevation
Slope
Soil drainage
Irrigation zone
Wind exposure
Shade
Row orientation
Historical disease pressure

A practical zoning plan may include:

Representative normal location
Known high-risk location
Different crop block
Separate greenhouse compartment
Independent irrigation zone

The exact quantity should follow the agronomic objective rather than a fixed sensors-per-hectare rule.

Installation Errors

Common errors include:

Installing above the crop canopy
Mounting directly under a sprinkler nozzle
Allowing the probe to touch foliage
Using an inconsistent angle
Placing every sensor at the field edge
Installing next to a road or building
Routing the cable where water enters the enclosure
Leaving the sensing surface covered with residue
Moving the sensor without updating its platform location
Comparing data from differently installed probes

Installation records should include photographs, coordinates, crop block, height, angle and orientation.

Cleaning and Maintenance

Outdoor probes can accumulate:

Dust
Pollen
Pesticide residue
Fertilizer salts
Algae
Biofilm
Insects
Bird droppings
Plant material
Mineral deposits

Contamination may cause:

False wet readings
Delayed drying
Reduced sensitivity
Electrical leakage
Corrosion
Unstable thresholds

A maintenance procedure may include:

Place the sensor in maintenance mode.
Record the pre-cleaning condition.
Inspect the sensing surface.
Remove loose debris carefully.
Use only an approved cleaning method.
Avoid scratching traces or coatings.
Allow the sensor to dry.
Verify its dry response.
Apply a controlled wetness check where appropriate.
Return the probe to its documented position.
Close maintenance mode.
Record the work performed.

Abrasive tools or inappropriate chemicals may permanently change the surface response.

Calibration and Functional Verification

Leaf wetness sensors are often used as comparative or threshold instruments rather than as direct measurements of a universal physical unit.

Verification may include:

Dry-state check
Controlled droplet application
Full-surface wetting
Transition-time check
Drying-response comparison
Temperature-channel verification
Comparison between production units
Chamber testing
Collocation with a reference probe

The procedure should document:

Water type
Droplet size or method
Surface coverage
Sensor angle
Temperature
Humidity
Airflow
Stabilization time
Acceptance criteria

Spraying an uncontrolled amount of water without documenting the method is not a repeatable calibration.

Frost and Ice

Some sensing surfaces may respond to frost or ice, but the interpretation depends on the technology.

Potential issues include:

Frozen water producing a different electrical response
Slow thawing
Surface coating damage
Temperature below the qualified range
Condensation during warming
Ice bridging exposed traces

If frost monitoring is required, the project should validate:

Minimum temperature
Temperature accuracy
Wetness response to frost
Thaw behavior
Enclosure sealing
Battery performance
Alarm logic

A standard wetness sensor should not be described as a frost detector unless that function has been verified.

Disease-Risk Models

A disease-risk model may combine sensor readings with crop and pathogen information.

Possible model inputs include:

Wetness start time
Continuous wetness duration
Temperature during wetness
Rainfall
Relative humidity
Crop growth stage
Previous infection period
Treatment history

A suitable platform should identify:

Model name
Model version
Crop
Target disease
Input sensors
Missing-data behavior
Risk calculation time
Alert threshold
User configuration

Missing Data

A model should not automatically treat missing wetness data as dry conditions.

Missing information may result from:

Battery failure
Probe disconnection
Gateway outage
Radio interference
Damaged cable
Firmware restart
Sensor maintenance

The platform should display a data-quality warning when an infection-risk calculation is incomplete.

Model Validation

A model developed for one crop, pathogen or climate should not automatically be applied to another region.

Customers should work with qualified agronomists, plant pathologists or local extension guidance when configuring disease-risk rules.

Spray-Decision Support

Leaf wetness information may help users:

Review recent infection-favorable periods
Plan field scouting
Evaluate canopy drying
Compare blocks
Examine conditions after treatment
Select a practical spray window

The sensor does not determine:

Which pesticide is legally permitted
The correct application rate
Re-entry interval
Pre-harvest interval
Resistance-management program
Worker-protection requirements

Agricultural chemical decisions must follow the approved product label and applicable local requirements.

Irrigation Integration

Leaf wetness monitoring can complement irrigation control.

Possible functions include:

Avoid overhead irrigation during high-risk periods
Compare wetness duration before and after irrigation changes
Detect unexpectedly wet foliage
Evaluate nighttime irrigation
Compare drip and sprinkler zones
Confirm canopy drying before another event

A complete architecture may be:

Leaf Wetness Sensor + Soil Moisture Sensor + Weather Data → Platform Rules → Irrigation Controller

The LoRaWAN irrigation valve controller guide provides additional information about remote valves, irrigation zones and control logic.

Essential pump protection, valve interlocks and water-pressure safeguards should remain in suitable local control equipment.

Sampling and Reporting Strategy

A typical measurement cycle may be:

Read the wetness probe.
Measure probe or air temperature.
Apply compensation.
Evaluate the wet or dry state.
Update the wetness-duration counter.
Check sensor quality.
Store the measurement.
Compare it with alarm rules.
Transmit an event or scheduled summary.
Return eligible circuits to a low-power state.

The device may sample more frequently than it transmits.

Possible uplinks include:

Dry-to-wet transition
Wet-to-dry transition
Current wetness value
Accumulated wetness duration
Temperature
Periodic minimum and maximum
Sensor fault
Low-battery alarm
Scheduled heartbeat

Transition events should include timestamps or sequence numbers so the platform can reconstruct wetness duration after a communication outage.

Battery and Solar Power

Battery operation may be practical when:

The probe has low power consumption.
Measurements are periodic.
The device operates in LoRaWAN Class A.
Reporting is event-based or infrequent.
No local display is continuously powered.
Gateway coverage is suitable.

The power budget should include:

Probe excitation
Temperature sensing
Sampling interval
Local calculations
Event storage
LoRaWAN transmissions
Alarm traffic
Confirmed-message retries
Bluetooth or NFC configuration
Battery self-discharge
Low-temperature performance
Firmware sleep current

Solar power may be considered when the product requires:

Frequent measurements
Several probes
Local weather instruments
Continuous processing
Powered ventilation or cleaning
Frequent downlink communication

Battery-duration claims must be verified with the final sensor, radio settings and environmental conditions.

LoRaWAN Payload Design

A leaf wetness payload may include:

Wet or dry state
Wetness index
Wetness percentage
Wetness-duration counter
Probe temperature
Air temperature
Relative humidity
Rain input
Sensor contamination flag
Probe fault
Calibration status
Battery voltage
Solar-charging status
Sequence number
Measurement timestamp
Historical-record flag
Firmware version
Protocol version

The payload specification should define:

Wetness units
Index scaling
Temperature units
Wet and dry codes
Threshold version
Invalid-value codes
Sensor-fault meanings
Counter rollover
Timestamp format
Historical-data handling
Protocol compatibility

A disconnected or contaminated probe should not be decoded as a confirmed dry canopy.

Local Storage and Gateway Outages

The sensor may continue recording while the gateway or backhaul is unavailable.

Local memory can store:

Wet and dry transitions
Wetness values
Temperature
Accumulated wetness duration
Alarm events
Sensor faults
Maintenance events
Configuration changes
Device restarts

Each record should include:

Original timestamp
Sequence number
Measurement-quality flag
Threshold version
Historical-record flag

After communication returns, stored records should be uploaded in the correct order.

An old wetness transition must not be presented as a new live rain or disease-risk event.

Gateway Planning for Farms

Agricultural radio coverage can be affected by:

Hills
Trees
Dense crop canopy
Greenhouse structures
Metal irrigation equipment
Storage buildings
Low sensor mounting
Seasonal vegetation
Long distances
Uneven terrain

Gateway planning should consider:

Farm area
Number of sensors
Crop height
Gateway antenna height
Terrain
Reporting interval
Event traffic
Required redundancy
Ethernet or cellular backhaul
Solar-power requirements
Regional frequency plan

The industrial LoRaWAN gateway selection and deployment guide provides further information about antennas, backhaul, capacity and private networks.

A coverage survey should use the final enclosure, antenna and canopy-level installation.

Agricultural Platform Functions

A suitable platform may provide:

Farm, field and crop-block hierarchy
Map of sensor locations
Current wet or dry state
Wetness trend chart
Wetness-duration calculation
Probe temperature
Air temperature and humidity
Rainfall comparison
Irrigation-event comparison
Disease-risk categories
Scouting notifications
Spray-event annotations
Sensor-maintenance records
Low-battery alarms
Device-offline alerts
Gateway status
User permissions
Scheduled reports
Data export
MQTT integration
HTTP API
Farm-management integration

The platform should distinguish:

Valid wetness measurement
Probe fault
Sensor contamination
Missing data
Maintenance mode
Historical record
Model-estimated value
Manually entered observation

OEM and ODM Customization Options

A custom LoRaWAN leaf wetness sensor may include:

Resistance-grid probe
Capacitive or dielectric probe
Wet or dry output
Continuous wetness index
Leaf or probe temperature
Air temperature and humidity
Rain gauge input
Soil-moisture input
Soil-temperature input
RS485 Modbus interface
SDI-12 interface
Analog voltage input
Multiple probe channels
Local data storage
Configurable wet and dry thresholds
Local display
Status indicator
Replaceable battery
External DC power
Solar charging
Internal or external antenna
Pole, trellis or greenhouse mounting
Bluetooth or NFC configuration
Customer-defined payload
Private Network Server integration
Agricultural platform API
Branded enclosure, labels and packaging

Projects requiring a dedicated sensor interface or radio controller can also evaluate custom LoRaWAN PCB design and development.

Regional Frequency and Compliance Planning

The endpoint and gateway must use the LoRaWAN regional plan permitted in the destination market.

Common plans include:

EU868
US915
AU915
AS923 variants
CN470
IN865
KR920
RU864

The final product may also require evaluation for:

Radio compliance
Electromagnetic compatibility
Electrical safety
Battery transportation
Ingress protection
UV resistance
Environmental testing
Agricultural chemical exposure
Temperature operation
Product labeling

No measurement accuracy, battery duration, ingress rating, disease-prevention claim or regulatory certification should be published before verification of the final production configuration.

Recommended OEM Development Process

1. Define the Crop and Disease Objective

Identify the crop, target disease model, growth stage and required environmental inputs.

2. Define the Measurement Output

Choose wet/dry state, wetness index, percentage, duration or raw sensor data.

3. Select the Probe Technology

Compare resistance and dielectric sensing according to sensitivity, contamination, corrosion, power and maintenance requirements.

4. Define the Installation

Specify canopy height, sensor angle, orientation, mounting bracket, cable length and number of monitoring zones.

5. Design the Electronics

Complete probe excitation, signal conditioning, temperature measurement, power architecture, storage and LoRaWAN communication.

6. Develop Wetness Logic

Implement thresholds, hysteresis, persistence, duration calculation, fault detection and quality flags.

7. Develop the Platform Model

Define crop blocks, transition records, risk-model inputs, missing-data behavior, alerts and API outputs.

8. Test Environmental Conditions

Evaluate rain, dew simulation, condensation, temperature, humidity, drying, residues, frost and representative agricultural chemicals.

9. Conduct a Field Pilot

Install sensors across representative and high-risk zones. Compare sensor data with canopy observations and local agronomic guidance.

10. Prepare for Production

Finalize probe inspection, test fixtures, firmware versioning, LoRaWAN credentials, provisioning, labels, packaging and traceability.

Information Required for a Quotation

Customers should provide:

Crop and variety
Greenhouse, vineyard, orchard or open-field application
Disease-risk or general microclimate objective
Required wetness output
Leaf or probe-temperature requirement
Air temperature and humidity requirement
Rain-gauge or weather-station integration
Soil-moisture integration
Number and size of crop blocks
Proposed sensor height and mounting method
Required probe cable length
Measurement and reporting intervals
Wet and dry threshold requirements
Local storage duration
Battery, external-power or solar preference
Operating-temperature range
Expected pesticide, fertilizer and dust exposure
Destination country and LoRaWAN frequency
Gateway and backhaul requirements
Network Server
Disease model, farm platform or API requirements
Prototype and estimated production quantities
Logo, enclosure, labels and packaging requirements

Crop maps, trellis drawings, irrigation layouts and photographs of representative canopies can improve the product recommendation.

Frequently Asked Questions

What does a LoRaWAN leaf wetness sensor measure?

It detects water on a simulated leaf surface and transmits the wetness state, index or duration through a LoRaWAN network.

Is leaf wetness the same as soil moisture?

No. Leaf wetness describes water on the crop surface. Soil moisture describes water around the roots.

Does the sensor measure water inside a living leaf?

Normally no. A conventional leaf wetness probe measures surface wetness on an artificial sensing plate.

What is leaf wetness duration?

It is the time between the detected start of a wet period and the return to a dry condition.

Can it detect crop disease?

It does not directly detect a pathogen or diagnose disease. Its data can support crop-specific disease-risk models.

Can one disease threshold be used for every crop?

No. Risk depends on the crop, pathogen, temperature, wetness duration, growth stage and local agronomic conditions.

Can the sensor distinguish rain from dew?

Not by wetness data alone. Rainfall, humidity, temperature and irrigation records can provide additional context.

Where should the sensor be installed?

It should normally be placed at a representative position within the crop canopy using a documented height, angle and orientation.

Should the sensing plate touch real leaves?

Normally no. Contact can change airflow, retain water and distort drying time.

How many sensors are required?

The number depends on field size, elevation, crop variety, canopy structure, irrigation zones and microclimate variability.

Can pesticide residue affect the reading?

Yes. Residues, salts, dust and biofilm can change the electrical or surface behavior of the probe.

Does the probe require cleaning?

Yes. It should be inspected and cleaned using a method compatible with its traces, coating and enclosure.

Can it operate from batteries?

Yes, depending on the probe, sampling interval, reporting frequency, radio coverage and environmental temperature.

What happens when the gateway is offline?

The sensor can continue measuring and store events if local memory is included. Live remote alerts require an available communication path.

Does every sensor require a SIM card?

No. Sensors communicate with a shared LoRaWAN gateway. The gateway may use cellular backhaul where fixed internet is unavailable.

Can it control an irrigation valve?

Its data can participate in platform rules, but leaf wetness does not replace soil moisture, flow, pressure and local pump-protection information.

Can it integrate with an existing farm platform?

Custom payloads, MQTT, HTTP APIs and private Network Server integration can be evaluated according to the customer’s architecture.

Is private-label manufacturing available?

Probe selection, PCB design, firmware, enclosure, wetness algorithms, payloads, labels, packaging and platform integration can be evaluated for OEM or ODM production.

Conclusion

A LoRaWAN leaf wetness sensor provides distributed information about dew, rain, fog, condensation and irrigation-related wetness across vineyards, orchards, greenhouses, nurseries and field crops.

Its most useful output is often not one instantaneous number but the beginning, duration and end of each wet period. When combined with temperature, humidity, rainfall and crop-specific models, these records can support disease-risk assessment and field-scouting decisions.

Reliable data depends on consistent placement, angle, surface condition and maintenance. A sensor above the canopy, beneath a sprinkler or covered with residue may produce results that do not represent the crop.

The device should also be presented within its correct limits. It measures conditions associated with crop disease risk; it does not identify pathogens, diagnose infection or determine which agricultural chemical should be applied.

Shenzhen Jinshengchang Technology Co., Ltd. can evaluate OEM and ODM leaf-wetness monitoring projects covering probes, PCB design, embedded firmware, LoRaWAN communication, gateways, payload protocols, agricultural platforms, APIs, prototypes and production preparation.

Request an OEM LoRaWAN Leaf Wetness Sensor Proposal

Send your crop, disease-monitoring objective, field layout, sensing technology preference, installation method, sampling interval, environmental requirements, destination country, estimated quantity and platform interface for technical evaluation.

Shenzhen Jinshengchang Technology Co., Ltd.

WhatsApp: +86 134 8088 1974
Phone: +86 134 8088 1974
Phone: +86 177 2242 0256
Email: 397017470@qq.com