> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/device-management/create-new-device/device-simulator.md).

# Device Simulator

This page explains the device simulator in more detail

The **device simulator** allows you to send data to your **HTTP device** on akenza without the need of a physical device.

The following steps are required to make use of the device simulator:

### 1. Create a Data Flow

* **Device Connector:** HTTP
* **Device Type:** Akenza Device Simulator
* **Output Connector:** Akenza DB

### 2. Create a device

Go to *Assets* and start with *Create device*. Proceed with the creation of an HTTP device.

{% hint style="info" %}
Find out more about [here](#2.-create-a-device) how to create an HTTP device.
{% endhint %}

### 3. Use of the Device Simulator

Select your HTTP device in *Assets*. The device detail page will be shown. The data generator is displayed in the header of your device detail page. Select *Edit* and the sidebar of the **data generator** will appear.

You can choose to have data generated automatically or manually specify the sensor values. Send it in intervals or manually.\
The following values are currently available for simulation:

* Temperature
* Humidity
* CO2
* Noise level
* Illuminance
* Occupancy

![Data Generator](https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2FGHWRsxygliJeIVDmA2Eq%2Fscreely-1685012300185.png?alt=media\&token=05878854-ac35-422b-966d-a9990dd4d950)


---

# 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.akenza.io/device-management/create-new-device/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.