> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/device-finder/features/device-status.md).

# Device Status

Device Status provides users a clear view of each device's status, ensuring they can easily identify and understand it at a glance. These statuses are organized under distinct tabs as follows:

* **Powered Off:** The device is completely shut down and non-operational.
* **Idle/Off Cradle:** The device is not in use, has been removed from its charging cradle, and no user is logged in.
* **Missing:** Denotes devices unaccounted for or not found as expected. This status can also be manually set in the Dashboard dropdown.
* **Not Reporting:** Indicates that the device has stopped sending data, exceeding the threshold defined in the configuration file (missingThresholdInHours in launcher.json).
* **Cradled:** The device is docked in its designated charging station.
* **In Use:** Signifies a device that is actively being used by a logged-in user while not cradled.

<br>


---

# 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.bluefletch.com/bluefletch-enterprise/product-guides/device-finder/features/device-status.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.