> 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/sensors-and-probes-pricing/hand-held-probe.md). # Hand Held Probe Hand-held LoRaWAN Probe – Wireless Spot & Continuous Temperature Monitoring for Food Safety Operations ### Overview The **Handheld LoRaWAN Probe** is a versatile, wireless temperature monitoring tool designed for both **spot checks** and **continuous temperature tracking**. Built for real-time HACCP compliance, it combines portability with robust connectivity through existing LoRa infrastructure. With an integrated display and **action button** for manual spot checks, the probe also supports **automated send intervals** (e.g., every 5 minutes), enabling it to operate as a continuous monitoring device in cook chill or hot holding processes. Purchase > $250 AUS per unit
*** #### Key Features * **Dual Functionality**: * **Spot checks** with instant reading and one-touch logging * **Continuous monitoring** for cook chill or hold scenarios * **LoRaWAN Connectivity**: * Sends data wirelessly to the same gateways and infrastructure as existing MFC/Didge temperature sensors * No additional hardware required * **Digital Display**: * On-screen real-time temperature for instant verification * **Action Button**: * Captures manual readings with a single press * **Compact & Durable**: * Designed for field use in kitchen and logistics environments *** #### Technical Specifications * **Sensor Type**: Food-grade stainless steel core temperature probe * **Temperature Range**: –55 °C to +125 °C * **Accuracy**: ±0.3 °C * **Display**: Backlit LCD screen * **Transmission**: LoRaWAN (Class A) * **Send Rate**: Configurable (default every 5 minutes) * **Button Function**: Manual spot check reading & log trigger * **Power Supply**: Long-life internal battery (2+ years under standard use) *** #### System Integration * Connects seamlessly with the **Didge platform** and DIG dashboards * Supports: * Real-time alerts * Audit trails * HACCP form population * API export to third-party platforms * No gateway or infrastructure changes required *** #### Use Cases * **Cook Chill Monitoring**: Insert into food inside a blast chiller to track cooling compliance * **Hot Holding**: Verify safe holding temperatures above 60 °C * **Cold Holding**: Ensure core food temps remain below 5 °C * **Incoming Goods Checks**: Verify supplier delivery temperatures on arrival * **QA & Training**: Use during shift checks, food handling training, or equipment validation *** #### Benefits * **Mobile**: Move easily between prep, delivery, and service areas * **Reliable**: Temperature displayed instantly on screen and logged to cloud * **Flexible**: Supports both one-time and ongoing temperature tracking * **Infrastructure-Friendly**: Uses your existing LoRaWAN network * **Compliant**: Supports audit-ready digital records for HACCP and ISO standards *** **Add the Handheld LoRaWAN Probe to your food safety toolkit** to combine convenience, visibility, and compliance in one smart handheld device. --- # 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/sensors-and-probes-pricing/hand-held-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.