> 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/templates/info.md).

# Info

This page keeps general info about the device such as:

![](https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MBFTVMf7L6S67HOuqVC%2F-MSd10OQfVizpqmVUVYY%2F-MSgkaz3Hwx99DrcPW3L%2Fprod_info.PNG?alt=media\&token=96b2f631-a2f3-4eba-9c1f-1ab1a2966cdb)

* **Name** – unique Template name that will be used during Device check and connection plus it's a default Device name (paste it to Sketches "#define BOARD\_NAME" string replacing the "Template Name"). Make it readable and understandable. Use only letters, digits, and spaces. 100 characters limit.
* **Hardware**– dropdown list of supported Boards. Start typing the name of board that will be used in your product and choose correct one from search results or select it manually from the list.

![](https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MBFTVMf7L6S67HOuqVC%2F-MSd10OQfVizpqmVUVYY%2F-MSglwP83swh5ur3Fqtq%2FHardware.png?alt=media\&token=035b0044-40f4-423b-a65f-2110ea885635)

* **Connection Type** – dropdown list of various possible board connections. Be sure to select correct one that is used by your product's Board.

![](https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MBFTVMf7L6S67HOuqVC%2F-MSd10OQfVizpqmVUVYY%2F-MSgmT2m75ITpmvfnji6%2Fconnection%20type.png?alt=media\&token=91aa2e0a-9409-4715-bfd6-0be580cc879e)

* [Offline Ignore Period](https://docs.blynk.io/en/blynk.console/templates/info/offline-ignore-period.md)– optional setting. 00 hrs 00 min 00 sec format.

![](https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MBFTVMf7L6S67HOuqVC%2F-MSd10OQfVizpqmVUVYY%2F-MSgn5reQdgOpQZzFozk%2Foffline_ignore_period.png?alt=media\&token=ab427a52-f171-4b8c-bc14-70a479d8497b)

* [Manufacturer](https://docs.blynk.io/en/blynk.console/templates/info/manufacturer.md)– a name of a Template maker that will be used during Device check and connection

  It's an Organization name often.
* [Template ID](https://docs.blynk.io/en/blynk.console/templates/info/template-ids.md) – a unique ID that will be automatically generated by server once a Template is created. It's used for recognition of in/correct Devices by Blynk.Apps during [Device Provision](https://docs.blynk.io/en/blynk.apps/device-management/add-new-device.md). Copy and paste it to your Device's Firmware `define BOARD_TEMPLATE_ID` value.
* [Categories ](https://docs.blynk.io/en/blynk.console/templates/info/categories.md)– dropdown list of various devices groups that are used by Voice Assistants.

![](https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MBFTVMf7L6S67HOuqVC%2F-MSd10OQfVizpqmVUVYY%2F-MSgnfRwc9aSL-h9ds_C%2FCategories.png?alt=media\&token=baa0922d-1a1f-49e4-a6ed-3ad0bc80cef8)

* [Hotspot Prefix](https://docs.blynk.io/en/blynk.console/templates/info/hotspot-prefix.md) – Device's SSID that will be used during the Provision.
* Description – brief (up to 200 characters) description of a product's purpose and functionality.
* Logo – add image/logo of your Product that will be displayed in Templates List tile. Upload from computer or drag-n-drop .png or .jpg, min 500x500px


---

# 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/templates/info.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.
