8689698486
Update configuration variable. Fix api_key value in example configuration. Have consistent capitalization when referencing Emoncms
1.7 KiB
| layout | title | description | date | sidebar | comments | sharing | footer | logo | ha_category | featured | ha_release |
|---|---|---|---|---|---|---|---|---|---|---|---|
| page | Emoncms history | Instructions on how to integrate Emoncms history into Home Assistant. | 2016-09-25 12:50 | true | false | true | true | emoncms.png | History | false | 0.31 |
The emoncms_history component makes it possible to transfer details collected with Home Assistant to 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:
# Example configuration.yaml entry
emoncms_history:
api_key: YOUR_EMONCMS_WRITE_API_KEY
url: https://emoncms.org
inputnode: 19
whitelist:
- sensor.owm_temperature
- sensor.owm_wind_speed
{% configuration %} api_key: description: Your Emoncms write api key required: true type: string url: description: The root URL of your Emoncms installation. (Use https://emoncms.org for the cloud based version) required: true type: string inputnode: description: Input node that will be used inside Emoncms. Please make sure you use a dedicated, not used before, node for this component! required: true type: integer whitelist: description: List of entity IDs you want to publish. required: true type: list scan_interval: description: Defines, in seconds, how regularly the states of the whitelisted entities are being gathered and send to Emoncms. required: false type: integer default: 30 {% endconfiguration %}