home-assistant.io/source/_components/emoncms_history.markdown
Matt N 2b5d3c0c10 Fix over 100 typos/spelling mistakes :P (#1483)
* Fix a bunch of typos/spelling mistakes
* Removed extra spaces from emulated_hue
* Correct device type. of binary_sensor.enocean.markdown
2016-11-23 10:23:23 +01:00

39 lines
1.5 KiB
Markdown

---
layout: page
title: "Emoncms history"
description: "Instructions on how to integrate Emoncms history into Home Assistant."
date: 2016-09-25 12:50
sidebar: true
comments: false
sharing: true
footer: true
logo: emoncms.png
ha_category: History
featured: false
ha_release: 0.31
---
The `emoncms_history` component makes it possible to transfer details collected with Home Assistant to [Emoncms.org](https://emoncms.org/) or your local running Emoncms instance. It will send the data to a specific input node on Emoncms with the entity IDs as a key. Afterwards you can create feeds and dashboards in Emoncms with the collected data.
To use the `emoncms_history` component in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
emoncms_history:
api_key: put your emoncms WRITE api key here
url: https://emoncms.org
inputnode: 19
whitelist:
- sensor.owm_temperature
- sensor.owm_wind_speed
```
Configuration variables:
- **api_key** (*Required*): Your emoncms write api key
- **url** (*Required*): The root URL of your Emoncms installation. (Use https://emoncms.org for the cloud based version)
- **inputnode** (*Required*): Input node that will be used inside emoncms. Please make sure you use a dedicated, not used before, node for this component!
- **whitelist** (*Required*): List of entity IDs you want to publish.
- **scan_interval** (*Optional*): Defines, in seconds, how regularly the states of the whitelisted entities are being gathered and send to emoncms. Default is 30 seconds.