> 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/preface/faq.md).

# FAQ

#### 1. Do you offer sensors or devices?

No. ABB BuildingPro is a platform for managing and controlling your buildings and devices.

#### 2. Which devices can be connected to ABB BuildingPro?

In ABB BuildingPro, you can integrate all data from devices that are connected via our [**connector apps** ](/collection/english-v14/apps/apps.md)are connected. We currently support the following connector apps:\
*ABB free\@home*, *Akenza*, *CoffeeCloud*, *Electricity Maps*, *Exchange app*, *Forecast*, *Glutz*, *GP Joule*, *Kentix*, *KentixONE*, *Kontakt.io*, *Localino*, *Loriot.io*, *Microsoft 365*, *myStrom app*, *Niagara*, *OpenBOS*, *ROOMZ*, *SAML SSO*, *Signify*, *Spreadsheet*, *stopwatch*, *Thingdust*, *Weather*, *Xovis*, *Xovis People Counter*, *Zevyy*.

Via the module [**Connectivity as a Service** → **Connect devices with Eliona**](/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden.md) the following protocol integrations are also available to you:

1. **Connect devices via Modbus**
2. **Connect devices via MQTT**\
   – incl. **MQTT Edge Nodes** (Control Edge)
3. **Connect devices via RESTful**
4. **Connect devices via Webhook**
5. **Connect devices via Apache Kafka**
6. **Connect devices via OPC UA**

In addition, you will find in the main menu under [**EDGE NODES**](/collection/english-v14/edge-nodes/edgenodes-in-abb-buildingpro.md)

* **What are Edge Nodes?** – a brief introduction to the concept
* **EdgeNodes in** ABB BuildingPro → **Set up Control Edge** – here you configure and manage your edge nodes to connect even remote field devices and protocols (e.g. BACnet, KNX, MBUS) via EdgeNode.

#### 3. If a sensor stops working, will I see that in ABB BuildingPro?

Yes. When setting up the sensor, you set a "Time to inactivity." This means that if the system does not receive a signal from the sensor after this time, the sensor is set to the status "inactive." You can view the information about the sensors (including their status) in the menu item "[asset management](/collection/english-v14/documentation/assets/asset-modellierung-templates-erstellen.md)" view.

#### 4. Can I change my active subscription plan?

All our subscriptions are valid for one year. During the first three months, you can change your package; to do so, write to <support@eliona.io>. After one year, you can renew your existing package or choose a different one.

#### 5. What does "Infravolt" mean?

Infravolt is basically a currency we use to measure resource consumption. Each element has its cost in Infravolt. "The costs" can be viewed in the section "[settings](/collection/english-v14/documentation/einstellungen.md)" on the tab "[license](/collection/english-v14/documentation/einstellungen/lizenz.md)view in the block "Infravolt consumption".

#### 6. How will I be informed about changes and new features?

The world keeps turning, and so does ABB BuildingPro. We notify all our users in the newsletter as soon as a new update is released. You can also learn about upcoming changes in the chapter [Changelog](/collection/english-v14/new-features/changelog-aktuelle-version-v14.2.5.md) learn more.

#### 7. How does the deployment of ABB BuildingPro work?

The ABB BuildingPro system can be deployed on any virtual machine or cloud solution. If you provide an SSH connection, the system is set up remotely via "one-click deployment". If you cannot provide an SSH connection, contact the Eliona support team. We recommend a virtual machine running version "Ubuntu 20.04", as support for older versions (Ubuntu 18.04) is being phased out and this can lead to problems.

#### 8. Why do we rely on PostgreSQL instead of NoSQL or time-series databases?

Most developer teams, including our ABB BuildingPro developers, work in the smart building provider environment on this huge pool of data called Big Data. For performance reasons, the extreme flood of time-series data is often stored in a NoSQL database, while the meta information is stored in a relational database. Almost all IoT platforms use NoSQL databases. It is clear that each of these databases works differently; operating a polyglot database architecture increases operational and application complexity. At Eliona, we do without a NoSQL database while maintaining the same performance, thereby eliminating the increased complexity in operations and the challenge in configuration.

To ensure excellent scalability of data ingestion rates (time series) while keeping all meta information in a single database, we rely on PostgreSQL and TimescaleDB. This makes it possible to write time series and meta information simultaneously with enormous data throughput. 120,000 data records per second with a massive database size. In one minute, one could write the energy data of all of Switzerland into ABB BuildingPro.

Let's go back once more and show what is in focus in IoT/smart building projects: collecting data, analyzing it, and reacting to it in order to improve benefits/efficiency, reduce downtime/waste, and offer better services. In other words, we need more than a data store: we also need an easy way to derive actionable insights from the data. And this is where SQL comes in. While it has been fashionable in recent years to denounce SQL and praise NoSQL, the truth is that SQL is extremely powerful.

**Advantages of PostgreSQL**

On the market for more than 30 years Open source many add-ons, plugins and extensions web services such as [RESTful](/collection/english-v14/for-developers/rest-api.md) complex WHERE predicates (supported by secondary indexes) aggregations and orderings; window functions, libraries with mathematical and statistical functions, etc. All GEO information – important in the area of localization and tracking – is provided via PostGIS

If the standard performance of PostgreSQL needs to be increased (from 100,000 transactions per second), there is a PostgreSQL extension called «TimescaleDB», which can easily compete with InfluxDB.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/c0AUMShnXEIBtKBuNYZY/image.png" alt=""><figcaption></figcaption></figure>

#### 9. What standardized integration options are there in ABB BuildingPro?

* Eliona [REST API](/collection/english-v14/for-developers/rest-api.md).
* Eliona [App SDK](/collection/english-v14/apps/app-sdk.md).
* [MQTT](/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/gerate-per-mqtt-verbinden.md) (we ship an MQTT broker with ABB BuildingPro, with ABB BuildingPro itself acting as an MQTT client).
* [REST](/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/gerate-per-restful-verbinden/restful-verbindung-konfigurieren.md) Requests (we have the option to configure REST and various requests in the frontend).
* [Webhooks](/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/gerate-per-webhook-verbinden.md)

#### **10. Why am I not staying logged in to** ABB BuildingPro **?**

Why am I, despite selecting "*Stay logged in*" after a certain time prompted to log in again?

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/toEsBaM2vdKybd5t3ZJ7/image.png" alt=""><figcaption></figcaption></figure>

The "Stay logged in" option normally has a validity period of 8 hours, roughly one working day. It only ensures that during this time no new login is required with the same browser, even if it or the app has been closed. The limited validity period ensures that security and control over access to ABB BuildingPro are maintained. After this time has expired, the user must log in again.


---

# 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.buildings.ability.abb/collection/english-v14/preface/faq.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.
