|
<< Click to Display Table of Contents >> Navigation: Components > IoT > InfluxDB Writer |
This component is used to write to an Influx database 2.0, which must be installed. The line protocol is used for this.
Data points of the component:
Name |
Type |
Function |
|---|---|---|
Diagnosis [Text] |
Output |
Error messages are output here. Attention: Diagnostic or debug outputs are only intended for use in the event of an error. Please only use them after consulting the support team! If used, these can considerably impair the performance of the service. |
Dynamic |
Folder |
This folder contains the data points created in the channel editor. |
Driver On/Off |
Bidirectional |
Switches the driver On or Off |
Driver Gateway - KNX |
Input |
Direct connection to the KNX driver. All group addresses are automatically created in the database with component name. |
Driver Status |
Output |
If the driver is connected, an ON signal is output. |
Properties of the component
Name |
Standard |
Function |
|---|---|---|
Channels |
|
Channel editor for storing network data |
URL |
|
URL to the InfluxDb system, for example: http://localhost:8086 or https://a_name.cloud2.influxdata.com |
Authentication token |
|
Authentication token assigned in the InfluxDb system. |
Bucket Name |
|
BucketName assigned in the InfluxDb system. |
Organisation ID |
|
ID which is displayed in the Influx system. |
Driver On/Off |
|
(De)Activate the component at system startup. |
Channel Editor
Name |
Description |
|---|---|
Name |
Display name of the data point in the Dynamic folder |
Measurement |
Name of the measurement in which the data is written |
Tags |
Tag name in which the data points are recorded. The tag key and the tag value are linked with a =. Example: Channel=channel001 |
Field |
Fields for the data points. Each data point requires at least one field in the line protocol. There can only be one field (value) per channel. |
Factor |
Specification of a value with which the input value is to be factorised. |