> 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/edge-app-marketplace-for-plug-ins-and-extentions/apps/loriot.io.md).

# Loriot.io

The Loriot.io App provides integration and synchronization between BuildingPro Suites and   Loriot.io services as well as LoRaWAN devices.

### Overview

This manual provides instructions on how to configure, install, and use the Loriot.io App to manage resources and synchronize LoRaWAN devices between BuildingPro Suites and Loriot.io services.

### Installation

Install the Loriot.io App via the BuildingPro Suites App Store.

### Configuration

The Loriot.io App requires configuration via the BuildingPro Suites settings. The following are the general steps and details required to effectively configure the app.

#### Registering the App with the Loriot.io Service

Create credentials in the Loriot.io service to establish the connection from BuildingPro Suites to Loriot.io services. All required credentials are listed below in the configuration section.

To connect to the [Loriot.io API](https://docs.loriot.io/space/LNS/6231610/User+API+7.0), you must ask your provider for an API key.

#### Configuring the Loriot.io App

Configurations can be created in BuildingPro Suites under `Apps > Loriot.io > Settings`, which opens the app's [Generic Frontend](https://doc.eliona.io/collection/v/eliona-english/manuals/settings/apps). Here you can use the `/configs` endpoint with the POST method. Each configuration requires the following data:

| Attribute         | Description                                                |
| ----------------- | ---------------------------------------------------------- |
| `apiBaseUrl`      | URL of the Loriot.io services.                             |
| `apiToken`        | API token to access the API.                               |
| `enable`          | Flag to activate or deactivate this configuration.         |
| `refreshInterval` | Interval in seconds for data synchronization.              |
| `requestTimeout`  | API query timeout in seconds.                              |
| `tenantIDs`       | List of BuildingPro Suites Tenant IDs for data collection. |

Example configuration in JSON:

```json
{
  "apiBaseUrl": "http://service/v1",
  "apiToken": "53cr3t",
  "enable": true,
  "refreshInterval": 60,
  "requestTimeout": 120,
  "tenantIDs": [
    "10"
  ]
}
```

To define devices managed by the Loriot.io App, it is necessary to configure these devices. Here you can use the `/devices` endpoint with the POST method. If the device does not yet exist, it is also registered in Loriot.io.

Example for device configuration via OTAA v1.0 in JSON:

```json
{
    "devEUI": "0123456789ABCDEF",
    "appID": "1234ABCD",
    "assetTypeName": "Device",
    "configID": 1,
    "title": "LoRaWAN Testgerät",
    "description": "Dies ist ein LoRaWAN Testgerät",
    "appEUI": "1000000000000000",
    "appKey": "geheim"
}
```

### Continuous Asset Creation

Once the configuration and device setup are complete, the app starts Continuous Asset Creation (CAC). Discovered resources are automatically created as assets in BuildingPro Suites, and users are notified via the BuildingPro Suites notification system.

### Additional Functions

#### Device Updates

You can change the title and description of a device asset in BuildingPro Suites. These changes are automatically synchronized in Loriot.io. If you delete an asset in BuildingPro Suites, the corresponding device is also unregistered in Loriot.io.


---

# 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/edge-app-marketplace-for-plug-ins-and-extentions/apps/loriot.io.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.