Publish HASS events to your Elasticsearch cluster!
Features
- Effeciently publishes Home-Assistant events to Elasticsearch using the Bulk API
- Automatically maintains Indexes and Index Templates using the Rollover API
- Supports X-Pack Security via optional username and password
- Tracks the Elasticsearch cluster health in the
sensor.es_cluster_health
sensor - Exclude specific entities or groups from publishing
Compatability
Getting Started
The Elasticsearch component requires, well, Elasticsearch! This component will not host or configure Elasticsearch for you, but there are many ways to run your own cluster. Elasticsearch is open source and free to use: just bring your own hardware! Elastic has a great setup guide if you need help getting your first cluster up and running.
If you don’t want to maintain your own cluster, then give the Elastic Cloud a try! There is a free trial available to get you started.
Installation
- Copy the contents of
custom_components
to your$HASS_CONFIG/custom_components
directory, where$HASS_CONFIG
is the location on your machine where Home-Assistant lives. Example:/home/pi/.homeassistant
and/home/pi/.homeassistant/custom_components
. You may have to create thecustom_components
directory yourself. - Configure the component in
$HASS_CONFIG/configuration.yaml
(see Configuration section below) - Restart Home-Assistant
Expected file structure
.homeassistant/
|-- custom_components/
| |-- elastic/
| |-- __init__.py
| |-- sensor.py
Configuration
This is the bare-minimum configuration you need to get up-and-running:
elastic:
# URL should point to your Elasticsearch cluster
url: http://localhost:9200
Configuration Variables
All variables are optional unless marked required.
Basic Configuration
- url (Required, unless using
cloud_id
): The URL of your Elasticsearch cluster - cloud_id: The Cloud ID of your Elasticsearch cluster
- username: If your cluster is protected with Basic Authentication via X-Pack Security, then provide a username here
- password: If your cluster is protected with Basic Authentication via X-Pack Security, then provide a password here
-
exclude:
- domains: Specify an optional array of domains to exclude from publishing
-
entities: Specify an optional array of entity ids to exclude from publishing
Advanced Configuration
- verify_ssl (default:
true
): Set tofalse
to disable SSL certificate verification. - sslcapath (default:
None
): Optional path to PEM encoded certificate authority bundle. - index_format (default:
"hass-events"
): The format of all index names used by this component. The format specified will be used to derive the actual index names. Actual names use the Rollover API convention of appending a 5-digit number to the end. e.g.:hass-events-00001
- alias (default:
"active-hass-index"
): The index alias which will always reference the index being written to. - publish_frequency (default:
60
): Specifies how often, in seconds, this component should publish events to Elasticsearch. - onlypublishchanged (default:
false
): Specifies that only entities that underwent a state change should be published. Whenfalse
, all entity states are published. - requestrolloverfrequency (default:
3600
): Specifies how often, in seconds, this component should attempt a Rollover. The Rollover will only occur if the specified criteria has been met. - rollovermaxage (default:
None
): Specifies themax_age
condition of the Rollover request - rollovermaxdocs (default:
None
): Specifies themax_docs
condition of the Rollover request - rollovermaxsize (default:
"30gb"
): Specifies themax_size
condition of the Rollover request
Example Configurations
Exclude all groups from publishing:
elastic:
# URL should point to your Elasticsearch cluster
url: http://localhost:9200
exclude:
domains: ['group']
Exclude a specific switch from publishing:
elastic:
# URL should point to your Elasticsearch cluster
url: http://localhost:9200
exclude:
entities: ['switch.living_room_switch']
Multiple exclusions:
elastic:
# URL should point to your Elasticsearch cluster
url: http://localhost:9200
exclude:
domains: ['group', 'automation']
entities: ['switch.living_room_switch', 'light.hallway_light']
Security
If you are connecting to a secured Elasticsearch cluster, the user you authenticate with (see username
and password
configuration options above)
should have a role assigned with the following privileges. Note that if you adjust the index_format
or alias
settings that the role definition must be updated accordingly:
POST /_xpack/security/role/hass_writer
{
"cluster": [
"manage_index_templates",
"monitor"
],
"indices": [
{
"names": [
"hass-events*",
"active-hass-index"
],
"privileges": [
"manage",
"index",
"create_index",
"create"
],
"field_security": {
"grant": [
"*"
]
}
}
],
"applications": [],
"run_as": [],
"metadata": {},
"transient_metadata": {
"enabled": true
}
}
Troubleshooting
Solutions to common questions and errors:
Error loading elasticsearch
After installing this component, you may see an error similar to this on startup:
No module named ‘elasticsearch’
ERROR (MainThread) [homeassistant.setup] Error during setup of component elastic Traceback (most recent call last): File "/usr/src/app/homeassistant/setup.py", line 145, in _async_setup_component hass, processed_config) File "/usr/local/lib/python3.6/asyncio/coroutines.py", line 212, in coro res = func(*args, **kw) File "/config/custom_components/elastic/__init__.py", line 62, in async_setup gateway = ElasticsearchGateway(hass, conf) File "/config/custom_components/elastic/__init__.py", line 126, in __init__ self.client = self._create_es_client() File "/config/custom_components/elastic.py", line 134, in _create_es_client import elasticsearch ModuleNotFoundError: No module named 'elasticsearch'
This means that home-assistant was not able to download the required elasticsearch
module for this comonent to function.
Solution: Restart home assistant
More info: https://github.com/legrego/homeassistant-elasticsearch/issues/23
Certificate verify failed
When connecting to a TLS protected cluster, you might receive the following error:
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)
This generally means that the certificate is not trusted by the home-assistant runtime. Please ensure your certificates are setup correctly. To skip certificate verification, see setup instructions here
More info: https://github.com/legrego/homeassistant-elasticsearch/issues/33
index_format
and index_alias
not working
If you make any changes to the index_format
or index_alias
configuration settings, it’s necessary to delete the active-hass-index-v2
index template before starting home-assistant:
DELETE _template/active-hass-index-v2
More info: https://github.com/legrego/homeassistant-elasticsearch/issues/48
Support
This project is not endorsed or supported by either Elastic or Home-Assistant - please open a GitHub issue for any questions, bugs, or feature requests.