What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
LoRaWAN temperature and humidity sensors are best for low-power, periodic monitoring in places that are difficult or expensive to wire. They can run for years, reach remote buildings and outdoor assets, and send small readings through a gateway to dashboards and alerts. They are not broadband links, continuous-control systems, or automatically compliant cold-chain instruments.
The buying decision depends on five things: the exact measurement accuracy you need, the regional frequency model, gateway and network-server compatibility, realistic battery conditions, and installation quality. This guide covers the complete path from sensor selection to decoding and troubleshooting.
What a LoRaWAN temperature and humidity sensor actually is
A typical device combines a temperature element, relative-humidity element, microcontroller, LoRa radio, battery, and firmware. Some models also report battery status, store readings locally, or accept an external temperature probe.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsLoRa is the radio modulation. LoRaWAN is the networking protocol that defines device activation, security, classes, regional channels, data rates, and how gateways and servers cooperate. The LoRa Alliance describes it as a low-power wide-area, end-to-end system for battery devices: LoRaWAN for developers.
#1 Best Overall
- LoRaWAN Class A protocol
- Built-in 2400mAh battery for more than 10 year use
- Built-in Temperature & Humidity sensor
- Optional External Sensors
- 3200 set sensor record with time stamp
A standards-based LoRaWAN sensor normally follows this path:
Sensor ↓ LoRaWAN uplink Gateway ↓ Ethernet, Wi-Fi, or cellular backhaul Network server ↓ Application server, MQTT, API, or dashboard ↓ Alerts, reports, automation, and storage
The sensor does not normally connect directly to Wi-Fi or the internet. Multiple gateways can receive one uplink; the network server deduplicates those receptions and selects a gateway for downlinks.
LoRa versus LoRaWAN: choose the right architecture
Choose LoRaWAN when you need devices from multiple vendors, standard gateways, over-the-air activation, remote configuration, scalable deployments, or integrations with MQTT and APIs. A proprietary point-to-point LoRa product can make sense for two endpoints that you control completely, but it may not join The Things Stack, ChirpStack, or a public LoRaWAN network.
Confirm the words LoRaWAN, the supported protocol version, and the regional model before buying. “LoRa sensor” alone does not establish interoperability.
Where LoRaWAN is a good—and poor—fit
Strong use cases
- Remote buildings, sheds, basements, and equipment rooms.
- Greenhouses, farms, and irrigation or storage areas.
- Warehouses, facilities, and data centers.
- Refrigeration and cold storage when the sensor range, calibration, enclosure, and regulatory evidence fit the application.
- Large sites where Wi-Fi coverage or cabling is impractical.
- Periodic readings, threshold alarms, and deployments that can buffer data during outages.
Look elsewhere when
- You need high-frequency, high-bandwidth data or very low latency.
- Power and cabling are available and deterministic delivery is important.
- A safety-critical control loop cannot tolerate radio or gateway outages.
- A small home already has reliable Wi-Fi, Zigbee, Thread, or Bluetooth infrastructure.
- Each sensor must connect independently over a wide area and cellular subscription cost is acceptable.
LoRaWAN is low bandwidth: The Things Network describes European data rates of roughly 250 bit/s to 11 kbit/s depending on spreading factor (limitations and bandwidth). That is ample for temperature and humidity values, not for streaming.
Device classes and downlinks
Class A: the normal battery choice
After an uplink, a Class A device briefly opens receive windows, then sleeps. This minimizes energy use but means it is not continuously reachable. The Milesight EM300-TH and Dragino LHT65N are listed as Class A devices (EM300-TH profile; LHT65N specifications).
Rank #2
- LHT52 Indoor LoRaWAN Temperature & Humidity Sensor
- The Dragino LHT52 Indoor LoRaWAN Temperature & Humidity Sensor is a Long Range LoRaWAN Sensor
- It includes a built-in Temperature & Humidity Sensor and a USB Type-C sensor connector to external sensors such as an external temperature sensor
- LHT52 senses environment temperature and humidity and sends these values via long-range wireless LoRaWAN protocol
- Sensors, Temperature & Humidity
Class B and Class C
Class B adds scheduled receive opportunities and uses more energy. Class C keeps the receiver open most of the time and generally requires external power. For ordinary battery environmental monitoring, select Class A unless you have a documented need for faster downlinks.
Uplinks consume airtime; downlinks consume airtime and battery and are constrained by regional rules. Configuration commands or alarms therefore cannot be treated as free, instant messaging.
Measurement specifications that matter
Temperature
- Actual measurement range and accuracy across that range.
- Typical versus guaranteed accuracy, resolution, drift, and response time.
- Whether the element measures air, a surface, an enclosure, or a remote probe.
- Warm-up behavior and accuracy near the range limits.
Relative humidity
- RH range, accuracy at normal conditions and near saturation, hysteresis, and long-term drift.
- Whether operation is non-condensing and how the element recovers after saturation.
- Whether the stated accuracy is tied to a temperature and RH test condition.
A “0–100% RH” range does not mean headline accuracy over the whole range. For example, Milesight specifies the EM300-TH at typically ±3% RH from 10% to 90% RH at 25°C, but ±5% RH below 10% and above 90%; temperature is typically ±0.3°C from 0°C to 70°C and ±0.6°C from −30°C to 0°C (manufacturer specifications). Dragino lists the LHT65N at typically ±0.3°C and ±3% RH for its built-in sensors, with separate ranges and an optional external temperature sensor (Dragino specifications).
Accuracy is not calibration
Radio technology does not determine measurement accuracy. The element, thermal layout, airflow, enclosure, firmware compensation, condensation, and calibration do. Resolution is not accuracy, and repeatability is not absolute accuracy. A one-point calibration does not prove performance across the operating range.
For regulated or high-consequence work, specify traceable calibration, an interval, acceptance testing, alarm verification, and a documented replacement procedure. An IP rating or a temperature number alone is not evidence of pharmaceutical, food, medical, or laboratory compliance.
Regional frequency versions are a first-order buying decision
Common plans include US915 (United States and parts of the Americas), EU868 (much of Europe), AU915, AS923 variants, IN865, KR920, CN470, and RU864. Regional parameters define mandatory channels, data rates, and other radio behavior; they are not interchangeable (regional parameters).
Rank #3
- LHT65S-NE117 LoRaWAN Temperature & Humidity Sensor
- The Dragino LHT65S-NE117 Temperature & Humidity sensor is a Long Range LoRaWAN Sensor
- It includes a built-in Temperature & Humidity sensor and has an external sensor connector to connect to an external Temperature Sensor
- The LHT65S-NE117 allows users to send data and reach extremely long ranges
- LoRa / LoRaWAN, Sensors, Temperature & Humidity
Match the sensor, gateway, antenna approval, network-server plan, transmit-power limits, and channel or sub-band behavior to the deployment country. A US915 model is not a substitute for EU868 even if the enclosure is identical.
Activation, versions, certification, and payloads
Record the LoRaWAN version, OTAA or ABP support, exact firmware, DevEUI, JoinEUI/AppEUI, AppKey, payload format, and codec. Prefer OTAA for new deployments. Never publish or expose the AppKey.
The Things Network profile lists the EM300-TH as LoRaWAN 1.0.3, Class A, OTAA-capable, available in eight regional plans, and accompanied by a payload codec (device repository). That profile currently marks it as not LoRa Alliance certified, despite manufacturer claims of gateway and network-server compatibility. Interoperability and certification are separate questions.
Recommended Free Tools
Obtain the codec, example uplinks, FPort, units, scaling, signedness, byte order, battery flags, alarm fields, and firmware compatibility. Payloads may encode fixed-point values or several fields in bit fields; a wrong decoder can produce plausible but false numbers.
Battery life: read the test conditions
Battery life changes with reporting interval, spreading factor, data rate, transmit power, region, confirmed uplinks, downlinks, joins, retries, temperature, battery age and chemistry, signal quality, and firmware. Treat every “10-year” figure as a conditional estimate.
Milesight reports more than 10 years for an EM300-TH under an SF7, 10-minute-interval test at 25°C in EU868 and US915, but approximately 5.8 years at SF10 in EU868 and 4.2 years at SF10 in US915 (battery estimates). Dragino describes the LHT65N’s 2,400-mAh non-rechargeable battery as lasting up to 10 years while stating that actual life depends on transmission frequency (official store).
Rank #4
- D22-LB LoRaWAN Waterproof /Outdoor Temperature Sensor
- D22-LB LoRaWAN Waterproof /Outdoor Temperature SensorThe Dragino D22-LB is a LoRaWAN Temperature Sensor for Internet of Things solution
- D22-LB will convert the Temperature reading to LoRaWAN wireless data and send to IoT platform via LoRaWAN gateway
- The LoRa wireless technology used in D22-LB allows device to send data and reach extremely long ranges at low data-rates
- LoRa / LoRaWAN, Sensors, Temperature & Humidity
Compare battery claims only when the interval, spreading factor or data rate, region, temperature, and downlink assumptions are also stated.
Range is a site property, not a box specification
Line of sight, gateway height, walls, terrain, vegetation, antenna quality, orientation, interference, spreading factor, transmit power, and local limits determine coverage. Milesight advertises up to 10 km line of sight for the EM300-TH (product description); that is not an indoor or urban guarantee.
- Position the gateway where it will actually be installed.
- Place a sensor at its production location.
- Transmit at the planned interval and record RSSI, SNR, data rate, gateway reception, and packet loss.
- Repeat in representative weather and building conditions.
- Raise, relocate, or add a gateway if link margin is poor.
Local logging and outage recovery
Look for historical storage, retransmission, missing-packet detection, timestamp behavior, clock drift, and recovery after gateway or battery outages. The EM300-TH advertises storage for 2,800 historical records, retransmission, and retrieval (EM300-TH). The LHT65N advertises datalogging for periods without coverage (LHT65N store listing).
Buffering is not a guarantee of perfect data integrity. Applications must identify duplicates, late records, gaps, and clock anomalies.
Enclosure and installation
Compare IP rating, UV resistance, condensation behavior, operating temperature, mounting, probe options, battery access, local configuration, and tamper resistance. IP67 concerns ingress protection—not calibration, humidity accuracy, food contact, or regulatory qualification.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- Avoid direct sun unless solar-exposed conditions are the subject.
- Keep the sensor away from heaters, HVAC outlets, and warm electronics.
- Do not mount directly on a conductive exterior wall when air temperature is the target.
- Do not seal an air sensor in a cabinet unless cabinet conditions are intended.
- Keep the humidity element away from liquid water and condensation.
- Use a remote probe when the enclosure would distort the measurement or cannot enter the monitored space.
Alerts that do not flap
Separate sensor-side alarms from network-server and application rules. Implement warning and critical thresholds, minimum duration, hysteresis, recovery notifications, battery-low alarms, rate-of-change rules, and a communications-loss timeout. A single noisy sample should not page an operator. For high-consequence monitoring, do not rely on one wireless sensor as the sole safety mechanism.
Best Value
- LHT65S-E5 LoRaWAN Temperature, Humidity & Illuminance Sensor
- LHT65S-E5 Illuminance SensorThe Dragino LHT65S-E5 Temperature, Humidity & Illuminance sensor is a Long Range LoRaWAN Sensor
- It includes a built-in Temperature & Humidity sensor and has an external Illuminance sensor
- The LHT65S-E5 allows users to send data and reach extremely long ranges
- LoRa / LoRaWAN, Sensors, Temperature & Humidity
Verified product comparison
| Feature | Dragino LHT65N | Milesight EM300-TH |
|---|---|---|
| Best fit | Budget deployments, external temperature probe, local logging | Rugged facilities, agriculture, indoor/outdoor monitoring |
| Protocol/class | LoRaWAN, Class A | LoRaWAN, Class A |
| Temperature | Typically ±0.3°C; ranges vary by sensor option | −30°C to +70°C; typically ±0.3°C from 0–70°C and ±0.6°C from −30–0°C |
| Humidity | Typically ±3% RH; range and conditions must be checked | 0–100% RH; typically ±3% RH at 10–90% RH and 25°C, ±5% RH outside |
| Regional versions | US915, EU868, AU915, AS923, IN865, CN470, KR920, EU433 and others listed by manufacturer | Eight regional families listed by manufacturer and repository |
| Enclosure | Check the exact variant | IP67 |
| Battery | 2,400-mAh non-rechargeable; up to 10 years claimed conditionally | Replaceable 4,000-mAh ER18505 Li-SOCl₂; optional 8,000-mAh version |
| Local storage | Datalog feature | 2,800 historical records, retransmission and retrieval advertised |
| External probe | Optional temperature sensor | Integrated sensor; verify probe requirement before purchase |
| Certification | Not established here for regulated use | Manufacturer lists EN12830; verify scope for your application |
| Price | $43.00 observed on the official store; taxes and duties excluded | Public price not displayed on the official product page |
| Decoder | Obtain manufacturer documentation | Payload codec listed in The Things Network repository |
Official references: LHT65N specifications, LHT65N store, and EM300-TH specifications.
Onboarding path
- Confirm the device: record model, regional version, LoRaWAN version, class, join method, DevEUI, JoinEUI/AppEUI, AppKey, codec, and firmware.
- Confirm the gateway: match its band, network-server plan, backhaul, antenna, and coverage.
- Create the application and device: select the plan, enter identifiers and keys, choose the vendor profile or codec, power or reset the sensor, and confirm a join and first uplink.
- Validate readings: compare with a trusted reference at the same location after thermal equilibration, keeping the instruments physically separated.
- Set reporting: begin conservatively; shorter intervals increase energy use, airtime, collisions, and network load.
- Test failure recovery: gateway outage, network outage, out-of-coverage buffering, reboot, battery replacement, rejoin, downlink, decoder updates, missing-data alerts, and historical retrieval.
Troubleshooting
No join
Check the regional model, DevEUI, JoinEUI, AppKey, join mode, gateway plan, coverage, and whether the sensor is already joined elsewhere.
Values are nonsense
Check the firmware-specific codec, signed versus unsigned interpretation, byte order, scaling, units, FPort, and external-probe field identifiers.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Readings are biased
Investigate sunlight, HVAC airflow, wall conduction, warm enclosures, condensation, poor circulation, reference calibration, and warm-up time.
Battery drains quickly
Review interval, spreading factor, weak-signal retries, confirmed uplinks, downlinks, repeated joins, cold temperatures, battery condition, and firmware behavior.
Data gaps
Check gateway placement, backhaul, antenna, interference, server limits, battery, local logging, late packets, and whether another gateway is needed.
Humidity stays at 100% RH
It may indicate real saturation, condensation, contamination, drift, or a decoding error. Investigate the physical environment before applying a software correction.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Pre-purchase and deployment checklist
- Is the product explicitly LoRaWAN rather than proprietary LoRa?
- Is the regional frequency model correct for the country?
- Do gateway and network server support that plan and device version?
- Are accuracy, range, battery, and IP claims tied to stated conditions?
- Is the sensing element, probe, enclosure, and calibration suitable for the actual environment?
- Are codec, FPort, scaling, firmware, and example uplinks documented?
- Will local storage or retransmission cover gateway outages?
- Have gateway placement and radio performance been tested at the installation point?
- Are alert hysteresis, no-data alarms, battery alarms, and recovery notifications defined?
- Have gateway hardware, network service, dashboard, storage, installation, taxes, duties, and maintenance been included in total cost?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
