> 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/door-sensor.md). # Door Sensor Wireless Door State Sensor Integrated with the MFC Temperature Monitoring System > $250 AUS per unit
*** ### Overview The Dragino LoRaWAN Door Sensor provides reliable detection of door open/close states in cold storage and food safety environments. Designed for seamless integration with the MFC Safe platform, this sensor is ideal for identifying one of the most common root causes of temperature non-compliance—doors being left open. It supports commercial kitchens, cold rooms, walk-in freezers, and food storage areas by enabling real-time visibility and corrective response when temperature control is compromised. *** ### Key Features * Real-Time Door State Reporting Continuously monitors and reports the door’s current status (open or closed) using LoRaWAN communication. * Customizable Alert Delay Includes configurable time delay to avoid unnecessary alerts for quick entries. Alerts only trigger when a door remains open beyond the set duration. * LoRaWAN-Based Connectivity Low-power, long-range wireless protocol ideal for commercial environments with limited infrastructure. Pairs with MFC’s existing LoRaWAN gateways. * Fully Integrated with DIGDE Works directly with the MFC DIGDE platform, allowing centralized visibility across door sensors, temperature sensors, audit logs, and alerts. *** ### Integration in the MFC Ecosystem Once installed on a refrigeration unit, the sensor delivers live door status updates to the DIGDE dashboard. This allows staff and management to: * Identify if prolonged door openings coincide with abnormal temperature events. * Respond quickly to events that might lead to spoilage or compliance breaches. * Review door open/close logs in performance reports or audits. * Link door events to corrective action logs and assign follow-ups. *** ### Use Cases * Walk-in refrigerators and freezers * Commercial kitchen cold rooms * Beverage display fridges in public-facing areas * Banquet and event storage areas * Back-of-house food prep and receiving zones *** ### Benefits * Enables early detection of temperature risks caused by open doors * Supports energy efficiency by ensuring doors are not left ajar * Enhances food safety compliance and traceability * Provides operational oversight across multiple zones or branches * Reduces manual checks and improves accountability *** ### Pricing * $170 USD per unit Volume discounts and installation services available upon request. Includes integration support with the DIGDE platform. --- # 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/door-sensor.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.