Skip to content
🏠 => 📊 Publish Home-Assistant events to Elasticsearch
Branch: master
Clone or download
Latest commit 9aab331 Feb 27, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Update issue templates Sep 2, 2018
LICENSE Adds basic troubleshooting guide (#53) Feb 27, 2019
pylintrc Initial Commit May 10, 2018
requirements.travis.txt Update travis requirements (#44) Nov 1, 2018

Elasticsearch Component for Home-Assistant Build Status

Publish HASS events to your Elasticsearch cluster!


  • 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


  • Elasticsearch 6.x (Self or Cloud hosted), with or without X-Pack.

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.


  1. 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 the custom_components directory yourself.
  2. Configure the component in $HASS_CONFIG/configuration.yaml (see Configuration section below)
  3. Restart Home-Assistant

Expected file structure

|-- custom_components/
|   |-- elastic/
|       |--
|       |--


This is the bare-minimum configuration you need to get up-and-running:

    # 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 to false to disable SSL certificate verification.
  • ssl_ca_path (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.
  • only_publish_changed (default: false): Specifies that only entities that underwent a state change should be published. When false, all entity states are published.
  • request_rollover_frequency (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.
  • rollover_max_age (default: None): Specifies the max_age condition of the Rollover request
  • rollover_max_docs (default: None): Specifies the max_docs condition of the Rollover request
  • rollover_max_size (default: "30gb"): Specifies the max_size condition of the Rollover request

Example Configurations

Exclude all groups from publishing:

    # URL should point to your Elasticsearch cluster
    url: http://localhost:9200
        domains: ['group']

Exclude a specific switch from publishing:

    # URL should point to your Elasticsearch cluster
    url: http://localhost:9200
        entities: ['switch.living_room_switch']

Multiple exclusions:

    # URL should point to your Elasticsearch cluster
    url: http://localhost:9200
        domains: ['group', 'automation']
        entities: ['switch.living_room_switch', 'light.hallway_light']


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": [
  "indices": [
      "names": [
      "privileges": [
      "field_security": {
        "grant": [
  "applications": [],
  "run_as": [],
  "metadata": {},
  "transient_metadata": {
    "enabled": true


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/", line 145, in _async_setup_component hass, processed_config) File "/usr/local/lib/python3.6/asyncio/", line 212, in coro res = func(*args, **kw) File "/config/custom_components/elastic/", line 62, in async_setup gateway = ElasticsearchGateway(hass, conf) File "/config/custom_components/elastic/", line 126, in __init__ self.client = self._create_es_client() File "/config/custom_components/", 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:

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:

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:


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.

You can’t perform that action at this time.