> 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/journey-to-getting-started-with-giot/6.-device-activation-and-set-its-properties.md).

# 6. Device Activation and set its properties

All devices are automatically onboarded to your Tenant profile upon purchase. Once received, ensure the new device is activated to complete the bootstrap process and connect it seamlessly to the platform.

### Activate the device LCT and LM Devices

{% hint style="success" %}
Activate Low Cost Tracker \
\
[**VIDEO INSTRUCTION**](/low-cost-tracker-full-device-guide-book/low-cost-tracker-handling-information-book/low-cost-tracker-activation-process.md)\
\
[https://app.gitbook.com/o/DKrl40rifuf7Bl8WIqXK/s/fEQ6KpTjmszWVWQqgcEa/\~/changes/145/low-cost-tracker-full-device-guide-book/low-cost-tracker-handling-information-book/low-cost-tracker-initial-setup](/low-cost-tracker-full-device-guide-book/low-cost-tracker-handling-information-book/low-cost-tracker-activation-process.md)
{% endhint %}

{% hint style="success" %}
Activate Level Meter\
[https://app.gitbook.com/o/DKrl40rifuf7Bl8WIqXK/s/fEQ6KpTjmszWVWQqgcEa/\~/changes/145/level-meter-full-device-guide-book/level-meter-handeling-information-book/level-meter-activation-procedure](/level-meter-full-device-guide-book/level-meter-handeling-information-book/level-meter-activation-procedure.md)
{% endhint %}

### How to identify Bootstrap state? And the device Properties.

{% hint style="success" %}
Device page introduction\
[https://app.gitbook.com/o/DKrl40rifuf7Bl8WIqXK/s/fEQ6KpTjmszWVWQqgcEa/\~/changes/145/platform-user-guide-book/device/device-page-introduction](/platform-user-guide-book/device/device-page-introduction.md)
{% endhint %}

### Device card shows - Not Activated - ?

<figure><img src="https://122097802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfEQ6KpTjmszWVWQqgcEa%2Fuploads%2Fpq0AG0MqqZblTC60qOSD%2Fdd.png?alt=media&amp;token=35f21fca-af7a-494e-84a4-f8caaa6e71ac" alt=""><figcaption><p>Device not Activated</p></figcaption></figure>

{% hint style="success" %}
Follow the link to lean more about devices Not Activated:\
[https://app.gitbook.com/o/DKrl40rifuf7Bl8WIqXK/s/fEQ6KpTjmszWVWQqgcEa/\~/changes/313/platform-user-guide-book/device/device-page-introduction](/platform-user-guide-book/device/device-page-introduction.md)
{% endhint %}

### From the PROPERTIES section you can also:

* Rename device.
* Add a device description.&#x20;
* Upload asset pictures.


---

# 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.g-iot.io/journey-to-getting-started-with-giot/6.-device-activation-and-set-its-properties.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.