Integration that allows to use InfluxDB 1.x as telemetry data sink.
InfluxDB 2.x is not yet supported, vote or submit a PR if you want to use 2.x instead or in addition to 1.x.
NOTE: This integration will be inactive except for
sensor-field-mapping
unless included into directors.connectors.
NOTE: This integration is different from default InfluxDB integration embedded into Spring and Quarkus, those must be configured in infrastructure configuration.
Short list:
- Zone state (setpoints, PID controller internal state, and more)
- Economizer state (setpoints, PID controller internal state, and more)
- Unit state (demand, uptime, filter life left, and more)
Best explained by example:
connectors:
- influx:
id: influxdb-connector-house
instance: house
db: dz-reactive
uri: http://dx:8086
username: <InfluxDB username>
password: <InfluxDB password>
sensor-feed-mapping:
ambient-courtyard-temperature: air-ambient-courtyard
air-ambient-northeast: air-ambient-northeast
id
: Unique identifier this entity will be known as to the rest of the system. In particular, it is used by directors.connectors.instance
: Unique identifier for this entity (not the whole system, like in home-climate-control.instance - though that value can be used if there is just one InfluxDB connector).db
: InfluxDB database nameuri
: InfluxDB server to connect tousername
: InfluxDB username - optional, but recommendedpassword
: InfluxDB password - optional, but recommendedsensor-feed-mapping
: Optional list of pairs where on the left is the sensor ID, and on the right is the name it will translate to in InfluxDB. Note that this mapping is on top of the standard telemetry emitted for all the entities included in the directors this connector is attached to.