Updates for 0.13

This commit is contained in:
Paulus Schoutsen 2016-02-13 00:02:44 -08:00
parent 784f4836d5
commit 944c7a40e4
20 changed files with 132 additions and 26 deletions

View File

@ -0,0 +1,28 @@
---
layout: page
title: "Graphite"
description: "Instructions on how to record Home Assistant history in Graphite."
date: 2016-02-10 17:11
sidebar: true
comments: false
sharing: true
footer: true
logo:
ha_category: History
---
Component that records all events and state changes and feeds the data to
a graphite installation.
Example configuration:
```yaml
# Example configuration.yaml entry
graphite:
host: foobar
port: 2003
prefix: ha
```
All config elements are optional, and assumed to be on localhost at the
default port if not specified. Prefix is the metric prefix in graphite,
and defaults to 'ha'.

View File

@ -18,6 +18,13 @@ Check the **Set State** page from the **Developer Tools** and browse the **Curre
```yaml
# Example configuration.yaml entry
group:
# If you name an entry default_view it will REPLACE the contents of the "Home" tab
default_view:
view: yes
entities:
- group.awesome_people
- group.climate
kitchen:
name: Kitchen
entities:

View File

@ -0,0 +1,15 @@
---
layout: page
title: "MySensors Light"
description: "Instructions how to integrate MySensors lights into Home Assistant."
date: 2016-01-17 15:49
sidebar: true
comments: false
sharing: true
footer: true
logo: mysensors.png
ha_category: Light
featured: false
---
Integrates MySensors lights into Home Assistant. See the [main component] for configuration instructions.

View File

@ -1,6 +1,6 @@
---
layout: page
title: "SCSGate light"
title: "SCSGate Light"
description: "Instructions how to integrate SCSGate lights into Home Assistant."
date: 2016-01-31 19:30
sidebar: true

View File

@ -0,0 +1,23 @@
---
layout: page
title: "snapcast"
description: "Instructions how to integrate a snapcast in Home Assistant."
date: 2016-02-01 19:00
sidebar: true
comments: false
sharing: true
footer: true
logo:
ha_category: Media Player
featured: false
---
The `snapcast` platform allows you to control [Snapcast](https://github.com/badaix/snapcast).
To add Snapcast to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
media_player:
platform: snapcast
```

View File

@ -118,7 +118,25 @@ Home Assistant will automatically load the correct certificate if you connect to
- [OwnTracks Device Tracker](/components/device_tracker.owntracks/)
- [MQTT automation rule](/components/automation/#mqtt-based-automation)
- [MQTT alarm](/components/alarm_control_panel.mqtt/)
- Integrating it into own component. See the [MQTT example component](https://github.com/balloob/home-assistant/blob/dev/config/custom_components/mqtt_example.py) how to do this.
- Integrating it into own component. See the [MQTT example component](/cookbook/python_component_mqtt_basic/) how to do this.
### {% linkable_title Publish service %}
The MQTT component will register the service `publish` which allows publishing messages to MQTT topics. There are two ways of specifiying your payload. You can either use `payload` to hard-code a payload or use `payload_template` to specify a [template](/getting-started/templating/) that will be rendered to generate the payload.
```json
{
"topic": "home-assistant/light/1/command",
"payload": "on"
}
```
```json
{
"topic": "home-assistant/light/1/state",
"payload_template": "{% raw %}{{ states('device_tracker.paulus') }}{% endraw %}"
}
```
## {% linkable_title Testing your setup %}

View File

@ -1,6 +1,6 @@
---
layout: page
title: "SCSGate switch"
title: "SCSGate Switch"
description: "Instructions how to integrate SCSGate switches into Home Assistant."
date: 2016-01-31 22:15
sidebar: true

View File

@ -15,7 +15,7 @@ ha_category: Hub
There is currently support for switches, lights and sensors. All will be picked up automatically after configuring this platform.
### Installation
### {% linkable_title Installation %}
To allow Home Assistant to talk to your Z-Wave USB stick you will have to compile Python Open Z-Wave. This can be done using [this script](https://github.com/balloob/home-assistant/blob/dev/script/build_python_openzwave). _(The Home Assistant docker image has support for Z-Wave built-in)_
@ -26,7 +26,7 @@ $ apt-get install cython3 libudev-dev python-sphinx python3-setuptools
$ pip3 install "cython<0.23"
```
### Configuration
### {% linkable_title Configuration %}
```yaml
# Example configuration.yaml entry
@ -53,7 +53,7 @@ To find the path of your Z-Wave stick, run:
$ ls /dev/ttyUSB*
```
#### Events
#### {% linkable_title Events %}
Some devices can also trigger scene activation events, which can be used in automation scripts (for example the press of a button on a wall switch):

View File

@ -10,8 +10,6 @@ footer: true
ha_category: Automation Examples
---
### {% linkable_title Rainy Day Light %}
This requires a [forecast.io](components/sensor.forecast/) sensor with the condition `weather_precip` that tells if it's raining or not.
Turn on a light in the living room when it starts raining, someone is home, and it's afternoon or later.

View File

@ -1,6 +1,6 @@
---
layout: page
title: "Automation examples using the sun"
title: "Examples using the sun"
description: "Automation examples that use the sun."
date: 2015-10-08 19:05
sidebar: true

View File

@ -1,6 +1,6 @@
---
layout: page
title: "Automation: use_trigger_values"
title: "Example using use_trigger_values"
description: "Basic example how to use use_trigger_values in automation"
date: 2015-10-08 19:05
sidebar: true
@ -10,8 +10,6 @@ footer: true
ha_category: Automation Examples
---
### {% linkable_title Basic example for use_trigger_values %}
Turn on lights during daytime when it's dark enough < 200 lux.
```yaml

View File

@ -7,7 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
ha_category: Full configuration.yaml Examples
ha_category: Example configuration.yaml
ha_external_link: https://gist.github.com/CCOSTAN/9934de973a293b809868
---

View File

@ -7,7 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
ha_category: Full configuration.yaml Examples
ha_category: Example configuration.yaml
ha_external_link: https://github.com/happyleavesaoc/my-home-automation/tree/master/homeassistant
---

View File

@ -0,0 +1,20 @@
---
layout: page
title: "Customize polling interval for any component"
description: "Shows how to customize polling interval for any component via configuration.yaml."
date: 2016-02-12 23:17 -0800
sidebar: true
comments: false
sharing: true
footer: true
ha_category: Example configuration.yaml
---
Platforms that require polling will be polled in an interval specified by the main component. For example a light will check every 30 seconds for a changed state. It is possible to overwrite this scan interval for any platform that is being polled by specifying a `scan_interval` config key. In the example below we setup the Philips Hue lights but tell Home Assistant to poll the devices every 10 seconds instead of the default 30 seconds.
```yaml
# Example configuration.yaml entry to poll Hue lights every 10 seconds.
light:
platform: hue
scan_interval: 10
```

View File

@ -10,10 +10,9 @@ footer: true
ha_category: Automation Examples
---
#### {% linkable_title Send a reminder %}
Always forget to eat lunch? Let Home Assistant send you a reminder.
Add a [notify platform](/components/notify/) of your choice
Add a [notify platform](/components/notify/) of your choice.
```yaml
notify:

View File

@ -10,8 +10,6 @@ footer: true
ha_category: Automation Examples
---
### {% linkable_title Battery level %}
The [iCloud](/components/device_tracker.icloud/) is gathering various details about your device including the battery level. To display it in the Frontend use a [template sensor](/components/sensor.template/).
```yaml

View File

@ -1,6 +1,6 @@
---
layout: page
title: "Motion detected light"
title: "Turn on lights for 10 minutes after motion detected"
description: "Turn on lights for 10 minutes when motion detected."
date: 2015-10-08 19:05
sidebar: true
@ -12,11 +12,11 @@ ha_category: Automation Examples
#### {% linkable_title Turn on lights with a resettable off timer %}
This recipe will turn on a light when there is motion and turn off the light when ten minutes has passed without any motion events .
This recipe will turn on a light when there is motion and turn off the light when ten minutes has passed without any motion events.
```yaml
automation:
alias: Turn on kitchen lights when there is movement
alias: Turn on kitchen lights when there is movement
trigger:
- platform: state
entity_id: sensor.motion_sensor
@ -29,14 +29,14 @@ script:
timed_lamp:
alias: "Turn on lamp and set timer"
sequence:
# Cancel ev. old timers
# Cancel ev. old timers
- execute_service: script.turn_off
service_data:
service_data:
entity_id: script.timer_off
- execute_service: light.turn_on
service_data:
entity_id: light.kitchen
# Set new timer
# Set new timer
- execute_service: script.turn_on
service_data:
entity_id: script.timer_off
@ -47,6 +47,6 @@ script:
- delay:
minutes: 10
- execute_service: light.turn_off
service_data:
service_data:
entity_id: light.kitchen
```

View File

@ -14,6 +14,8 @@
<li>
{% if recipe.url == page.url %}
{{recipe.title}}
{% elsif recipe.ha_external_link %}
<a href='{{recipe.ha_external_link}}'>{{recipe.title}} <i class="icon-external-link"></i></a>
{% else %}
<a href='{{recipe.url}}'>{{recipe.title}}</a>
{% endif %}

View File

@ -30,7 +30,7 @@ Some users keep a public scrubbed copy of their `configuration.yaml` to learn fr
{% for recipe in site.cookbook %}
{% if recipe.ha_category == category %}
{% if recipe.ha_external_link %}
* [{{recipe.title}}]({{recipe.ha_external_link}})
* [{{recipe.title}} <i class="icon-external-link"></i>]({{recipe.ha_external_link}})
{% else %}
* [{{recipe.title}}]({{recipe.url}})
{% endif %}

Binary file not shown.

Before

Width:  |  Height:  |  Size: 42 KiB

After

Width:  |  Height:  |  Size: 18 KiB