> 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/mandatory-base/platform-core/connect-hub/device-simulator.md).

# Device Simulator

Device Simulator is a built-in feature of **Platform Core > Connect Hub** in ABB Ability BuildingPro Suites. It generates test data for asset attributes without requiring physical devices or a separate app installation. Use it to test dashboards, analytics, alarms, and other data-driven configurations before connecting real equipment, or to prepare demonstrations and training scenarios.

You configure a simulation for each attribute by selecting an algorithm and its parameters. While the simulation runs, Device Simulator writes generated values to that attribute at the configured interval.

## What You Can Do

* Create dedicated simulated assets from an asset type.
* Connect simulations to attributes of existing assets.
* Generate numeric waveforms, random values, constant values, building-load patterns, and mapped states.
* Pause or activate one simulation, all simulations of an asset, or all simulations in the current tenant.
* Inspect the configured parameters, current values, and the last 24 hours of attribute data.
* Copy an algorithm and its parameters to other attributes of the same asset.

## Simulated Assets and Connected Attributes

<table><thead><tr><th width="203.7999267578125">Area</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Simulated Assets</strong></td><td>Create a new virtual asset dedicated to simulation data. Its asset type defines the available attributes. After creating the asset, configure simulations for the attributes you want to use.</td></tr><tr><td><strong>Connected Attributes</strong></td><td>Add simulations to attributes of assets that already exist. The assets remain normal assets; Device Simulator lists their simulation connections grouped by asset.</td></tr></tbody></table>

Both areas use the same algorithms and attribute-level configuration. Creating a virtual asset does not automatically configure simulations for all its attributes.

{% hint style="warning" %}
A simulation on an existing attribute writes test values to that attribute. Choose test assets or attributes carefully, especially if real devices or other processes also write data to them. Generated data can affect dashboards, analytics, and alarm evaluations that use those attributes.
{% endhint %}

## Before You Start

* Use a user account with access to **Device Simulator** in **Platform Core > Connect Hub**. If the page is unavailable, ask your administrator to check your access permissions.
* For a new virtual asset, have an appropriate [asset template](/collection/mandatory-base/assets/asset-modeling-create-templates/create-a-new-template.md) available.
* For an existing asset, identify the attributes that should receive test data and choose parameters appropriate for their units and intended value ranges.

## Get Started

1. [Open Device Simulator](/collection/mandatory-base/platform-core/connect-hub/device-simulator/open-device-simulator.md).
2. [Create a simulated asset or connect existing attributes](/collection/mandatory-base/platform-core/connect-hub/device-simulator/create-edit-simulation.md).
3. [Manage simulated assets and connected attributes](/collection/mandatory-base/platform-core/connect-hub/device-simulator/simulated-assets-and-connected-attributes.md).
4. [Inspect and configure an asset's simulations](/collection/mandatory-base/platform-core/connect-hub/device-simulator/asset-simulation-details.md).

Use the [simulation algorithms reference](/collection/mandatory-base/platform-core/connect-hub/device-simulator/simulation-algorithms.md) to choose a data pattern and understand its parameters.


---

# 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/mandatory-base/platform-core/connect-hub/device-simulator.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.