> 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/widgets/vordefinierte-widgets/analoger-trend.md).

# Analog trend

An Analog Trend displays value changes for one or more assets over a specific period of time.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/TyY8MiwZkn8nnra7qP54/2BED1009-BB75-4402-AE9A-D3BAB95E622C.png" alt=""><figcaption><p>Example of an Analog Trend – The temperature for two assets over the course of a day</p></figcaption></figure></div>

## When should this display be used?

The "Analog Trend" display should be used if you want to track the progression of one or more values over a certain period of time - e.g. the temperature in a room, or the number of people in a room.

## What is the difference compared to the widget "Two Analog Trends"?

In the “Analog Trend” widget, the individual trends are displayed overlaid.

In the “Two Analog Trends” widget, the individual trends are displayed one below the other.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/H4WDAWsOLY98H7OcLM3t/Bildschirmfoto%202023-09-28%20um%2016.48.06.png" alt=""><figcaption><p>Comparison between “Analog Trend” (bottom) and “Two Analog Trends” (top) - Both widgets show the temperature trends for the same 3 assets</p></figcaption></figure></div>

## Overview

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/knIDePuDmeY1KdV9WWzp/0827E63E-393E-4E4B-9452-F11CF8DBD543.png" alt=""><figcaption></figcaption></figure></div>

<table data-full-width="true"><thead><tr><th width="86.33333333333331"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Title bar</td><td>The title of the widget. Can be set during widget configuration under "Primary Asset".</td></tr><tr><td><strong>[B]</strong></td><td>Icon</td><td>Widget icon</td></tr><tr><td><strong>[C]</strong></td><td>Title of the displayed value</td><td>Can be adjusted when creating the widget</td></tr><tr><td><strong>[D]</strong></td><td>Content</td><td>The analog trend of a value</td></tr><tr><td><strong>[E]</strong></td><td>Set scaling</td><td>Click to select whether a day, a week, or a month should be displayed.</td></tr><tr><td><strong>[F]</strong></td><td>More options</td><td>See <a href="#ueber-widgets-navigieren">-> Navigate through widgets</a></td></tr><tr><td><strong>[G]</strong></td><td>Value</td><td>Numeric values of the added assets</td></tr></tbody></table>

## Configure Analog Trend

{% @supademo/embed url="<https://app.supademo.com/demo/IRQq1bECd2QOl_4n650KY>" demoId="IRQq1bECd2QOl\_4n650KY" fullWidth="true" %}

1. Make sure you are in the “Dashboard” menu.
2. Click “Add widget”.
3. Click on "Analog Trend".
4. Select the primary asset. The name of this asset will appear in the widget title bar.
5. Select the asset for which you want to create the Analog Trend.
6. Select the attribute for which you want to create an analog trend.
7. Choose whether the current value or the aggregated value should be displayed.
8. Optional: Repeat the last steps to create an analog trend for another asset. Both trends will then be overlaid in this widget.
9. Optional: Choose how much space your new widget should take up on the dashboard. By default, each widget takes up 1 column.
10. Click “Add widget”.

### Set scaling

Click repeatedly on **Set scaling \[E]**, to select whether a day, a week, or a month should be displayed.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/IZZLGl5YQsASB3zhZCbZ/42E13385-3D2B-489B-A96B-3E04EBF62B18.png" alt=""><figcaption><p>Day, week, or month view</p></figcaption></figure></div>


---

# 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/widgets/vordefinierte-widgets/analoger-trend.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.