> 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/sensor-dashboard.md).

# Sensor Dashboard

### 1. Admin Overview

The Sensor Dashboard Admin area is the central control panel for managing and configuring all temperature sensors and their associated workflows. This administrative interface provides a comprehensive set of tools across multiple tabs:

#### Primary Navigation Tabs

* **Devices**
* **Recipients**
* **Corrective Actions**
* **Calibration**
* **Compliance**

***

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FIsytLOPPtJALnlxQcFDN%2FScreenshot%202025-04-19%20at%2012.24.24%E2%80%AFpm.png?alt=media&amp;token=fb83001c-b77d-4307-9743-ba46d5886ee1" alt=""><figcaption></figcaption></figure>

### 2. Core Features

#### 1. **Device Attachment & Configuration**

Devices are added to the system using a unique DevEUI. Admins can input the DevEUI directly or use a QR scan feature. When attaching a device, the following fields are configured:

* **Label** (Custom Name)
* **Profile** (e.g., Dragino LHT65 - AS\_920\_923\_TTN\_AU)
* **Alert Template** selection, which defines threshold rules:
  * Cold Storage
  * Cold Storage (Probe)
  * Cold Storage (Both)
  * Frozen Storage
  * Frozen Storage (Probe)
  * Frozen Storage (Both)

Once configured, the device is attached to the dashboard.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2F0UZwWdQwxDxeycsINlxe%2FScreenshot%202025-04-19%20at%2012.30.31%E2%80%AFpm.png?alt=media&amp;token=122ead51-4fc4-4b93-827c-7d37f3db271d" alt=""><figcaption></figcaption></figure>

***

### 3. **Device Order**

Admins can reorder devices on the dashboard using the `Change Devices Order` function accessible from the three-dot menu. This helps prioritize frequently viewed units.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FbLcVPw0aG8LQTrJeY069%2FScreenshot%202025-04-19%20at%2012.24.55%E2%80%AFpm.png?alt=media&amp;token=dcfa6c95-d7a3-4ee3-a31d-41d173147fbb" alt="" width="272"><figcaption></figcaption></figure>

***

### 4. **Bulk Downlink**

The `Bulk Downlink` feature allows administrators to apply configuration updates across multiple sensors. It is primarily used to change the **send rate** for calibration workflows:

* Send rate options: 1 min, 5 min, 10 min, 20 min
* Configuration templates:
  * Enable Ext Probes (A202)
  * Enable Probes & Timestamp (A20A)

This setting is pushed during the next uplink cycle.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2F1rdLqn5cG0aav6pE5s0V%2FScreenshot%202025-04-19%20at%2012.25.26%E2%80%AFpm.png?alt=media&amp;token=176278a9-d4c0-44df-87ec-fc7424d7b1f8" alt=""><figcaption></figcaption></figure>

***

### 5. **Placeholder**

Placeholders allow admins to preconfigure dashboard layouts for upcoming installations:

* Define placeholder name, description, and tags.
* Helps teams plan sensor locations and configurations in advance.

Useful during large-scale setups when sensor installation is staged.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FcT55A9OShTgZAPRCzG7V%2FScreenshot%202025-04-19%20at%2012.25.41%E2%80%AFpm.png?alt=media&amp;token=860eca3f-41d1-410e-8462-a26e5e519588" alt="" width="375"><figcaption></figcaption></figure>

***

### 6. **Device Cards**

Each attached device displays:

* Status tags (e.g., Custom, Frozen Storage -18)
* DevEUI identifier
* Active configuration (e.g., TMP117 & timestamp)
* Icons for:
  * Check recent measurements
  * Aggregated time bucket measurements
  * Notifications
  * Go to TTS
  * Images when device attached
  * Transfer to another work area
  * Calibrate device
  * Update decoder

The admin can remove or edit device labels directly from the card view.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FrRo20aCKsjBTPtuMU36f%2FScreenshot%202025-04-19%20at%2012.37.18%E2%80%AFpm.png?alt=media&amp;token=4e6fd2cc-e75d-4972-bac4-fd2fb8ff4267" alt="" width="375"><figcaption></figcaption></figure>

***

### 7. Summary

The Sensor Dashboard Admin panel offers full control over:

* Device onboarding
* Bulk configuration
* Sensor sorting
* Placeholder setup
* Alert template assignment

Together, these tools streamline the operational and compliance workflows needed for large-scale wireless temperature monitoring systems in food safety environments.


---

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