OEM LoRaWAN PM2.5 Sensor Manufacturer for Air Quality Monitoring

Airborne particulate matter can vary significantly between streets, buildings, workshops and different areas of the same industrial site.

A single central monitoring station may provide high-quality regional data but cannot represent every school entrance, construction boundary, warehouse, factory workshop or traffic corridor.

A LoRaWAN PM2.5 sensor adds distributed particulate monitoring without requiring a cellular subscription or data cable at every measurement point. It measures airborne particles, processes the result locally and sends selected values through a LoRaWAN gateway.

For OEM and ODM projects, reliable performance depends on much more than connecting a particle-sensing module to a LoRaWAN radio. The airflow path, humidity response, enclosure, fan, contamination control, calibration, power supply, installation position and data-quality strategy all affect the final result.

What Is a LoRaWAN PM2.5 Sensor?

A LoRaWAN PM2.5 sensor is a wireless IoT endpoint that measures fine airborne particulate matter and transmits the result through a LoRaWAN network.

A typical system architecture is:

Particle Sensor → LoRaWAN Device → Gateway → Network Server → Air Quality Platform

Depending on the selected sensing module and product design, the device may report:

• PM1.0 concentration
• PM2.5 concentration
• PM10 concentration
• Particle-count bins
• Temperature
• Relative humidity
• Air-quality status
• Warning or alarm state
• Sensor-fan status
• Measurement-quality flag
• Battery or input voltage
• Filter-maintenance reminder
• Communication status
• Firmware version

The platform can organize measurement points by city, district, building, floor, workshop or monitoring zone.

What Do PM1.0, PM2.5 and PM10 Mean?

Particulate matter is commonly grouped according to aerodynamic particle diameter.

PM1.0

PM1.0 generally refers to particles with an aerodynamic diameter of approximately one micrometer or less.

Whether a sensor reports PM1.0 depends on its optical design, firmware and output protocol.

PM2.5

PM2.5 refers to fine particulate matter with an aerodynamic diameter of 2.5 micrometers or less.

It is commonly included in air-quality monitoring because fine particles can remain suspended and travel through indoor and outdoor air.

PM10

PM10 includes particles with an aerodynamic diameter of 10 micrometers or less.

Construction dust, road dust and industrial activities may produce substantial PM10 variation.

A device that reports all three values does not necessarily contain three independent sensing elements. Many optical modules estimate several particulate fractions from the same sampled particle signal.

How Does an Optical Particle Sensor Work?

Many compact PM sensors use optical light-scattering measurement.

A typical sensing process is:

1. Air enters the measurement chamber.
2. A fan or controlled airflow moves particles through the optical path.
3. A light source illuminates the particles.
4. Scattered light reaches a photodetector.
5. Electronics process the signal.
6. An algorithm estimates particle size distribution or mass concentration.
7. The MCU reads the result and prepares the LoRaWAN payload.

The displayed value is therefore influenced by:

• Optical design
• Airflow
• Particle shape
• Particle refractive properties
• Particle density assumptions
• Humidity
• Sensor contamination
• Signal-processing algorithm
• Factory calibration
• Field correction

A compact optical sensor is not automatically equivalent to a regulatory reference instrument.

Particle Count Versus Mass Concentration

Buyers should understand what the selected sensor actually measures.

Particle Count

Some modules classify detected particles into size bins and report an estimated number of particles within each range.

This output may be useful for:

• Research
• Source comparison
• Filtration studies
• Indoor environmental analysis
• Sensor diagnostics

Mass Concentration

Air-quality platforms commonly display PM values in micrograms per cubic meter.

Optical sensors usually estimate mass concentration from the measured scattering response and assumptions about particle properties.

Two environments containing the same number of particles may not produce the same estimated mass if particle size, density or composition differs.

An OEM supplier should document whether the output is:

• A direct module reading
• A manufacturer-corrected value
• A locally calibrated value
• A platform-adjusted result
• A particle count
• An estimated mass concentration

Typical LoRaWAN PM2.5 Sensor Applications

Smart City Air Quality Networks

Distributed LoRaWAN sensors can add measurement points around:

• Roads
• Schools
• Parks
• Residential areas
• Bus stations
• Public buildings
• Industrial boundaries
• Pedestrian zones
• Waste-transfer facilities

These sensors can help visualize local differences and identify periods requiring further investigation.

They should normally be described as supplemental or informational sensors unless the complete monitoring system meets the applicable regulatory requirements.

Schools and Educational Buildings

PM levels can change because of:

• Outdoor pollution entering the building
• Ventilation operation
• Cleaning activities
• Chalk or craft materials
• Occupant movement
• Nearby traffic
• Construction work
• Open windows and doors

A monitoring system can compare classrooms, entrances and outdoor reference positions.

The device may also measure temperature, humidity and CO₂, but each parameter has different sensing and calibration requirements.

Offices and Commercial Buildings

Indoor PM monitoring may support:

• Filtration assessment
• HVAC maintenance
• Indoor environmental dashboards
• Cleaning evaluation
• Outdoor-air comparison
• Tenant comfort programs
• Building automation integration

A PM sensor should be installed where it samples representative occupied-zone air rather than directly beside a supply vent or open window.

Construction Sites

Construction activities can generate rapidly changing dust levels.

Potential measurement locations include:

• Site boundaries
• Vehicle entrances
• Material-handling areas
• Demolition zones
• Nearby sensitive locations
• Worker welfare areas

Outdoor installation requires careful attention to weather protection, airflow, maintenance and power.

A general environmental PM monitor should not be presented as a certified personal dust-exposure instrument.

Factories and Workshops

Industrial applications may include:

• Woodworking
• Food processing
• Packaging
• Material handling
• Warehouses
• Manufacturing workshops
• Loading zones
• Dust-collection equipment areas

The sensor can indicate changing particulate conditions and support inspection.

It does not identify the chemical composition of the particles or replace the appropriate occupational exposure measurement method.

Warehouses and Logistics Facilities

Forklifts, loading activities, packaging materials and open loading doors can affect particulate levels.

A LoRaWAN network can connect several monitoring points without installing a new data cable across the warehouse.

Agricultural Facilities

Feed handling, bedding, animal activity, grain processing and ventilation can generate airborne particles.

Agricultural installations may also need:

• Ammonia monitoring
• CO₂ monitoring
• Temperature and humidity
• Fan-status data
• Outdoor weather information

Every sensing channel should be evaluated separately for range, maintenance and cross-influence.

Indoor Versus Outdoor PM2.5 Sensor Design

An indoor sensor and outdoor monitoring node may require different mechanical structures.

Indoor Design

Indoor devices may prioritize:

• Quiet fan operation
• Compact enclosure
• Wall or desktop installation
• Low visual impact
• Local display
• Status indicator
• USB or DC power
• Occupant-facing air-quality status

Outdoor Design

Outdoor devices may require:

• Rain protection
• UV-resistant materials
• Insect protection
• Controlled air inlet
• Water drainage
• Condensation management
• Replaceable inlet filter or screen
• Solar or external power
• Pole or wall mounting
• Protected antenna installation

A fully sealed enclosure can protect the electronics but prevent representative air from reaching the sensing chamber.

The enclosure must protect the device without creating an uncontrolled, stagnant air volume.

Airflow Path Design

The airflow path is one of the most important parts of a particulate monitor.

The design should define:

• Air inlet position
• Air outlet position
• Flow direction
• Fan location
• Measurement chamber
• Protective screen
• Drainage
• Separation from warm electronics
• Access for cleaning
• Resistance to wind-driven rain

Avoiding Air Recirculation

If the outlet is too close to the inlet, sampled air may recirculate through the device.

This can reduce the representativeness of the reading.

Avoiding Heat Influence

The radio, MCU, display, power supply and battery-charging circuit can warm the air inside the enclosure.

This may affect temperature and humidity measurements and can influence particle behavior around the sensing chamber.

Passive Versus Fan-Assisted Airflow

Some designs use passive diffusion, while others use a fan.

Fan-assisted measurement can provide more controlled sampling but introduces:

• Additional power consumption
• Mechanical wear
• Noise
• Dust accumulation
• Fan-stall risk
• Maintenance requirements

The selected airflow system must match the required sampling frequency and power architecture.

Humidity Interference

High relative humidity can affect optical particulate readings.

Water can accumulate on or around hygroscopic particles, making them scatter more light. The sensor may then report a different concentration even if the dry particulate mass has not changed proportionally.

Humidity can also cause:

• Condensation on optical surfaces
• Blocked inlet screens
• Fog droplets entering the chamber
• Corrosion
• Electrical leakage
• Slower sensor recovery

An OEM design may include:

• Temperature and humidity measurement
• Humidity flags
• Data-quality warnings
• Approved correction algorithms
• Heated inlet evaluation
• Condensation-resistant air paths
• Protected mounting

A correction algorithm should be based on testing or documented sensor guidance. It should not be invented solely to make the chart appear smoother.

Aerosol Composition Affects Optical Measurement

Optical scattering depends partly on particle properties.

Examples of different particle sources include:

• Combustion smoke
• Wildfire smoke
• Road dust
• Construction dust
• Sea salt
• Agricultural dust
• Industrial powder
• Cooking emissions
• Indoor cleaning aerosols

A calibration relationship developed for one aerosol type may not perform identically for another.

This is why an OEM buyer should define the intended environment before sensor selection.

Sensor Placement

Installation position determines what the device measures.

Avoid placing the sensor:

• Directly beside an exhaust pipe
• Immediately below an HVAC supply outlet
• Against a wall that blocks airflow
• Inside a sealed cabinet
• Directly beside a humidifier
• Where rain enters the air inlet
• Above a strong heat source
• Where cleaning spray reaches the sensor
• Behind a permanent obstruction
• In an inaccessible maintenance location

Outdoor monitoring plans should also consider:

• Mounting height
• Distance from roads
• Nearby buildings
• Trees
• Local emission sources
• Prevailing wind
• Security
• Electrical power
• Gateway coverage

Monitoring objectives should be defined before installation. A roadside sensor, neighborhood-background sensor and factory-boundary sensor require different site-selection logic.

Reference Monitoring and Sensor Collocation

Compact PM sensors should be evaluated against an appropriate reference before procurement claims are finalized.

Collocation means operating the LoRaWAN sensor near a reference instrument so both devices sample similar environmental conditions.

A collocation program may evaluate:

• Measurement agreement
• Linear response
• Bias
• Precision between units
• Temperature influence
• Humidity influence
• Low-concentration behavior
• High-concentration behavior
• Missing data
• Sensor drift
• Unit-to-unit variation

Collocation Before Deployment

A sample group can be tested before field installation to establish baseline performance.

Field Collocation

Selected production devices may be periodically returned to a reference site for verification.

Multiple-Unit Testing

Testing only one prototype does not show production variation.

Several units should be operated together where the project requires consistent results across a distributed network.

Collocation results should be reported with the tested sensor model, firmware, enclosure and correction method.

Calibration and Data Correction

Calibration may take place at several levels.

Sensor-Module Calibration

The sensing-module supplier may provide factory calibration and internal algorithms.

Device-Level Calibration

The completed enclosure and airflow design may require additional testing because the product can behave differently from a bare module.

Site-Specific Correction

A correction model may be developed from collocation data collected in the intended environment.

Platform-Level Adjustment

The cloud platform may apply correction coefficients based on:

• Device model
• Temperature
• Relative humidity
• Location
• Reference period
• Firmware version

The platform should preserve enough information to identify whether a value is raw, corrected or invalid.

Calibration coefficients must be versioned. A firmware or platform update should not silently change historical interpretation.

PM Sensor Cleaning and Aging

Dust can accumulate inside the airflow path and optical chamber.

Possible effects include:

• Raised baseline
• Reduced airflow
• Unstable readings
• Fan overload
• Slower response
• Increased measurement noise
• Complete sensor failure

Maintenance may involve:

• Cleaning the inlet
• Replacing an external screen
• Inspecting drainage
• Checking the fan
• Cleaning approved optical surfaces
• Comparing with a reference
• Replacing the sensing module
• Recording the maintenance event

The cleaning procedure should follow the sensing-module requirements. Compressed air, solvents or direct contact with optics may damage some modules.

The OEM design should allow technicians to service the device without changing the sensor alignment or damaging the enclosure seals.

Detecting Sensor Faults

A valid zero measurement is different from a sensor fault.

Firmware should detect conditions such as:

• No response from the sensor
• Invalid data frame
• Fan failure
• Repeated identical values
• Impossible particle distribution
• Sensor warm-up
• Optical contamination warning
• Reading outside the supported range
• Internal communication error
• Power-supply instability

The LoRaWAN payload should report a diagnostic state instead of converting every error into zero.

Measurement and Reporting Strategy

A PM sensor can measure more frequently than it transmits.

A typical process may be:

1. Wake the controller.
2. Activate the sensor or confirm continuous operation.
3. Allow airflow and readings to stabilize.
4. Collect several samples.
5. Remove invalid data.
6. Calculate averages, minimums or maximums.
7. Apply documented correction.
8. Compare the result with thresholds.
9. Store selected records.
10. Transmit a summary or alarm.
11. Return eligible circuits to low-power mode.

The design must account for sensor warm-up time. A short measurement immediately after power-up may not represent stable performance.

Averaging and Alarm Logic

Particle readings can change quickly.

Firmware or platform processing may use:

• Moving averages
• Median filters
• Time-weighted averages
• Minimum and maximum values
• Outlier rejection
• Alarm persistence
• Hysteresis
• Rate-of-rise detection
• Data-quality flags

Possible alarms include:

• PM2.5 above warning threshold
• PM2.5 above critical threshold
• PM10 above threshold
• Sustained elevated concentration
• Rapid concentration increase
• Sensor fault
• Fan fault
• Device offline
• Low battery

Thresholds should follow the customer’s monitoring objective and applicable local guidance. One universal value should not be used for every country, workplace and application.

Battery or External Power?

Particulate sensors often consume more power than simple temperature or door-contact sensors.

Battery-Powered Operation

Battery operation may be possible when the device uses:

• Periodic sampling
• Controlled sensor warm-up
• Infrequent LoRaWAN reporting
• Efficient fan management
• Low-power MCU operation
• Suitable battery chemistry

The power budget should include:

• Sensor startup current
• Fan current
• Optical-source current
• Sampling duration
• Measurement interval
• LoRaWAN transmission
• Confirmed-message retries
• Local storage
• Temperature and humidity sensing
• Firmware sleep current

External Power

External DC, USB or building power may be more appropriate for:

• Continuous measurement
• Rapid alarms
• Short reporting intervals
• Local display
• Multiple gas sensors
• Heated inlet
• LoRaWAN Class C
• Relay output
• Permanent outdoor stations

A backup battery can be evaluated where data collection must continue during a power interruption.

Solar Power

Solar operation may be considered for outdoor monitoring stations.

The system design must account for:

• Sensor and fan consumption
• LoRaWAN radio
• Battery capacity
• Solar-panel orientation
• Seasonal sunlight
• Shading
• Temperature
• Charge-controller losses
• Required backup duration

Solar sizing should be calculated from the complete device load, not from the radio alone.

LoRaWAN Payload Design

A particulate-monitor payload may include:

• PM1.0 concentration
• PM2.5 concentration
• PM10 concentration
• Particle counts
• Temperature
• Relative humidity
• Air-quality status
• Warning and alarm flags
• Raw or corrected-data indicator
• Sensor warm-up status
• Fan or optical fault
• Battery or input voltage
• Historical-record flag
• Sequence number
• Firmware version
• Protocol version

The payload specification should define:

• Units
• Scaling
• Byte positions
• Field lengths
• Byte order
• Invalid-value codes
• Alarm-bit meanings
• Correction-status flags
• Counter rollover
• Protocol compatibility

A documented protocol helps prevent a platform from confusing micrograms per cubic meter, particle counts and air-quality indexes.

Local Storage and Communication Recovery

The device may continue collecting measurements while its gateway or backhaul is unavailable.

Local memory can store:

• Periodic PM values
• Temperature and humidity
• Minimum and maximum readings
• Alarm events
• Sensor faults
• Calibration changes
• Device restarts
• Communication failures

When connectivity returns, historical data should be uploaded at a controlled rate.

Delayed records must be identified clearly so the platform does not display an old high-PM event as a new live alarm.

Gateway Planning for Air Quality Networks

Gateway planning depends on the deployment environment.

Indoor Buildings

Consider:

• Floors
• Reinforced concrete
• Mechanical rooms
• Metal partitions
• Basements
• Sensor quantity
• Gateway backhaul
• Redundancy requirements

Outdoor Cities and Campuses

Consider:

• Building height
• Street layout
• Trees
• Terrain
• Gateway antenna position
• Outdoor power
• Cellular or Ethernet backhaul
• Weather protection
• Number of monitoring points

Industrial Sites

Consider:

• Metal machinery
• Electrical interference
• Production buildings
• Outdoor yards
• Dust sources
• Restricted installation zones
• Gateway redundancy

The industrial LoRaWAN gateway selection guide provides additional guidance about frequency plans, antennas, capacity and backhaul.

A coverage pilot should be completed before large-scale installation.

Air Quality Platform Functions

A monitoring platform may provide:

• Site and zone hierarchy
• Map-based monitoring points
• Current PM1.0, PM2.5 and PM10 values
• Temperature and humidity
• Historical charts
• Raw and corrected data
• Air-quality status
• Warning and alarm events
• Sensor-fault notifications
• Device-offline alarms
• Battery condition
• Gateway status
• Maintenance records
• Calibration records
• Data export
• User permissions
• MQTT integration
• HTTP API
• Customer platform integration

A companion LoRaWAN industrial temperature sensor can be evaluated when separate temperature monitoring points are required outside the particulate sensor enclosure.

Air Quality Index Calculation

A platform may convert particulate concentration into an air-quality category or index.

However, index calculations vary by country and authority.

The software specification should define:

• Selected index
• Pollutants included
• Averaging period
• Breakpoints
• Units
• Rounding rules
• Missing-data behavior
• Update interval
• Version of the calculation method

The displayed index should not combine incompatible national calculation methods.

The platform should retain the measured concentration even when an index is displayed to users.

OEM and ODM Customization Options

A custom LoRaWAN PM2.5 sensor may include:

• PM1.0, PM2.5 and PM10 measurement
• Particle-count output
• Temperature and humidity
• CO₂
• VOC
• Carbon monoxide
• Nitrogen dioxide
• Ozone
• Barometric pressure
• Fan diagnostics
• Replaceable sensing module
• Local display
• Color status indicator
• Buzzer
• Relay output
• RS485 or Modbus
• 4–20mA output
• Battery operation
• External DC power
• Solar power
• Backup battery
• Local data storage
• Internal or external antenna
• Indoor or outdoor enclosure
• Wall or pole mounting
• Bluetooth or NFC configuration
• Customer-defined payload
• Private Network Server integration
• Customer API
• Branded enclosure, labels and packaging

Each additional sensing channel requires separate evaluation. One calibration method cannot automatically verify PM, CO₂, VOC and gas measurements together.

Regional Frequency and Compliance Planning

The sensor and gateway must use the frequency plan required in the destination market.

Common regional plans include:

• EU868
• US915
• AU915
• AS923 variants
• CN470
• IN865
• KR920
• RU864

The project may also need to evaluate:

• Radio compliance
• Electromagnetic compatibility
• Electrical safety
• Optical safety
• Battery transportation
• Environmental testing
• Product labeling
• Air-monitoring requirements
• Outdoor enclosure testing
• Calibration documentation

No certification, measurement accuracy, ingress rating, battery duration or regulatory-monitoring claim should be made before it has been verified for the final product.

Recommended OEM Development Process

1. Define the Monitoring Purpose

Confirm whether the device will support indoor air quality, city mapping, construction monitoring, industrial inspection or another application.

2. Define the Required Measurements

Specify PM fractions, particle counts, temperature, humidity and any additional gas channels.

3. Select the Particle Sensor

Compare measurement range, airflow method, power, warm-up time, maintenance and output protocol.

4. Design the Air Path and Enclosure

Develop the inlet, outlet, rain protection, drainage, optical protection and access for cleaning.

5. Develop Hardware and Firmware

Complete the sensor interface, PCB, power supply, antenna, fault detection, filtering, data storage and LoRaWAN payload.

6. Test the Finished Device

Evaluate temperature, humidity, dust loading, condensation, fan operation, enclosure influence and radio performance.

7. Conduct Collocation

Operate several devices beside a suitable reference instrument and document the comparison.

8. Perform a Site Pilot

Install sensors in representative indoor or outdoor locations and verify coverage, data quality, maintenance and platform alarms.

9. Prepare for Production

Finalize test fixtures, sensor verification, device credentials, firmware versioning, labels, packaging and traceability.

Information Required for a Quotation

Customers should provide:

1. Indoor, outdoor or industrial application
2. Required PM1.0, PM2.5 and PM10 outputs
3. Particle-count requirement
4. Expected concentration range
5. Accuracy and resolution targets
6. Temperature and humidity range
7. Possible dust or aerosol sources
8. Required measurement interval
9. Required reporting interval
10. Alarm and averaging rules
11. Raw or corrected-data requirements
12. Collocation and calibration requirements
13. Local display, buzzer or relay requirements
14. Battery, external power or solar preference
15. Installation and mounting method
16. Cleaning and maintenance conditions
17. Destination country and LoRaWAN frequency
18. Gateway and backhaul requirements
19. Network Server
20. Platform, BMS or API requirements
21. Prototype and estimated production quantities
22. Logo, enclosure and packaging requirements

Site plans, installation photographs and information about likely particle sources can improve sensor and enclosure selection.

Frequently Asked Questions

Is a LoRaWAN PM2.5 sensor the same as a regulatory air-quality station?

Not automatically. A compact optical sensor is normally used for supplemental or informational monitoring unless the complete instrument and measurement process meet the applicable regulatory requirements.

Can one sensor measure PM1.0, PM2.5 and PM10?

Many optical modules estimate several particulate fractions from one sensing chamber. The available outputs depend on the selected module and algorithm.

Does the sensor measure the chemical composition of particles?

No. A standard optical PM sensor estimates particle concentration or count from light scattering. It does not identify the chemical composition of each particle.

Can humidity affect PM readings?

Yes. High humidity and water associated with particles can change optical scattering. Humidity compensation and data-quality flags should be evaluated.

Why does the device need a fan?

Many particle modules use a fan to create controlled airflow through the optical chamber. The fan affects power consumption, noise, maintenance and service life.

Can the device operate from batteries?

Possibly. Feasibility depends on the sensor’s warm-up time, fan consumption, sampling duration and LoRaWAN reporting interval.

Can the device be installed outdoors?

An outdoor design is possible, but the enclosure must provide representative airflow while protecting the sensing chamber from rain, insects, condensation and direct contamination.

How often should a PM sensor be calibrated?

The verification interval depends on the sensing module, required data quality, environment, contamination and project requirements. Periodic comparison or collocation should be planned.

Can the same sensor monitor construction dust?

It can provide particulate trends and alarms, but the required PM range, weather protection and applicable construction-site monitoring rules must be confirmed.

Can the sensor replace a personal occupational dust monitor?

Not automatically. Area monitoring and personal exposure monitoring have different sampling, placement and compliance requirements.

What happens if the optical chamber becomes dirty?

Readings may drift or become unstable. The system should support maintenance records, sensor diagnostics and a defined cleaning or replacement procedure.

Does every sensor require a SIM card?

No. LoRaWAN end devices normally communicate with a shared gateway. The gateway may use a cellular SIM for backhaul where fixed internet is unavailable.

Can the device connect to an existing air-quality platform?

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

Is private-label manufacturing available?

PCB functions, sensor selection, firmware, enclosure, payload protocol, labels, packaging and platform branding can be evaluated for OEM or ODM production.

Conclusion

A LoRaWAN PM2.5 sensor enables distributed particulate monitoring across cities, schools, buildings, construction projects and industrial sites without installing a separate cellular connection at every measurement point.

Reliable results require more than an optical module and radio. Airflow, humidity, particle composition, sensor contamination, placement, calibration and data correction must all be considered.

For projects that require comparable measurements across many locations, testing several finished devices beside a suitable reference instrument is an essential part of product validation.

Shenzhen Jinshengchang Technology Co., Ltd. can evaluate OEM and ODM particulate-monitoring projects covering sensing hardware, PCB design, embedded firmware, LoRaWAN communication, gateways, air-quality platforms, APIs, prototypes and production preparation.

Request an OEM LoRaWAN PM2.5 Sensor Proposal

Send your monitoring application, required particulate outputs, installation environment, power preference, calibration requirements, destination country, expected quantity and platform interface for technical evaluation.