> 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/weitere-funktionen/attribut-funktionen/geratesimulator.md).

# Device simulator

{% hint style="warning" %}
Attention: In order to use the device simulator, the [-> Device Simulator App](/collection/english-v14/apps/apps/device-simulator.md) must be installed.
{% endhint %}

The **Device Simulator** in *Eliona* allows you to simulate data streams to test dashboards, rules, and other features before real devices are connected. It is ideal for validating configurations, prototyping new features, and analyzing different scenarios. It also supports training and troubleshooting by replicating realistic operating states – all without physical hardware.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/8ux2APfqVDmUczmSKTJp/Device%20simulator%20(1).png" alt=""><figcaption></figcaption></figure>

## Device Simulator **Configure**

1. **Navigate to the desired attribute of an asset:**\
   Open an asset and select an attribute from the list of **attribute values** by clicking on the attribute **\[A]**.
2. **Enable simulator:**\
   Switch on the device simulator with the **Enable \[B]** in.
3. **Select simulation type:**\
   Select the desired type of simulation **\[C]**:

   ▷ **Sine wave:** Smooth, cyclical data.

   ▷ **Random:** Unpredictable values.

   ▷ **Sawtooth wave:** Linear rise followed by abrupt drop.\
   These options can be found under **Configuration** .
4. **Integer:** Specifies whether the generated value should be an integer or a float **\[D]**.
5. **Define parameters:**\
   Set the simulation parameters:

   ▷ **Minimum value:** The lowest generated value **\[E]**.

   ▷ **Maximum value:** The highest generated value **\[F]**.

   ▷ **Interval (seconds):** Interval in seconds for data generation. (sampling rate) (How often should new data be generated?) **\[G]**.

   ▷ **Frequency (Hz):** Frequency in Hz for wave functions. (How often should the function reach the original value per second?) (typically less than 1) (Must not be higher than 1/(2\*interval\_seconds) to avoid aliasing/Nyquist frequency) **\[H]**.
6. **Save settings:**\
   Click on **Save**, to apply the configuration **\[I]**.\
   ▷ The simulation is activated with the selected parameters.

{% hint style="info" %}
Simulated attributes are marked with a <img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/Cu0nLXkYtFiPCpo09deb/image.png" alt="" data-size="line"> Marked.
{% endhint %}

## **Additional management options**

For advanced configurations and API-based generators, the **Device Simulator App** can be used.\
[-> Device Simulator App Documentation](/collection/english-v14/apps/apps/device-simulator.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.buildings.ability.abb/collection/english-v14/documentation/weitere-funktionen/attribut-funktionen/geratesimulator.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.