Scalable datastore for metrics, events, and real-time analytics.
InfluxDB is an open source time series database optimized for high-write-volume. It's useful for recording metrics, sensor data, events, and performing analytics. It exposes an HTTP API for client interaction and if often used in combination with Grafana to visualize the data.
This add-on comes with Chronograf & Kapacitor pre-installed as well. Which gives you a nice InfluxDB admin interface for managing your users, databases, data retention settings, and lets you peek inside the database using the Data Explorer.
The installation of this add-on is pretty straightforward and not different in comparison to installing any other Hass.io add-on.
- Add our Hass.io add-ons repository to your Hass.io instance.
- Install the "InfluxDB" add-on.
- Start the "InfluxDB" add-on.
- Check the logs of the "InfluxDB" to see if everything went well.
- Click the "OPEN WEB UI" button!
NOTE: Do not add this repository to Hass.io, please use:
https://github.com/hassio-addons/repository
.
Note: Remember to restart the add-on when the configuration is changed.
Example add-on configuration:
{
"log_level": "info",
"auth": true,
"reporting": true,
"ssl": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
}
Note: This is just an example, don't copy and past it! Create your own!
The log_level
option controls the level of log output by the addon and can
be changed to be more or less verbose, which might be useful when you are
dealing with an unknown issue. Possible values are:
trace
: Show every detail, like all called internal functions.debug
: Shows detailed debug information.info
: Normal (usually) interesting events.warning
: Exceptional occurrences that are not errors.error
: Runtime errors that do not require immediate action.fatal
: Something went terribly wrong. Add-on becomes unusable.
Please note that each level automatically includes log messages from a
more severe level, e.g., debug
also shows info
messages. By default,
the log_level
is set to info
, which is the recommended setting unless
you are troubleshooting.
Enable or disable InfluxDB user authentication.
Note: Turning this off is NOT recommended!
This option allows you to disable the reporting of usage data to InfluxData.
Note: No data from user databases is ever transmitted!
Enables/Disables SSL (HTTPS) on the web interface.
Set it true
to enable it, false
otherwise.
Note: This does NOT activate SSL for InfluxDB, just the web interface
The certificate file to use for SSL.
Note: The file MUST be stored in /ssl/
, which is the default for Hass.io
The private key file to use for SSL.
Note: The file MUST be stored in /ssl/
, which is the default for Hass.io
Adding this option to the add-on configuration allows you to disable
authentication on the Web Terminal by setting it to true
and leaving the
username and password empty.
Note: We STRONGLY suggest, not to use this, even if this add-on is only exposed to your internal network. USE AT YOUR OWN RISK!
The influxdb
component of Home Assistant makes it possible to transfer all
state changes to an InfluxDB database.
You need to do the following steps in order to get this working:
- Click on "OPEN WEB UI" to open the admin web-interface provided by this add-on.
- On the left menu click on the "InfluxDB Admin".
- Create a database for storing Home Assistant's data in, e.g.,
homeassistant
. - Goto the users tab and create a user for Home Assistant,
e.g.,
homeassistant
.
Now we've got this in place, add the following snippet to your Home Assistant
configuration.yaml
file.
influxdb:
host: a0d7b954-influxdb
port: 8086
database: homeassistant
username: homeassistant
password: <yourpassword>
max_retries: 3
default_measurement: state
Restart Home Assistant.
You should now see the data flowing into InfluxDB by visiting the web-interface and using the Data Explorer.
- While the Chronograph interface supports SSL, currently, the add-on does not support having SSL on InfluxDB. This limitation is caused by Chronograf and we are still looking into a proper solution for this.
This repository keeps a change log using GitHub's releases functionality. The format of the log is based on Keep a Changelog.
Releases are based on Semantic Versioning, and use the format
of MAJOR.MINOR.PATCH
. In a nutshell, the version will be incremented
based on the following:
MAJOR
: Incompatible or major changes.MINOR
: Backwards-compatible new features and enhancements.PATCH
: Backwards-compatible bugfixes and package updates.
Got questions?
You have several options to get them answered:
- The Community Hass.io Add-ons Discord chat server for add-on support and feature requests.
- The Home Assistant Discord chat server for general Home Assistant discussions and questions.
- The Home Assistant Community Forum.
- Join the Reddit subreddit in /r/homeassistant
You could also open an issue here GitHub.
This is an active open-source project. We are always open to people who want to use the code or contribute to it.
We have set up a separate document containing our contribution guidelines.
Thank you for being involved! 😍
The original setup of this repository is by Franck Nijhof.
For a full list of all authors and contributors, check the contributor's page.
Want some more functionality to your Hass.io Home Assistant instance?
We have created multiple add-ons for Hass.io. For a full list, check out our GitHub Repository.
MIT License
Copyright (c) 2018-2019 Franck Nijhof
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.