> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-properties.md).

# LCT - Properties

The **Properties** page provides detailed information about the selected device and includes several tools for monitoring, management, and diagnostics. Use the navigation bar at the top of the page to access device information, location, metrics, configuration history, images, remote commands, and event logs.

<figure><img src="/files/2fVk846xnwwQhcBAaq5H" alt=""><figcaption></figcaption></figure>

#### Accessing the Properties Page

To access the **Properties** page:

1. Select the desired device from the **Devices** list.
2. Click the device to open its **Device Dashboard**.
3. Select the **Properties** tab.
4. Use the top navigation bar to switch between the available sections, including **Details**, **Groups**, **Device Metrics**, **Location**, **History**, **Images**, **Commands**, and **ELOGs**.

***

#### Details

The **Details** tab displays the device's general information and configuration. From this page you can view:

* Device name
* Hardware configuration
* Device status
* Connectivity information
* Battery information
* Device description
* Time zone settings
* Location type *(*[*see the **Location Type** section for more information*](https://docs.g-iot.io/~/revisions/yXMWhWEtXTiMOSAvX4oJ/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-properties/page-1)*)*

***

#### Groups

The **Groups** tab lists all groups to which the device belongs, allowing you to quickly identify its organizational structure within the tenant.

***

#### Device Metrics

The **Device Metrics** tab provides a complete list of all metrics collected by the device. These metrics are used throughout the platform for dashboards, alarms, rules, and historical analysis.

***

#### Location

The **Location** tab displays the device's current position on an interactive map, allowing users to quickly verify its latest reported location.

***

#### History

The **History** tab allows users to review the complete configuration history of the device.

Each configuration version includes:

* **Bootstrapped** – Initial configuration created during device provisioning.
* **Received** – Configuration received and applied by the device.
* **Confirmed** – Configuration successfully applied and acknowledged by the device.

Each entry also includes the date and time when the event occurred.

To inspect a configuration version, click the **arrow** icon next to the desired entry. The **Device Configuration Details** panel opens, displaying all configuration parameters. Any values that changed compared to the previous version are highlighted in **yellow** for easy identification.

> <img src="/files/gWHvuFu4t1CvxxqjrfUZ" alt="" data-size="original"><img src="/files/kvSfnieQNw2P6R0yumo1" alt="" data-size="original">

***

#### Images

The **Images** tab allows users to upload a profile image for the device, making it easier to visually identify assets.

**Supported formats**

* JPG
* JPEG
* PNG

**Maximum file size**

* 1 MB

***

#### Commands

The **Commands** tab allows users to remotely execute supported maintenance commands on the device.

**Send Reboot Command**

The **Send Reboot Command** function remotely restarts the device.

Click **Send Reboot Command** to immediately reboot the device. The reboot resets the device's internal state and starts a new bootstrap process.

> <img src="/files/nFK0ps01Y6tbsZOEtWtX" alt="" data-size="original">

**Request Logs**

The **Request Logs** function retrieves diagnostic logs from the device. This feature is available **only for Low Cost Tracker Advanced devices**.

Select one of the available retrieval modes:

* **Tail** – Retrieves the most recent log entries.
* **From Index** – Retrieves log entries starting from a specified log entry ID.

When using **From Index**, specify:

* **First Log Entry ID** – Starting index for the log retrieval.
* **Number of Log Entries** – Number of log records to retrieve.

The **Last Log Index** displays the index of the most recent log entry available on the device.

Click **Request Logs** to submit the request. Once the device uploads the requested logs, they become available in the **ELOGs** tab.

***

#### ELOGs

The **ELOGs** tab allows users to manage and review diagnostic log requests received from the device.<br>

1. **Delete Log Request**\
   To remove a previously submitted log request, click the **Delete** (trash bin) icon next to the request.\
   In the confirmation dialog, select:

* **Delete** to permanently remove the request.&#x20;
* **Cancel** to keep the request.<br>

1. **View Logs:** \
   Click the **arrow** icon next to a log request to open the **Log Details** panel, where all retrieved log entries are displayed.<br>
2. **Export Logs**

Within the **Log Details** panel, click the **Export** icon to download the retrieved log entries as a **CSV** file for offline analysis.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-properties.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
