> 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/pricing/archive-sensor-probe.md). # \[Archive] Sensor Probe Sensor Probe Add-On – Continuous Temperature Monitoring for Cook Chill, Hot Hold, and Immersed Applications
*** > $20 per unit (exclusive of sensor, in USD) #### Overview The **Sensor Probe Add-On** is a high-accuracy temperature probe designed to connect to the Dragino LHT65S or other compatible LoRaWAN sensors via **USB-C interface**. It provides **real-time, continuous temperature monitoring** in scenarios where ambient readings are insufficient, such as inside food, liquids, or enclosed thermal environments. This add-on enables precise tracking of **core product temperatures**, and is ideal for HACCP-critical applications where monitoring must be accurate, uninterrupted, and non-ambient. *** #### Technical Specifications * **Connector**: USB-C (C-USB) interface to sensor * **Cable Length**: 0.5 m (extendable up to 5 m) * **Probe Type**: Food-grade stainless steel * **Measurement Range**: −55 °C to +125 °C * **Accuracy**: ±0.5 °C (from −50 °C to +100 °C) * **Cable Rating**: Waterproof, heat-resistant insulation (suitable for immersion) * **Mounting**: Direct probe insertion, clip holders optional *** #### Use Cases **Cook Chill Processes** In food production environments using blast chillers, the probe can be directly inserted into food portions to verify rapid chilling from cooked temperatures to below 5 °C within safe timeframes. This enables full traceability for compliance and audit records. **Hot Holding / Bain-Marie Monitoring** The probe can be submerged in a hot water bath within bain-marie units to ensure food is maintained above 60 °C, avoiding conditions that allow bacterial growth. Supports continuous validation of hot holding temperatures without manual probing. **Immersion Monitoring (Soups, Gravies, Sauces)** The sensor probe can be inserted directly into hot or cold liquid products to continuously monitor temperature over time. Ideal for: * Gravies and soups held in dispensers * Stews in reheating wells * Hot-fill applications in central kitchens **Pre-Delivery Validation / Transport Readiness** Use the probe to monitor products just before dispatch, ensuring they meet holding or cooling criteria. Sensors can log data during pre-staging before final delivery, supporting cold-chain assurance. *** #### Integration & Functionality * Plug-and-play with LHT65S using C-USB port * Probe readings are automatically used in place of internal ambient sensor * Compatible with DIG dashboard, showing real-time values and alert thresholds * Supports configurable send intervals and alert logic (e.g., above 60 °C for hot hold, below 5 °C for chill) *** #### Benefits * **Accurate core readings** for product safety * **Non-ambient validation** for regulatory compliance (HACCP, ISO 22000) * **No manual probing** needed—automated logs reduce labor * **Waterproof and immersion-ready** for liquid and semi-solid applications * **Secure connection** with high-quality USB-C connector *** Add the **Sensor Probe Add-On** to your temperature monitoring strategy and gain continuous visibility into critical food safety thresholds—whether you're chilling, holding, or heating. Let your data tell the full story, from core to compliance. --- # 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/pricing/archive-sensor-probe.md?ask=&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.