> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/foodcore-sensors/technical/hardware-specs/dragino-sensors/specifications.md).

# Specifications

### 📦 Product Overview

The **Dragino LHT65S** is a long-range LoRaWAN sensor designed for monitoring temperature and humidity. It features:​

* A built-in temperature and humidity sensor.
* An external sensor connector for additional measurements.
* Compatibility with LoRaWAN v1.0.3 Class A protocol.
* A built-in 2400mAh non-rechargeable battery, supporting up to 10 years of operation (depending on usage).​

Ideal applications include smart agriculture, cold chain monitoring, building automation, and smart cities. ​

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FzfcWWjcY2n3ObejVONW7%2Fdownload%20(18).jpeg?alt=media&amp;token=0de0893e-d20a-4660-9997-41118ba6aec3" alt=""><figcaption></figcaption></figure>

***

### 📐 Technical Specifications

#### Built-in Temperature Sensor

* **Resolution**: 0.01 °C
* **Accuracy**: ±0.3 °C
* **Long-term Drift**: < 0.02 °C/year
* **Operating Range**: -40 to 80 °C​

#### Built-in Humidity Sensor

* **Resolution**: 0.04 %RH
* **Accuracy**: ±3 %RH
* **Long-term Drift**: < 0.02 %RH/year
* **Operating Range**: 0 to 96 %RH

#### External Temperature Sensor (E1)

* **Resolution**: 0.0625 °C
* **Accuracy**:
  * ±0.5 °C from -10 °C to +85 °C
  * ±2 °C from -55 °C to +125 °C
* **Operating Range**: -55 to 125 °C

***

### 🔋 Power Consumption

* **Idle Mode**:
  * Without external sensor: 3 µA
  * With E1 sensor: 4 µA
* **Transmit Mode**: Maximum 130 mA

***

### 📡 LoRaWAN Communication

* **Protocol**: LoRaWAN v1.0.3 Class A
* **Frequency Bands**: CN470, EU433, KR920, US915, EU868, AS923, AU915
* **Join Method**: Over-The-Air Activation (OTAA)
* **Uplink Interval**: Default every 20 minutes (configurable)​

***

### 🛠️ Configuration & Activation

* **Activation**:
  * Press the ACT button for more than 3 seconds to activate the device and join the LoRaWAN network.
* **Deactivation**:
  * Quickly press the ACT button 5 times to deactivate and enter deep sleep mode.
* **Configuration**:
  * Supports AT commands for parameter changes.
  * Remote configuration via LoRaWAN downlink.
  * Firmware upgradable via the program port.

***

### 📊 Data Payload & Decoding

* **Uplink Payload Structure** (FPort=2):

  | Bytes | Description             |
  | ----- | ----------------------- |
  | 0-1   | Battery Voltage         |
  | 2-3   | Built-in Temperature    |
  | 4-5   | Built-in Humidity       |
  | 6     | External Sensor Type ID |
  | 7-10  | External Sensor Value   |
* **Decoding**:
  * Dragino provides payload decoders compatible with platforms like The Things Network (TTN).
  * Decoders can be downloaded from Dragino's GitHub repository:
    * [Dragino Payload Decoders](https://github.com/dragino/dragino-end-node-decoder)

***

### 📄 Documentation & Resources

* **Product Page**: [Dragino LHT65S Product Page](https://www.dragino.com/products/temperature-humidity-sensor/item/256-lht65s.html)
* **User Manual**: [LHT65S User Manual](https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65S_LoRaWAN_TemperatureHumidity_Sensor_Manual/)
* **Payload Decoders**: [Dragino GitHub - Payload Decoders](https://github.com/dragino/dragino-end-node-decoder)​


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didge.io/home/foodcore-sensors/technical/hardware-specs/dragino-sensors/specifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.