> 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/admin/alerts-and-actions/alerts.md).
# Alerts
### Overview
The Alerts Configuration module enables proactive temperature monitoring by sending automated alerts when a device records values outside predefined limits. These settings are essential for ensuring food safety compliance, protecting stock integrity, and avoiding critical failures in cold or hot storage environments.
***
### Purpose of Alerts
Alerts are used to:
* Notify users when a temperature threshold is breached (too high or too low).
* Differentiate between regulatory compliance values and operational triggers.
* Minimize false alarms using configurable delay settings.
* Support food safety programs by maintaining critical control points.
***
### Accessing Alerts Configuration
1. Navigate to the Devices tab in the Sensor Dashboard Admin.
2. On the desired sensor’s card, click the Alerts option to open the Alerts Modal.
3. From this panel, configure both preset templates or custom values.
***
### Alert Templates
Templates help apply quick, consistent rules based on the type of sensor usage. You can select from the following:
| Template Name | Description |
| ---------------------- | ---------------------------------------------------- |
| Cold Storage | Standard upper limit for coolers (ambient or probe). |
| Cold Storage (Probe) | Alerts only from the probe sensor. |
| Cold Storage (Both) | Both ambient and probe must exceed threshold. |
| Frozen Storage | For freezers; typically triggers at -15°C or -18°C. |
| Frozen Storage (Probe) | Monitors only probe data for frozen zones. |
| Frozen Storage (Both) | Alerts if both probe and ambient fail. |
| Custom | Allows full manual configuration. |
***
### Manual Configuration Fields
Each sensor supports individual configuration for:
* Probe Sensor (e.g., TMP117)
* Ambient Sensor (e.g., SHT)
The fields are divided into Lower Limit and Upper Limit sections:
| Field | Description |
| ---------- | ---------------------------------------------------------------- |
| Threshold | Temperature value to trigger alert (e.g., 8°C, -5°C). |
| Delay | Duration for which threshold must be breached to trigger alert. |
| Compliance | The regulatory value used for audit purposes (e.g., 5°C, -18°C). |
#### Delay Options:
* Immediately
* 5 minutes
* 10 minutes
* 30 minutes
* 1 hour
* 2 hours (recommended for cold storage to avoid service-related fluctuations)
***
### Alert Logic
#### Upper Limit
Used primarily for cold or frozen storage.
Example: If 8°C is the threshold, and 5°C is the compliance limit, alerts begin when temperature exceeds 8°C continuously for the set delay (e.g., 2 hours).
#### Lower Limit
Used for hot holding or warm areas.
Example: Trigger an alert if temperature drops below 65°C (e.g., for bain-marie units).
Note: If no values are entered in either limit section, no alerts will be triggered.
***
### Compliance vs. Alerts
| Type | Purpose | Example |
| ---------------- | ----------------------------------------- | ------- |
| Alert Threshold | Triggers operational alerts | 8°C |
| Compliance Limit | Used in audit logs and compliance records | 5°C |
* Compliance values are stored and reported for food safety audits.
* Alert thresholds may be slightly higher or lower to give staff time to respond before non-compliance occurs.
***
### Saving Alert Settings
Once all settings have been configured:
* Click the green Save Alerts button.
* Your thresholds, delays, and compliance values are now applied to that sensor.
***
### Corrective Actions Triggered by Alerts
When an alert is triggered, the system will automatically generate a Corrective Action task — provided that the corrective actions module has been configured. This ensures a closed-loop response system, where temperature breaches are not only recorded but also immediately acted upon by staff.
* The alert serves as the trigger.
* The system generates a predefined corrective action form or task.
* Staff must complete this action to resolve or acknowledge the issue.
This integration supports HACCP compliance and improves traceability and accountability during audits.
***
### Best Practices
* Use alert templates to standardize configuration across similar units.
* Always assign a compliance value even if alerts are not required.
* For busy environments (e.g., kitchens), apply a 1–2 hour delay to reduce false positives.
* Use the “Both” sensor configurations (ambient and probe) for critical control zones requiring higher accuracy.
***
---
# 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/admin/alerts-and-actions/alerts.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.
