influx
Defines the configuration required to write data to Influx.
InfluxDB v1.8.x
Section titled “InfluxDB v1.8.x”Example for Influx v1:
influx: url: http://localhost:8086 database: evcc # user: # password:InfluxDB v2.x
Section titled “InfluxDB v2.x”Example for Influx v2:
influx: url: http://localhost:8086 database: evcc # InfluxDB v2.x uses the term `bucket`, but for compatibility, it's still named `database` here token: 1234567890abcdef org: homeInfluxDB 3
Section titled “InfluxDB 3”InfluxDB 3 Core and Enterprise accept the write API of InfluxDB 2, so the settings for InfluxDB v2.x apply here as well.
The database is created on the first write if it doesn’t exist yet.
The token needs write access to this database.
InfluxDB 3 ignores org, so it can be left out.
Username and password aren’t accepted.
Example for InfluxDB 3:
influx: url: http://localhost:8181 database: evcc token: apiv3_1234567890abcdefIn the UI, use the regular InfluxDB form and enter the database name as Bucket. Organization can stay empty.
HTTPS with Self-Signed Certificate
Section titled “HTTPS with Self-Signed Certificate”When using HTTPS (https://), the TLS certificate is verified by default.
If you’re using a self-signed certificate, certificate verification can be disabled:
For example:
influx: url: https://influxdb.example.com:8086 database: evcc token: 1234567890abcdef org: home insecure: trueVictoriaMetrics
Section titled “VictoriaMetrics”VictoriaMetrics is a time series database with InfluxDB compatible REST API.
HTTP basic authentication can be done via the URL.
Example for VictoriaMetrics:
influx: url: http://[username:password@]victoria-metrics:8428