Plugin to connect to InfluxDB. It allows to easily send information by simply selecting the corresponding commands in a list. This allow to externalize the history which can then be consulted via Grafana for example.
The plugin also allows you to export Jeedom order history to InfluxDB.
Attention
The plugin supports influxDB versions >= 1.8 or >= 2.0. Older influxDBv1 versions < 1.8 are not supported.
Component | Version |
---|---|
Debian | Bullseye(11) & Bookworm(12) |
Jeedom | >= 4.4 |
InfluxDB | v1.8+ & v2 |
In order to use the plugin, you must download, install and activate it like any Jeedom plugin.
There is no particular configuration to do, the plugin may use cronDaily to reset the counters.
A Jeedom device correspond to one InfluxDB connection
Each connector will connect and send data to one and only one influxDB instance, but you can have as many connectors as you need. The plugin manages InfluxDB v1.8+ and v2, the basic principle between the two remains the same but the way to connect changes between the two.
For each connector, you have to configure the IP address of InfluxDB server, a user, a password and the database name. You have the option to enable or not https.
For v2, you must configure the URL in the form https://server.my
, the access token, the organization and the destination bucket (see influxDB documentation)
Tip influxDB has a free cloud offer for v2 that is very easy to set up for testing or even definitively if it suits you (limited to a single organization, rate and history retention), more info: https://www.influxdata.com/influxdb-cloud-pricing/
You can also choose how data must be sent, by default with auto-refresh. This configuration can be changed anytime without impact.
It is possible to have multiple connectors to the same database each configured with different mode and different commands if you want to have some commands send in real time while optimizing the load for others
In Auto-refresh mode, you can choose the schedule and the value that will be sent as the timestamp of the measurement:
In the second tab are displayed all the commands selected for sending to InfluxDB. It is possible to filter the lines displayed via the “Search” field.
It is possible to search and select commands to send via 3 methods:
Search example:
To export the history you must go to the Measurements tab in which you have configured the commands for your Jeedom device to be sent.
You can:
In both cases, the next step will ask you for the start date and the desired end date for the export and then the task will be scheduled. This may take some time depending on the amount of data to be exported but it will be transparent as the task will run in the background.
The InfluxDb device/connector commands are visible in the 3rd tab:
A point in InfluxDB represents a single data record that has 4 components: a measurement, fields set, tags set and a timestamp.
Below the relation implemented by the plugin between InfluxDB concepts and Jeedom concepts:
Jeedom | InfluxDB | Description |
---|---|---|
Command name | Measurement | A measurement in InfluxDB is conceptually similar to a SQL table. |
Command value date | Timestamp | It’s the timestamp of the data |
Device name | Field(key) | A field key is similar to a column name in a SQL table. |
Command value | Field(value) | It is the value of the point. |
Tags in InfluxDB are optional additional information associated to points. Tags can be used in queries to filter result. The following tags can be associated with each point sent, they must be selected in the device configuration page. This list can be amended if you need more:
Tag(key) | Tag(value) |
---|---|
Plugin | plugin name |
Object | Object/room name in Jeedom or “None” |
CommandName | command name |
GenericType | generic type of command |
If you have a problem, start by reading the latest plugin-related topics on community.
If despite this you do not find an answer to your question, do not hesitate to create a new topic, with the tag of the plugin (plugin-influxdb).
At a minimum, you will need to provide:
Preformatted Text
(button </>
on community), no files!