> 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/add-edit-device.md).

# Add/Edit Device

This documentation outlines the steps required to add a new sensor to the system using the Sensor Dashboard Admin interface. The process includes scanning the device, configuring its settings, and activating it to begin transmitting data.

***

### 1. Accessing the Sensor Dashboard Admin

Navigate to the **Sensor Dashboard Admin**. This is the main interface for managing devices and configuring system settings for temperature monitoring.

***

### 2. Attaching a Device

#### a. Scanning the Device DevEUI

* Click the **QR** button beside the input field.
* Use the camera interface to scan the **QR code** of the sensor.
* This will auto-fill the **DevEUI** field with the unique identifier of the device.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2F9NqMq8vvBj0UoVMwugiM%2FIMG_0303.jpg?alt=media&amp;token=de2a8feb-2ad8-425b-b27a-8ff5f39ea03f" alt="" width="188"><figcaption></figcaption></figure>

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FruqUUGNAvJpIKl2tjCJy%2FScreenshot%202025-04-19%20at%2012.43.17%E2%80%AFpm.png?alt=media&amp;token=eeabc706-93b0-4713-8502-aa194e400037" alt="" width="244"><figcaption></figcaption></figure>

#### b. Labeling the Sensor

* Enter a **Label** in the provided field.
* This label typically represents the name of the fridge, freezer, or storage unit (e.g., "Walk-in Freezer – Main Kitchen").

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FgGIcuOReQO3I0fVXF1KY%2FScreenshot%202025-04-19%20at%2012.44.02%E2%80%AFpm.png?alt=media&amp;token=af238636-ae45-4de5-84f1-461b730dd8af" alt=""><figcaption></figcaption></figure>

#### c. Selecting the Profile

* The **Profile** is auto-selected based on the device (e.g., Dragino LHT65).

#### d. Choosing an Alert Template

* Select a predefined **Alert Template** from the dropdown:
  * Cold Storage
  * Cold Storage (Probe)
  * Cold Storage (Both)
  * Frozen Storage
  * Frozen Storage (Probe)
  * Frozen Storage (Both)

The selected template will apply relevant alert thresholds and compliance values.

#### e. Attaching the Device

* Click the green **Attach** button.
* The sensor is now linked to the dashboard.

***

### 3. Activating the Device

#### a. Physical Activation

* Press the sensor’s physical button **fully down** and **hold** it for a few seconds.
* When the LED begins **flashing green**, release the button.
* This action sends a **join request** to the gateway and server.

The device is now activated and will begin transmitting telemetry data.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FR7zU4IyILscedL8YKvgL%2FIMG_0302.jpg?alt=media&amp;token=abe2d423-f361-42f4-adb8-7ba5bd38efb7" alt="" width="375"><figcaption></figcaption></figure>

***

### 4. Tagging the Sensor

Tags categorize the type of storage:

* **Cold Storage**
* **Frozen Storage**
* **Hot Holding**

#### Importance of Tags:

Tags are used to generate graphs and differentiate sensor data by application type. Always assign the correct tag after attaching the device.

***

### 5. Sensor Card and Telemetry

Once activated:

* A **sensor card** appears on the dashboard.
* After a few minutes, the **telemetry data** begins displaying.
* The system auto-updates graphs and dashboards with incoming data.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FZErEXRYqn3VrjWqnnnDp%2FScreenshot%202025-04-18%20at%202.01.55%E2%80%AFpm.png?alt=media&amp;token=54837e29-41c5-44e5-8f69-58d6188923cd" alt=""><figcaption></figcaption></figure>

***

### 6. Sensor Provisioning Notes

* Each sensor comes with a **unique DevEUI**.
* Provisioned sensors have pre-uploaded configuration data including keys and profiles.
* Users only need to scan and assign the DevEUI during setup.

***

This process ensures each sensor is correctly assigned, activated, and ready to monitor temperature conditions in accordance with compliance requirements.


---

# 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/add-edit-device.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.