> 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-measurements.md).

# Sensor Measurements

### 1. Introduction

The **Recent Measurements Modal** offers a detailed view of sensor telemetry data for a specific unit (e.g. fridge, freezer, or chiller). This modal can be accessed directly from the dashboard and is essential for reviewing historical trends, identifying anomalies, and exporting data.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2F8pFTQj3ipI60wNAOSdF3%2FScreenshot%202025-04-18%20at%202.01.55%E2%80%AFpm.png?alt=media&amp;token=9b7beb87-191d-4f50-918d-c32a6bd3be23" alt=""><figcaption></figcaption></figure>

***

### 2. Accessing the Modal

From the **dashboard view**, each device block's **title is clickable**:

* **Hover over the unit title** (e.g., `FG4-HOR-C1 (166)`)
* Click to open the **Recent Measurements Modal** for that device

This action opens a pop-up with several powerful tools for analysis and visualization.

***

### 3. Modal Header Layout

#### 1. **Unit Name & ID**

* Shown prominently at the top-left
* Reflects the storage type and label (e.g., “Standing Chiller 4-Door”)

#### 2. **Storage Context Tag**

* Labelled as **Cold Storage**, **Frozen Storage**, **Wine Chiller**, etc.
* Helps users quickly understand the operational intent of the unit

#### 3. **Navigation Arrows**

* Top-right arrows allow quick toggling between adjacent devices **without closing the modal**

#### 4. **Image Button**

* Clicking the **camera icon** opens a visual reference screen
* Displays:
  * A photo of the **sensor installation**
  * A photo of the **unit’s external appearance**
* Assists with physical identification when addressing alarms or locating units

***

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FGK8OZKwmvx5iaIgu0IW5%2FScreenshot%202025-04-18%20at%202.03.42%E2%80%AFpm.png?alt=media&amp;token=5c6657c7-f166-4a9c-9940-974ad70ff0fa" alt=""><figcaption></figcaption></figure>

### 4. Visualization

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FuzEQ7nENV7oWHNqjD2D3%2FScreenshot%202025-04-18%20at%202.02.07%E2%80%AFpm.png?alt=media&amp;token=0e62a106-3dc0-4e95-919e-ef38573e98fd" alt=""><figcaption></figcaption></figure>

#### Chart Area Features:

* **Default Time Range**: Last 12–24 hours
* **X-axis**: Time (24-hour format)
* **Y-axis**: Temperature (°C)
* **Red line**: Indicates the configured **tolerance threshold** (e.g., 4°C or -18°C)
* **Average**: The calculated average for the selected data type is displayed below the chart (e.g., `avg 2.6°C`)

#### Tabs:

* **Ambient**: Shows environmental readings
* **Probe**: Shows product-mimicking readings (via vial)
* **All**: Overlays both types on a shared graph for comparison

> 📌 *Auto-update is triggered by device uplink.*

***

### 5. Telemetry Data Table

#### Column Breakdown:

| Column    | Description                                             |
| --------- | ------------------------------------------------------- |
| Date/Time | Timestamp in **local time zone** (e.g., Asia/Singapore) |
| Probe     | Product temperature (in vial of oil or water)           |
| Ambient   | Environmental temperature inside unit                   |

* **Out-of-spec values** appear **in red**
* Temperature limits (e.g., Probe < 5°C, Ambient < 4°C) are shown above columns

#### 🔺 Retransmission Indicators:

* Small **red triangle** next to a date: indicates a **retransmission**
  * Sensor held the data locally due to a temporary disconnect from the gateway
  * Common with send intervals every 20 minutes if real-time uplink is interrupted

#### 🔄 Pagination & Export:

* Footer contains **page navigation** controls
* **Download button (cloud icon)**: Exports displayed data into a **CSV file**
* **Refresh button (green)**: Manually refreshes the modal content

***

### 6. Time Filter Panel

Clicking **“Last 1 Day”** opens a date range selector:

* Options: Last 1 Day, 7 Days, 30 Days, 3 Months
* Manual selection available via calendar interface
* Affects both the graph and data table for synchronized review

***

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FZY4d94YqGrPLFMdCB3eZ%2FScreenshot%202025-04-18%20at%202.03.21%E2%80%AFpm.png?alt=media&amp;token=45d14604-2c5f-4036-839c-4fae197d9f5e" alt=""><figcaption></figcaption></figure>

### 7. Example Interpretation

For unit `CR1-BUT-FR1 (127)`:

* **Tolerance:** -18°C
* Any values above this (e.g., -14.76°C) will show in red
* Both **Probe** and **Ambient** are tracked
* The graph shows time-aligned trends, where spikes can indicate defrost cycles, door openings, or sensor drift

***

### 8. Use Cases

| Scenario                        | Feature                          |
| ------------------------------- | -------------------------------- |
| Investigate a high temp alarm   | View chart + table for spikes    |
| Identify physical unit in field | Use sensor/unit photos           |
| Validate past compliance        | Export CSV data                  |
| Review missed transmissions     | Look for red triangle indicators |

***

Let me know if you'd like this styled for publication, turned into PDF or HTML, or integrated with onboarding materials.


---

# 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-measurements.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.