The influxdb component makes it possible to transfer all state changes to an external InfluxDB database. For more details, see the blog post on InfluxDB.
To use the influxdb component in your installation, add the following to your configuration.yaml file:
The default InfluxDB configuration doesn’t enforce authentication. If you have installed InfluxDB on the same host where Home Assistant is running and haven’t made any configuration changes, add the following to your configuration.yaml file:
# Example configuration.yaml entry
influxdb:
You will still need to create a database named home_assistant via InfluxDB’s web interface or command line. For instructions how to create a database check the InfluxDB documentation relevant to the version you have installed.
Configuration variables:
In this section you find some real life examples of how to use this component.
-influxdb:
diff --git a/developers/rest_api/index.html b/developers/rest_api/index.html
index 8d03d154b3..3e1a555bd4 100644
--- a/developers/rest_api/index.html
+++ b/developers/rest_api/index.html
@@ -138,7 +138,7 @@ You can append ?api_password=YOUR_PASSWORDThe API supports the following actions:
GET /api/
-Returns message if API is up and running.
+Returns a message if the API is up and running.
{
"message": "API running."
@@ -226,7 +226,7 @@ You can append ?api_password=YOUR_PASSWORD
GET /api/events
-Returns an array of event objects. Each event object contain event name and listener count.
+Returns an array of event objects. Each event object contains event name and listener count.
[
{
@@ -277,7 +277,7 @@ You can append ?api_password=YOUR_PASSWORD
GET /api/history
-Returns an array of state changes in the past. Each object contains further detail for the entities.
+Returns an array of state changes in the past. Each object contains further details for the entities.
[
[
@@ -461,7 +461,7 @@ You can append ?api_password=YOUR_PASSWORD
POST /api/services/<domain>/<service>
-Calls a service within a specific domain. Will return when the service has been executed or 10 seconds has past, whichever comes first.
+Calls a service within a specific domain. Will return when the service has been executed or after 10 seconds, whichever comes first.
You can pass an optional JSON object to be used as service_data.
@@ -500,7 +500,7 @@ You can append ?api_password=YOUR_PASSWORD
-The result will include any changed states that changed while the service was being executed, even if their change was the result of something else happening in the system.
+The result will include any states that changed while the service was being executed, even if their change was the result of something else happening in the system.
POST /api/template
@@ -527,7 +527,7 @@ The result will include any changed states that changed while the service was be
POST /api/event_forwarding
-Setup event forwarding to another Home Assistant instance.
+Set up event forwarding to another Home Assistant instance.
Requires a JSON object that represents the API to forward to.
@@ -539,7 +539,7 @@ The result will include any changed states that changed while the service was be
-It will return a message if event forwarding was setup successful.
+It will return a message if event forwarding was set up successfully.
{
"message": "Event forwarding setup."
@@ -560,7 +560,7 @@ The result will include any changed states that changed while the service was be
-It will return a message if event forwarding was cancelled successful.
+It will return a message if event forwarding was cancelled successfully.
{
"message": "Event forwarding cancelled."
diff --git a/developers/server_sent_events/index.html b/developers/server_sent_events/index.html
index adc67b129f..ecf80c3608 100644
--- a/developers/server_sent_events/index.html
+++ b/developers/server_sent_events/index.html
@@ -102,7 +102,7 @@
-For more comfort put the HTML snippet below in a file sse.html in your www folder of your Home Assistant configuration directory (.homeassistant)
+You can create a convenient view for this by creating an HTML file (sse.html) in the www folder of your Home Assistant configuration directory (.homeassistant). Paste this snippet into the file:
<!DOCTYPE html>
<html>
@@ -124,7 +124,7 @@
Examples
-A simplest way to consume server-sent events is httpie.
+A simple way to consume server-sent events is to use a command-line http client like [httpie][https://httpie.org/]. Installation info is on the site (if you use Homebrew, it’s brew install httpie). Once installed, run this snippet from your terminal:
$ http --stream http://localhost:8123/api/stream x-ha-access:YOUR_PASSWORD content-type:application/json
@@ -132,17 +132,17 @@
Website
-The home-assistant-sse repository contains an more advanced example.
+The home-assistant-sse repository contains a more advanced example.
Python
-If you want test the server-sent events without creating a website then the Python module sseclient can help. Install it first:
+If you want to test the server-sent events without creating a website, the Python module sseclient can help. To install (assuming Python and pip3 are already installed):
$ pip3 install sseclient
-The simplest script to consume the SSE looks like the following snipplet.
+The simplest script to consume the SSE in Python looks like this:
from sseclient import SSEClient
diff --git a/sitemap.xml b/sitemap.xml
index 72f0dcbe91..3d96074466 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2168,62 +2168,62 @@
https://home-assistant.io/demo/frontend.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/demo/index.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00
https://home-assistant.io/static/mdi-demo.html
-2016-10-17T16:23:19+00:00
+2016-10-17T19:33:47+00:00