> For the complete documentation index, see [llms.txt](https://docs.akenza.io/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/akenza.io/how-to-create-a-working-environment/how-to-connect-a-device.md).

# Connect a Device

{% hint style="info" %}
If you do not have a physical device at hand, you can use the [Device Simulator](/akenza.io/get-started/create-new-device/device-simulator.md).
{% endhint %}

### **1. Create a Data Flow**

Data Flows define how device data is processed and stored in akenza.

#### 1.1. Device Connector

To create a **Data Flow**, select *Create Data Flow* on the menu tab *Data Flow*. Select the Device Connector of your choice. The following Device Connectors are available:

* [LoRaWAN](https://docs.akenza.io/get-started/your-integration/swisscom-cmp-lpn)
* [HTTP](https://docs.akenza.io/api-reference/http.)
* [MQTT](https://docs.akenza.io/api-reference/mqtt)
* [CoAP](https://docs.akenza.io/api-reference/coap)
* [Sigfox](/akenza.io/deprecated/sigfox.md)
* [Disruptive Technologies](/akenza.io/tutorials/add-devices/how-to-integrate-disruptive-technologies-on-akenza.md)
* [Yanzi](/akenza.io/deprecated/how-to-connect-the-yanzi-lifecycle-cloud-on-akenza.md)

![Device connector](/files/ZAGo5uDm4Fgcw2PUGf9K)

#### **1.2. Device Type**

Choose your Device Type to extract, transform and normalize the data sent from the device. Akenza provides an extensive [device type library](https://akenza.io/features/device-type-library) with 100+ ready-to-use device types from different manufacturers around the globe.

If you do not find a suitable Device Type, you can create a [Custom Device Type](/akenza.io/get-started/your-data-flow/device-type/device-type.md) for your device.

&#x20;Select *Passthrough i*f no data parsing is required. The payload will be forwarded without changes.&#x20;

![Device Type](/files/fHPDz4MC3TsRznZEtVJf)

#### **1.3. Output Connector**

Choose one or multiple **Output Connectors** for your Data Flow. Output Connectors define the data destination of your Data Flow. The following options are available to process your data to:

**Data sinks:**

* [akenza DB](/akenza.io/get-started/your-data-flow/connectors/databases/akenza-db.md)
* [Webhook](/akenza.io/get-started/your-data-flow/connectors/streaming/webhook.md)
* [Azure IoT Hub](/akenza.io/get-started/your-data-flow/connectors/streaming/azure-iot-hub.md)
* [Google Pub/Sub](/akenza.io/get-started/your-data-flow/connectors/streaming/google-cloud-pub-sub.md)
* [InfluxDB](/akenza.io/get-started/your-data-flow/connectors/databases/influxdb.md)
* [AWS Kinesis](/akenza.io/get-started/your-data-flow/connectors/streaming/aws-kinesis.md)
* [Apache Kafka](/akenza.io/get-started/your-data-flow/connectors/streaming/apache-kafka.md)

**Notification services:**

* [E-Mail](/akenza.io/get-started/your-data-flow/connectors/notifications/email.md)
* [SMS](/akenza.io/get-started/your-data-flow/connectors/notifications/sms.md)
* [Microsoft Teams](/akenza.io/get-started/your-data-flow/connectors/notifications/microsoft-teams.md)
* [Slack](/akenza.io/get-started/your-data-flow/connectors/notifications/slack.md)

![Output connectors](/files/kW5VHtqGGlVEsnPdlgwt)

{% hint style="info" %}
The **akenza DB** Output Connector ensures, that all data passing through this Data Flow are saved and thereby become accessible.
{% endhint %}

Learn more about Data Flows:

{% content-ref url="/pages/-MO5Hket2gfliIgl-ZTd" %}
[Data Flows](/akenza.io/get-started/your-data-flow.md)
{% endcontent-ref %}

### 2. Create a Device

To create a new device, select *Create Device* in the **Assets Inventory**.&#x20;

![Asset Inventory Overview](/files/tykHaNfkIrYgHQa40spz)

#### 2.1 Basic device Information

Add a device name and optionally a description, a tag, or define a custom field. Select *Next*.&#x20;

![Device information](/files/bFhvC8KYxbz0UzMahlU5)

Choose the **Data Flow** that you have created just before and select your desired offline timeout. Select *Next*.

<figure><img src="/files/PnTy8cgQl5YHkBoXhljY" alt=""><figcaption></figcaption></figure>

#### 2.2. Connectivity Parameters

Fill in the **Connectivity Parameters** for your device.

* LoRaWAN: See [LoRaWAN](https://docs.akenza.io/api-reference/lorawan)
* HTTP / MQTT: Alphanumerical string of length between 8 and 64 characters

![Connectivity parameters](/files/30419NwZkQIrwO2BNSpX)

Finish the process with the *Create device* button.

To check incoming data of your device, select your device from the Asset Inventory table and check device status on the **Device detail page**.

![Device detail page](/files/k28tZvW1UmczyykcL7k1)

**Congratulations**, you have successfully added your first device!


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akenza.io/akenza.io/how-to-create-a-working-environment/how-to-connect-a-device.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
