> 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/certifications.md).

# Certifications

**MFC Safe Pty Ltd**\
**Certificate of Hardware Compliance**

This is to certify that the following hardware has been reviewed and approved by MFC Safe Pty Ltd as meeting the operational, compliance, and technical standards required for deployment within wireless temperature monitoring systems across hospitality, food safety, and commercial refrigeration applications.

***

**Hardware Type:** Temperature & Humidity Sensor\
**Model:** Dragino LHT65S LoRaWAN Sensor\
**Manufacturer:** Dragino Technology Co., Ltd.

**Certified Capabilities:**

* CE and RoHS certified
* IP67 rated enclosure
* Integrated temperature & humidity sensor
* External probe support for cold chain / food safety use
* LoRaWAN 1.0.3 compatibility
* Ultra-low power consumption for multi-year battery life
* Operating range: -40°C to +80°C

This certificate confirms the Dragino LHT65S sensor as suitable for MFC Safe’s platform integrations and operational conditions.

***

**Certification Date:** 2 June 2025\
**Report Reference:** MFC-HW-AUDIT-2025-002

**Authorised By:**\
Morag Meikle\
Technology Director\
MFC Safe Pty Ltd\
Email: <technology@mfcsafe.com>

***

**End of Certificate**

***

| Category                     | Requirement / Check                                             | Purpose                                                           | Status                                              | Notes                                                                                                  |
| ---------------------------- | --------------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| Sensor Certification         | CE / FCC / RoHS                                                 | Ensure sensor legality and hazardous material safety              | CE / FCC / RoHS Certified                           | Dragino LHT65S CE Certificate: <https://www.dragino.com/downloads/index.php?dir=LHT65S/Certification/> |
| Ingress Protection           | IP65 Enclosure (splash resistant)                               | Verify device is suitable for cold storage and wet environments   | IP65 Rated (confirmed by Dragino)                   | IP65 rating confirmed in Dragino datasheet: <https://www.dragino.com/downloads/index.php?dir=LHT65S/>  |
| Battery Life Verification    | Battery longevity rated for >10 years under SF12                | Check internal battery performance against datasheet claims       | Estimated >10 years @ SF12 confirmed in datasheet   | Battery spec sheet and expected life: <https://www.dragino.com/downloads/index.php?dir=LHT65S/>        |
| Temperature Accuracy Testing | ±0.3°C accuracy in operating range (indoor/outdoor)             | Validate field accuracy vs calibration references                 | ±0.3°C (typical), range -40°C to 80°C documented    | Sensor accuracy confirmed on product datasheet and user manual                                         |
| Environmental Durability     | Performance in -40°C to +80°C tested                            | Ensure sensor casing and electronics hold in extreme temps        | Operating range -40°C to +80°C certified            | Performance tested in -40°C to +80°C (Dragino validation)                                              |
| Calibration Handling         | Probe sensor install & replace protocol                         | Document SOP for probe connection and field replacement           | Supports external probe; probe swappable            | External probe supported, replaceable with DS18B20 probe                                               |
| OTA Firmware Support         | Support for remote OTA updates & logs                           | Evaluate OTA update functionality and patching process            | Supports OTA firmware via UART (Dragino tools)      | OTA updates via UART (Dragino Tools): <https://www.dragino.com/downloads/index.php?dir=Tools/OTA/>     |
| Data Transmission Validation | End-to-end data transmission verified to gateway                | Confirm successful transmission of payload at expected intervals  | Payload confirmed via LoRaWAN; data format standard | LoRaWAN payload decoding supported, tested with The Things Stack                                       |
| LoRaWAN Compliance           | Device registered with LoRa Alliance or compatibility confirmed | Maintain compliance with network-level interoperability standards | LoRaWAN v1.0.3 Class A compliant (Dragino docs)     | LoRaWAN certification page: <https://lora-alliance.org/lorawan-certified-products/>                    |


---

# 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/certifications.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.
