> 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/end-user/core-functions/sensor-dashboard.md).

# Sensor Dashboard

### 1. Overview

The **Temperature Sensor Dashboard** provides real-time visibility into the status and readings of connected refrigeration units across different operational zones. This guide covers the layout, interaction methods, sensor data interpretation, and auxiliary features available through the dashboard interface.

***

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FLvyIog469jtVRKQmgXVO%2FScreenshot%202025-04-18%20at%201.29.17%E2%80%AFpm.png?alt=media&amp;token=f8e0dcdf-6edd-4af5-9570-9cc46f460ec3" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FaQ0kJRD6o8ffH6NQrHow%2FScreenshot%202025-08-15%20at%203.43.27%E2%80%AFPM.png?alt=media&amp;token=7e8c27fb-44dc-4579-bc17-8aa1240cf345" alt=""><figcaption></figcaption></figure>

### 2. Dashboard Layout

#### &#x20;

#### Tabs Across the Top

The dashboard includes multiple navigation tabs:

* **Devices** *(default tab)*: Displays a grid of temperature sensor blocks.
* **Corrective Actions**: Shows any recorded actions taken in response to out-of-spec temperatures.
* **Calibration**: Provides access to historical calibration data for each sensor.
* **Compliance**: Displays compliance records related to temperature monitoring.

These tabs are **consistent across all operational dashboards**, allowing users to switch views while staying within the context of a particular site, level, or kitchen zone.

***

### 3. Sensor Display

Each temperature sensor is displayed as an individual **block** containing:

#### 1. **Sensor & Unit Identification**

* **Unit Name**: Shown in bold at the top (e.g. `FG2-HOR-F1 (162)`).
* **Sensor ID**: A unique identifier string directly below the name (e.g. `A8404151545ACAF1`).

> ✅ **Interactive**: Clicking on the **unit name** opens a modal with detailed readings and historical data.

***

### 4. Visualization

Each sensor block features one or two vertical bars representing real-time temperature values.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FrFpK3ATtmalScYWKTaks%2FScreenshot%202025-04-18%20at%201.29.57%E2%80%AFpm.png?alt=media&amp;token=8bdd7697-7e29-4b4d-aefd-584c34a3b282" alt=""><figcaption></figcaption></figure>

#### Bar Types:

* **Ambient Temperature**: Blue (normal), represents environmental/display temperature.
* **Probe Temperature**: Green (normal) or Red (if out of range), represents internal/product temperature (e.g., in a vial of water or oil).

> ❗ **Red bars** indicate the temperature has breached the defined **tolerance threshold** (too high or too low).

#### Bar Details:

* **Live Temperature Reading**: Value is shown within each bar (e.g. `-18.44`).
* **Y-Axis**: Adjusts to suit temperature range (e.g., -20 to 15°C).
* **Average Temperature**: Shown below each bar (e.g., `avg 2.8`).

***

### 5. Status & Timing

At the bottom of each sensor block:

* **Last Update**: Indicates when the most recent telemetry value was received (e.g., `last update 3 minutes ago`).
* **Maintenance Mode**: If a sensor is under maintenance, a message will be shown, but it remains clickable for review.

***

### 6. Temperature Types

| Type    | Color | Description                                                                   |
| ------- | ----- | ----------------------------------------------------------------------------- |
| Ambient | Blue  | Air/display temp of the unit's environment                                    |
| Probe   | Green | Product-equivalent temp inside a vial (oil/water), simulates core temperature |

***

### 7. Operational Groupings

Sensor dashboards are grouped by **logical operational zones**, such as:

* Kitchen areas
* Refrigeration banks
* Floors or departments

This allows easy navigation across all monitored devices in a facility or building.

***

### 8. User Interactions

| Action                        | Result                                         |
| ----------------------------- | ---------------------------------------------- |
| **Click unit title**          | Opens latest sensor chart and historical modal |
| **Hover over title**          | Highlights it's clickable                      |
| **Red bar**                   | Indicates temperature is out of tolerance      |
| **Blue/Green bar**            | Indicates normal temperature within limits     |
| **"Under Maintenance" label** | Sensor still accessible but flagged for review |

***

### 9. Example Use Case

If a unit like `FG2-HOR-F1 (162)` is showing:

* Ambient: `-19.85°C (avg -20.3)`
* Probe: `-14.92°C (avg -15.9)`

And both bars are **not red**, the system is functioning within frozen storage expectations. If one were to turn red, a corrective action would be needed.


---

# 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/end-user/core-functions/sensor-dashboard.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.