Skip to content

Commit 8fc3193

Browse files
committed
Release 0.47
1 parent 52f2dda commit 8fc3193

11 files changed

+597
-25
lines changed

source/_components/mailgun.markdown

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
layout: page
3+
title: "Mailgun"
4+
description: "Instructions how to add Mailgun mail notifications to Home Assistant."
5+
date: 2017-02-06 16:52
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: mailgun.png
11+
ha_category: Notifications
12+
ha_release: 0.38
13+
---
14+
15+
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>`
16+
17+
To send messages, use the [Mailgun notify platform][notify].
18+
19+
[notify]: /components/notify.mailgun/
20+
21+
## {% linkable_title Sample configuration %}
22+
23+
```yaml
24+
# Example configuration.yaml entry
25+
mailgun:
26+
domain: mg.example.com
27+
api_key: token-XXXXXXXXX
28+
sandbox: False
29+
```
30+
31+
Configuration variables:
32+
33+
- **domain** (*Optional*): This is the domain name to be used when sending out mail. Defaults to the first custom domain you have set up.
34+
- **sandbox** (*Optional*): Whether to use the sandboxed domain for outgoing mail. The `domain` item takes precedence over this. Defaults to `False`.
35+
- **api_key** (*Required*): This is the API token that has been generated in your Mailgun account.

source/_components/notify.mailgun.markdown

Lines changed: 11 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
layout: page
3-
title: "Mailgun"
3+
title: "Mailgun Notify"
44
description: "Instructions how to add Mailgun mail notifications to Home Assistant."
55
date: 2017-02-06 16:52
66
sidebar: true
@@ -12,18 +12,23 @@ ha_category: Notifications
1212
ha_release: 0.38
1313
---
1414

15-
The Mailgun notification service allows you to send emails via Mailgun's REST API.
15+
The Mailgun notification service allows you to send emails via Mailgun's REST API. It requires the [Mailgun component] to be set up.
16+
17+
[Mailgun component]: /components/mailgun/
1618

1719
## {% linkable_title Sample configuration %}
1820

1921
```yaml
2022
# Example configuration.yaml entry
23+
mailgun:
24+
domain: mg.example.com
25+
api_key: token-XXXXXXXXX
26+
sandbox: False
27+
2128
notify:
22-
- name: NOTIFIER_NAME
29+
- name: mailgun
2330
platform: mailgun
24-
domain: YOUR_MAILGUN_DOMAIN
25-
token: TOKEN
26-
recipient: RECIPIENT_EMAIL
31+
recipient: me@example.com
2732
```
2833
2934
Configuration variables:
@@ -34,21 +39,6 @@ Configuration variables:
3439
- **recipient** (*Required*): The email address of the recipient.
3540
- **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.
3641

37-
## {% linkable_title Full configuration %}
38-
39-
A full configuration example for the Mailgun notifier system can look like this:
40-
41-
```yaml
42-
# Example configuration.yaml entry
43-
notify:
44-
- name: mailgun
45-
platform: mailgun
46-
domain: mg.example.com
47-
sanbox: False
48-
token: 'token-XXXXXXXXX'
49-
recipient: me@example.com
50-
```
51-
5242
## {% linkable_title Example automation %}
5343

5444
The following automation reacts to an event by sending out an email with two attachments.

source/_components/python_script.markdown

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,16 @@ ha_category: Automation
1212
ha_release: 0.47
1313
---
1414

15-
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`.
15+
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:
16+
17+
| Name | Description |
18+
| ---- | ----------- |
19+
| `hass` | The Home Assistant object. Access is only allowed to call services, set/remove states and fire events. [API reference][hass-api]
20+
| `data` | The data passed to the Python Script service call.
21+
| `logger` | A logger to allow you to log messages: `logger.info()`, `logger.warning()`, `logger.error()`. [API reference][logger-api]
22+
23+
[hass-api]: https://home-assistant.io/developers/development_hass_object/
24+
[logger-api]: https://docs.python.org/3.4/library/logging.html#logger-objects
1625

1726
## {% linkable_title Writing your first script %}
1827

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
layout: page
3+
title: "Ecobee Sensor"
4+
description: "Instructions how to setup the Ecobee sensors within Home Assistant."
5+
date: 2015-11-30 18:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: ecobee.png
11+
ha_category: Binary Sensor
12+
ha_release: 0.9
13+
ha_iot_class: "Local Push"
14+
---
15+
16+
To get your Ecobee sensors working with Home Assistant, follow the instructions for the general [Ecobee component](/components/ecobee/).

source/_posts/2017-05-06-zigbee-opencv-dlib.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ categories: Release-Notes
1111
og_image: /images/blog/2017-05-0.44/components.png
1212
---
1313

14-
<a href='/components/#added_in_current_version'><img src='/images/blog/2017-05-0.44/components.png' style='border: 0;box-shadow: none;'></a>
14+
<a href='/components/#version/0.44'><img src='/images/blog/2017-05-0.44/components.png' style='border: 0;box-shadow: none;'></a>
1515

1616
This release brings some great new integrations. The biggest one is the [native ZigBee integration][zha docs] by [Russell Cloran][@rcloran]. This will allow Home Assistant to natively control Philips Hue lights without the need for a hub! (IKEA Tradfri lights not yet due to implementing a different profile)
1717

source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ categories: Release-Notes
1111
og_image: /images/blog/2017-05-0.45/components.png
1212
---
1313

14-
<a href='/components/#added_in_current_version'><img src='/images/blog/2017-05-0.45/components.png' style='border: 0;box-shadow: none;'></a>
14+
<a href='/components/#version/0.45'><img src='/images/blog/2017-05-0.45/components.png' style='border: 0;box-shadow: none;'></a>
1515

1616
Welcome to another great release of Home Assistant! While some of contributors and users are gathering at PyCon US 2017, we still managed to get a great release together!
1717

source/_posts/2017-06-04-release-46.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ categories: Release-Notes
1111
og_image: /images/blog/2017-06-0.46/components.png
1212
---
1313

14-
<a href='/components/#added_in_current_version'><img src='/images/blog/2017-06-0.46/components.png' style='border: 0;box-shadow: none;'></a>
14+
<a href='/components/#version/0.46'><img src='/images/blog/2017-06-0.46/components.png' style='border: 0;box-shadow: none;'></a>
1515

1616
It's time for 0.46! This release does not have too many new integrations, instead it focussed on bug fixes.
1717

0 commit comments

Comments
 (0)