> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/blynk.console/devices.md).

# Devices

This is the main view, where you can manage all devices that belong to your organization, including the sub-organizations (if you have any).

<figure><img src="https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBFTVMf7L6S67HOuqVC%2Fuploads%2F0pFxxLpzfV1OCxFkQ9M0%2F10-devices%201.png?alt=media&amp;token=b7168f90-a2e7-455f-8d3e-6d7e5050b0ff" alt=""><figcaption></figcaption></figure>

## Predefined Filters

**My Devices** – List of devices that belong to your organization and the ones you have access to based on role and assigned permissions

**All** **Devices**– list of all devices that your organization has access to, including all devices in sub organizations.

## Quick search

You can search devices by almost any parameter.

<figure><img src="https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBFTVMf7L6S67HOuqVC%2Fuploads%2FESuVTDaHkHCI1DWwvsSJ%2F11-devices-search.gif?alt=media&amp;token=2241942e-a97f-4ca8-80f5-43a6c1585376" alt=""><figcaption></figcaption></figure>

Search can be performed by the following fields:

* Device Name
* ICCID
* Firmware Version
* Organization Name
* Device Model
* Template Name
* Device Owner Name
* Hotspot Name
* Contact Email, Street Address, Phone Number
* IMEI
* Auth Token
* Serial Number
* Device ID
* Tag
* other [Metadata](https://docs.blynk.io/en/blynk.console/templates/metadata.md) set in [Template](https://docs.blynk.io/en/concepts/device-template.md)

#### Search steps:

1. Start typing to perform a search. Search results will be segmented by sections will appear in the dropdown.
2. Click on result you need and you'll get all the Devices containing it in Table View
3. Use sorting and filter of the table columns to narrow down the search.

## Table view

{% hint style="info" %}
Keep scrolling down to load more devices.
{% endhint %}

**Navigation:**

* Click on **Device Name** – opens [Device View](https://docs.blynk.io/en/blynk.console/devices/device-profile.md)
* Click on **Device Owner** – opens Device Owner profile
* Click on **Organization Name** – opens device [Organization](https://docs.blynk.io/en/blynk.console/organizations.md)

## Map view

Here you can search and view Devices (depending on selected filter) by their locations.

<figure><img src="https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBFTVMf7L6S67HOuqVC%2Fuploads%2Fk3ZZ8T2mPtC4fh7YO680%2F12-devices-map%20view%201.png?alt=media&amp;token=e12580ce-380e-4102-8104-d75a4ed031aa" alt=""><figcaption></figcaption></figure>

Applied filtering option and Devices count are shown at top left.

Map supports mouse scroll zoom in/out.\
Hold left mouse button to move the map.

You'll see dots of two colors on the map:

* **Blue** – devices group with built-in devices counter. Click it to zoom in and view devices.
* **Orange** – device. Click it to view device name, template logo, actual connectivity status and latest in/accessibility date. Click on Device Name on map opens [Device View](https://docs.blynk.io/en/blynk.console/devices/device-profile.md).


---

# 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.blynk.io/en/blynk.console/devices.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.
