> 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/device-management/maintenance-mode.md).

# Maintenance Mode

#### Overview

Maintenance Mode is a critical administrative feature within the temperature monitoring system, used to temporarily exclude a sensor from alerting and compliance reporting during periods of maintenance. This function ensures data integrity and avoids false positives when maintenance or servicing is being conducted on equipment such as fridges, freezers, or chillers.

***

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FxbX8gOvbO6rnrrQAq9Ax%2FScreenshot%202025-04-19%20at%2012.47.37%E2%80%AFpm.png?alt=media&amp;token=f1cbccf3-54c4-4042-8292-b6b08f56d0a4" alt="" width="375"><figcaption></figcaption></figure>

#### Purpose of Maintenance Mode

Maintenance Mode is typically used when:

* Preventive or scheduled maintenance is taking place.
* Emergency (reactive) maintenance is needed.
* Sensor-related hardware changes or site testing is being conducted.

When a device is placed in Maintenance Mode:

* It will no longer generate alerts, even if thresholds are exceeded.
* It will be excluded from compliance reports.
* It will continue to collect and log telemetry data, which remains available for review and audit purposes.

***

#### How to Enable Maintenance Mode

1. Access the Admin Dashboard.
2. Navigate to the device you wish to modify.
3. Open the device options and select Set Maintenance.
4. Confirm your selection in the modal by clicking “Change”.
5. The device will now be flagged with a visible status: “In Maintenance”.
   * This label is shown:
     * On the device card in the admin dashboard.
     * On the end-user dashboard, replacing the temperature chart with a “Device Under Maintenance” message.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2F52Rr1d2lnQhH2XGP79BQ%2FScreenshot%202025-04-19%20at%2012.47.29%E2%80%AFpm.png?alt=media&amp;token=b1cdc81f-26c2-4b15-9575-779f2288f75e" alt="" width="301"><figcaption></figcaption></figure>

***

#### Behavior of Sensors in Maintenance Mode

* Sensors in this mode still collect and transmit data.
* However, they are excluded from compliance metrics and do not trigger alarms.
* This prevents skewed compliance statistics and avoids unnecessary alerts during known periods of disruption.

***

#### Reverting from Maintenance Mode

* Manual Action Required: Once a sensor is in maintenance mode, it remains in that state indefinitely until manually restored to operational mode by an admin user.
* Admins must revisit the device card and toggle the sensor back to “In Operation” when maintenance is complete.

***

#### Integration with Corrective Actions

Maintenance Mode can also be triggered as part of the corrective action workflow:

* If an alert triggers a corrective action task, the user completing the action may be given the option to place the device into Maintenance Mode.
* This should be used with caution, as a sensor in Maintenance Mode will require manual reset to resume normal monitoring.

***

#### Visual Indicators

* A sensor in Maintenance Mode will display:
  * An orange pill tag labeled “In Maintenance” on its card.
  * A bar chart replacement on the user-facing dashboard indicating the device is under maintenance.
  * Status will be reflected in dashboards for visibility to both admins and users.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FTAaEcTitCVwOmxiGltlp%2FScreenshot%202025-04-19%20at%2012.47.54%E2%80%AFpm.png?alt=media&amp;token=df697fe7-9124-43d8-bf3c-23e080c68936" alt=""><figcaption></figcaption></figure>

***

#### Summary

| Feature            | Behavior                                         |
| ------------------ | ------------------------------------------------ |
| Alerts             | Disabled while in Maintenance                    |
| Compliance Reports | Sensor is excluded                               |
| Telemetry          | Continues uninterrupted                          |
| Visibility         | Clearly marked on both admin and user dashboards |
| Reset              | Manual reset by admin required                   |

***


---

# 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/device-management/maintenance-mode.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.