> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/assets/qr-codes-generieren.md).

# Generate QR codes

You can generate a separate QR code for each asset.

Users can scan the QR code with their smartphone and then are taken via a link directly to the corresponding asset in eliona.

Requirements:

* Users have an eliona account and valid login credentials
* Users have sufficient permissions to access the asset

{% hint style="warning" %}
**Warning!**\
QR codes are not intended for use by the general public and building users.\
Only eliona users should be able to see and scan QR codes
{% endhint %}

{% hint style="info" %}
QR codes are not to be confused with [-> AR codes](/collection/english-v14/documentation/weitere-funktionen/augmented-reality.md)
{% endhint %}

{% hint style="success" %}
Generating QR codes costs no Infravolts.
{% endhint %}

## Use case

#### Give specialists quick access to information

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/5tDmfXvcTjERJAzgJv8K/88ACBC5D-0CB6-4F47-9804-A5879006D0AE.png" alt=""><figcaption><p>Fig. 1 – A printed QR code in a control cabinet</p></figcaption></figure>

1. You generate a QR code for an asset
2. The QR code is saved as an image file (.png) on your computer
3. You print out the code
4. You attach the printed QR code to a device that is present as an asset in eliona
5. A specialist performing maintenance work on the device scans the printed QR code with a smartphone
6. The specialist is taken to the "Asset Details" of the corresponding asset
7. The specialist can access relevant information, e.g. open tickets, attached documents, links, etc.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/iz5znq5y8dTbXkasKfXf/174BD8AC-9EFB-4F76-B637-C43B957A8C99.png" alt="" width="375"><figcaption><p>Fig. 2 – The asset details on a smartphone.<br>The asset details are opened after the QR code has been scanned</p></figcaption></figure>

## Generate a QR code

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/kpxjVZexMFYkX7bQAskn/91EDCE4F-7578-454F-9E99-A2657F87A989.png" alt=""><figcaption></figcaption></figure></div>

1. Open the [-> Asset Details](/collection/english-v14/documentation/assets/ein-asset-konfigurieren.md) of the asset for which you want to configure a QR code
2. Make sure that you are in the tab **General \[A]** are
3. Click on **QR Code \[B]**\
   ▷ The QR code is downloaded as an image file (.png)


---

# 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.buildings.ability.abb/collection/english-v14/documentation/assets/qr-codes-generieren.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.
