Connect Devices to Eliona
About This Chapter
This chapter describes how to connect external devices to Eliona and display data from these devices in Eliona.
Procedure
Overview
The first step is to establish a communication link between Eliona and the devices to be connected. In Fig. 1, this is Phase "B".
In the second step, the incoming raw data usually has to be decoded. This is because external devices send their data (payload) encoded or in another unusable format.
In the third step, the decoded data values are finally assigned to the individual ↗ attributes of an asset via formats.
The last two steps occur in Phase C.

Details
Fig. 1 shows the schematic data flow from an external device to Eliona.

Phase A
Phase A takes place entirely outside of Eliona. In Phase A, raw data from individual devices is provided and sent to a server or broker. An example of such a server is ↗ TTN [External Link]
The details, e.g., which transmission format is used, vary greatly depending on the manufacturer and device. Phase A is not a part of Eliona and is not explained in more detail in this documentation. Consult the documentation of the external devices or servers to learn more about this topic.
Phase B
In Phase B, the actual connection of Eliona and the device data takes place. In this phase, a data connection is established between Eliona and the external devices.
Eliona accepts the following interfaces:
Click on a link to jump directly to the instructions that describe how to establish a data connection via the corresponding interface.
Phase C
In Phase C, the data is processed and made usable within Eliona.
The data sent by the external devices and received in Eliona is in most cases not easily readable. Depending on the manufacturer, this raw data is encoded or is in a format that cannot be used further. Therefore, this raw data is decoded with ↗ functions and converted into a human-readable .json format.
The decoded data is assigned to the individual attributes of an asset via ↗ formats.
Prerequisites
The following prerequisites must be met to connect external devices:
Correctly Configured External Devices and Servers
The devices to be connected must be configured correctly and send data properly.
Servers and brokers must be configured correctly.
Existing Access Data for Servers, Brokers, and Other Services
The access data for servers and brokers must be known.
Asset Templates
It is assumed that you have created correct asset templates. The asset template must have the necessary asset attributes
Assets
Assets must be created based on the asset template.
Last updated