Release 0.47
This commit is contained in:
Paulus Schoutsen
parent
52f2dda864
commit
8fc3193a39
11 changed files with 597 additions and 25 deletions
35
source/_components/mailgun.markdown
Normal file
35
source/_components/mailgun.markdown
Normal file
|
|
@ -0,0 +1,35 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Mailgun"
|
||||
description: "Instructions how to add Mailgun mail notifications to Home Assistant."
|
||||
date: 2017-02-06 16:52
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: mailgun.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.38
|
||||
---
|
||||
|
||||
The component supports push messages and generates events based on inbound data. To use, add a Route set to Store and Notify with a URL of the following form: `https://<domain>/api/mailgun?api_password=<password>`
|
||||
|
||||
To send messages, use the [Mailgun notify platform][notify].
|
||||
|
||||
[notify]: /components/notify.mailgun/
|
||||
|
||||
## {% linkable_title Sample configuration %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
mailgun:
|
||||
domain: mg.example.com
|
||||
api_key: token-XXXXXXXXX
|
||||
sandbox: False
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **domain** (*Optional*): This is the domain name to be used when sending out mail. Defaults to the first custom domain you have set up.
|
||||
- **sandbox** (*Optional*): Whether to use the sandboxed domain for outgoing mail. The `domain` item takes precedence over this. Defaults to `False`.
|
||||
- **api_key** (*Required*): This is the API token that has been generated in your Mailgun account.
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Mailgun"
|
||||
title: "Mailgun Notify"
|
||||
description: "Instructions how to add Mailgun mail notifications to Home Assistant."
|
||||
date: 2017-02-06 16:52
|
||||
sidebar: true
|
||||
|
|
@ -12,18 +12,23 @@ ha_category: Notifications
|
|||
ha_release: 0.38
|
||||
---
|
||||
|
||||
The Mailgun notification service allows you to send emails via Mailgun's REST API.
|
||||
The Mailgun notification service allows you to send emails via Mailgun's REST API. It requires the [Mailgun component] to be set up.
|
||||
|
||||
[Mailgun component]: /components/mailgun/
|
||||
|
||||
## {% linkable_title Sample configuration %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
mailgun:
|
||||
domain: mg.example.com
|
||||
api_key: token-XXXXXXXXX
|
||||
sandbox: False
|
||||
|
||||
notify:
|
||||
- name: NOTIFIER_NAME
|
||||
- name: mailgun
|
||||
platform: mailgun
|
||||
domain: YOUR_MAILGUN_DOMAIN
|
||||
token: TOKEN
|
||||
recipient: RECIPIENT_EMAIL
|
||||
recipient: me@example.com
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
|
@ -34,21 +39,6 @@ Configuration variables:
|
|||
- **recipient** (*Required*): The email address of the recipient.
|
||||
- **sender** (*Optional*): The sender's email address. Defaults to `hass@DOMAIN`, where `DOMAIN` is outgoint mail domain, as defined by the `domain` and `sanbox` configuration entries.
|
||||
|
||||
## {% linkable_title Full configuration %}
|
||||
|
||||
A full configuration example for the Mailgun notifier system can look like this:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
notify:
|
||||
- name: mailgun
|
||||
platform: mailgun
|
||||
domain: mg.example.com
|
||||
sanbox: False
|
||||
token: 'token-XXXXXXXXX'
|
||||
recipient: me@example.com
|
||||
```
|
||||
|
||||
## {% linkable_title Example automation %}
|
||||
|
||||
The following automation reacts to an event by sending out an email with two attachments.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,16 @@ ha_category: Automation
|
|||
ha_release: 0.47
|
||||
---
|
||||
|
||||
This component allows you to write Python scripts that are exposed as services in Home Assistant. Each Python file created in the `<config>/python_scripts/` folder will be exposed as a service. The content is not cached so you can easily develop: edit file, save changes, call service. The scripts are run in a sandboxed environment with access to the `hass` object, the service call data as `data` and a logger as `logger`.
|
||||
This component allows you to write Python scripts that are exposed as services in Home Assistant. Each Python file created in the `<config>/python_scripts/` folder will be exposed as a service. The content is not cached so you can easily develop: edit file, save changes, call service. The scripts are run in a sandboxed environment. The following variables are available in the sandbox:
|
||||
|
||||
| Name | Description |
|
||||
| ---- | ----------- |
|
||||
| `hass` | The Home Assistant object. Access is only allowed to call services, set/remove states and fire events. [API reference][hass-api]
|
||||
| `data` | The data passed to the Python Script service call.
|
||||
| `logger` | A logger to allow you to log messages: `logger.info()`, `logger.warning()`, `logger.error()`. [API reference][logger-api]
|
||||
|
||||
[hass-api]: https://home-assistant.io/developers/development_hass_object/
|
||||
[logger-api]: https://docs.python.org/3.4/library/logging.html#logger-objects
|
||||
|
||||
## {% linkable_title Writing your first script %}
|
||||
|
||||
|
|
|
|||
16
source/_components/sensor.ecobee.markdown
Normal file
16
source/_components/sensor.ecobee.markdown
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Ecobee Sensor"
|
||||
description: "Instructions how to setup the Ecobee sensors within Home Assistant."
|
||||
date: 2015-11-30 18:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: ecobee.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.9
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
To get your Ecobee sensors working with Home Assistant, follow the instructions for the general [Ecobee component](/components/ecobee/).
|
||||
Loading…
Add table
Add a link
Reference in a new issue