> 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/attach-images.md).
# Attach Images
### Overview
The Sensor Images feature is designed to enhance traceability and clarity in identifying the placement of temperature monitoring sensors within food storage units such as cold rooms, under-bench chillers, or freezers. This is particularly helpful in environments where many storage units are deployed, ensuring quick identification for both engineering and operational teams.
### Purpose
The inclusion of images in the system supports:
* **Accurate sensor identification**
* **Ease of access for support or audit purposes**
* **Visual confirmation for maintenance and troubleshooting**
* **Operational efficiency in sites with complex or numerous cold storage setups**
### How It Works
From the **Admin Dashboard**, users can upload two key images associated with each sensor:
1. **Inside Unit Image**
* A clear photo showing where the sensor has been installed within the cold storage unit.
* This helps technicians and users understand the exact physical location and orientation of the sensor.
2. **External Unit Image**
* A photo of the unit itself from the outside.
* Should clearly display identifying features such as:
* Unit label or name
* Brand or model (if visible)
* Any signage or unique identifiers (e.g., zone name, floor label)
* This provides context for identifying the correct storage unit quickly and accurately.
### Adding Images
To upload these images:
1. Navigate to the **Sensor Admin Area**.
2. Select the sensor you wish to update.
3. Click on the image placeholder or existing image to **change or upload** a new photo.
4. Upload both the **interior sensor image** and the **external unit image**.
### End User Visibility
Once added, the uploaded images are also viewable by end users from their respective dashboards. This allows kitchen staff, hygiene officers, or auditors to quickly identify sensor locations without ambiguity.
### Benefits
* **Reduces confusion** in sensor-to-unit mapping
* **Improves response time** in maintenance and corrective actions
* **Supports compliance** with documentation and traceability requirements
* **Simplifies onboarding** for new team members
### Best Practices
* Ensure both images are clear and not obstructed.
* Use consistent angles and framing across sites for uniformity.
* Re-upload photos if sensors are relocated.
The Sensor Images feature, while simple, plays a vital role in making the temperature monitoring system user-friendly and audit-ready.
---
# 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/attach-images.md?ask=&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.
