> 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/zwei-analoge-trends.md).

# Two analog trends

The “Two Analog Trends” widget displays changes in value for two or more assets over a certain period of time.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/ji9ijZYmCQsMX7Ly8GFN/934CFAA0-29B1-4153-8583-7A8A477BAA90.png" alt=""><figcaption><p>The temperature for 3 assets over the course of a day</p></figcaption></figure></div>

## When should this display be used?

The “Two Analog Trends” display should be used when you want to track the progression of multiple values over a certain period of time — e.g., the temperature trend in rooms.

## What is the difference to the “Analog Trend” widget?

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/811A0GBLewnO3VxnUweb/082403A9-E3EE-4C52-978A-0EC6529FF6D7.png" alt=""><figcaption></figcaption></figure></div>

<table><thead><tr><th width="86.33333333333331"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Title</td><td>Widget title. Influenced by the selection of the "Primary Asset" (see below.)</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><p>Available options:</p><ul><li>Navigate to further sections <a href="broken://pages/e0e488a124019cdea14e52977e47c41e3cee0fe9">-> Navigate through widgets</a></li></ul></td></tr><tr><td><strong>[G]</strong></td><td>Value</td><td>[?] Can be set in the widget options whether aggregated or current</td></tr></tbody></table>

## Configure “Two Analog Trends”

{% @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 “Two Analog Trends”.
4. Select the primary asset. The name of this asset will appear in the widget title bar.
5. Select the widget 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/ji9ijZYmCQsMX7Ly8GFN/934CFAA0-29B1-4153-8583-7A8A477BAA90.png" alt=""><figcaption><p>Day view</p></figcaption></figure></div>

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/7xP77EDm74fvdzzLYwkh/255ECC49-F44E-4A66-9E69-5D9B20646AA5.png" alt=""><figcaption><p>Week view</p></figcaption></figure></div>

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/bsh0XDljkZgw4TdtfOBl/01B7C8D6-A038-43A3-8BC2-5AF436FAB551.png" alt=""><figcaption><p>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/zwei-analoge-trends.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.