mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-17 14:26:51 +00:00
Fix more for 0.23 release
This commit is contained in:
Paulus Schoutsen
parent
ea6304ee6c
commit
bacd4aab21
26
source/_components/garage_door.rpi_gpio.markdown
Normal file
26
source/_components/garage_door.rpi_gpio.markdown
Normal file
@ -0,0 +1,26 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Raspberry Pi Garage door"
|
||||
description: "Instructions how to setup the Raspberry Pi garage doors within Home Assistant."
|
||||
date: 2016-02-12 07:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: wink.png
|
||||
ha_category: Garage Door
|
||||
ha_release: 0.23
|
||||
---
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
garage_door:
|
||||
platform: rpi_gpio
|
||||
doors:
|
||||
- relay_pin: 10
|
||||
state_pin: 11
|
||||
name: 'Left door'
|
||||
- relay_pin: 12
|
||||
state_pin: 13
|
||||
name: 'Right door'
|
||||
```
|
||||
15
source/_components/garage_door.zwave.markdown
Normal file
15
source/_components/garage_door.zwave.markdown
Normal file
@ -0,0 +1,15 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave Garage Door"
|
||||
description: "Instructions how to setup the Z-Wave garage doors within Home Assistant."
|
||||
date: 2015-11-15 13:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: z-wave.png
|
||||
ha_category: Garage Door
|
||||
ha_release: 0.23
|
||||
---
|
||||
|
||||
To get your Z-Wave garage doors working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
|
||||
15
source/_components/rollershutter.zwave.markdown
Normal file
15
source/_components/rollershutter.zwave.markdown
Normal file
@ -0,0 +1,15 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave Rollershutter"
|
||||
description: "Instructions how to setup the Z-Wave rollershutters within Home Assistant."
|
||||
date: 2015-11-15 13:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: z-wave.png
|
||||
ha_category: Rollershutter
|
||||
ha_release: 0.23
|
||||
---
|
||||
|
||||
To get your Z-Wave rollershutters working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
|
||||
@ -10,7 +10,7 @@ comments: true
|
||||
categories: Release-Notes
|
||||
---
|
||||
|
||||
It's time for Home Assistant 0.23 and it's full of goodies. It's also the release that bumps us over a 1000 tests and to 94% test coverage!
|
||||
It's time for Home Assistant 0.23 and it's full of goodies. It's also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.
|
||||
|
||||
This release brings support for two new ecosystems: [Envisalink] and [Homematic]. We can now also control your TV via HDMI using [HDMI-CEC] (which works on the Pi!) and another cool feature is the [persistent notifications] which allow you to add a notification to the frontend till dismissed.
|
||||
|
||||
@ -18,7 +18,7 @@ This release brings support for two new ecosystems: [Envisalink] and [Homematic]
|
||||
|
||||
On the config side, you can now [store your passwords][secrets] in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!
|
||||
|
||||
<img src='/images/supported_brands/eyezon.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/homematic.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/fixer-io.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/openexchangerates.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' />
|
||||
<img src='/images/supported_brands/bravia.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/eyezon.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/homematic.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/fixer-io.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/openexchangerates.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' />
|
||||
|
||||
- Support for [Envisalink] added ([alarm control panel][envi-alarm], [binary sensor][envi-binary-sensor], [sensor][envi-sensor]) ([@cinntax])
|
||||
- Support for [Homematic] added ([binary sensor][hm-binary-sensor], [light][hm-light], [rollershutter][hm-rollershutter], [sensor][hm-sensor], [switch][hm-switch]) ([@pvizeli], [@danielperna84])
|
||||
@ -91,5 +91,6 @@ Breaking changes:
|
||||
[zwave-rollershutter]: /components/rollershutter.zwave/
|
||||
[Fixer.io]: /components/sensor.fixer/
|
||||
[persistent notifications]: /components/persistent_notification/
|
||||
[reload core config service]: /getting-started/XX
|
||||
[reload core config service]: /getting-started/customizing-devices/#reloading-customize
|
||||
[Sony Bravia TV]: /components/media_player.braviatv/
|
||||
[Raspberry Pi GPIO pins]: /components/garage_door.rpi_gpio/
|
||||
|
||||
@ -11,7 +11,7 @@ footer: true
|
||||
|
||||
The `configuration.yaml` file a plain-text file thus it is readable for everyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. This separation can also help you to keep easier track of your passwords and API keys (as they are all stored at one place and no longer spread across the `configuration.yaml` file) if you don't want to [split up your configuration](topics/splitting_configuration/).
|
||||
|
||||
### {% linkable_title `secrets.yaml` %}
|
||||
### {% linkable_title Using secrets.yaml %}
|
||||
|
||||
The workflow for the outsourcing in the `secrets.yaml` are very similar to the [splitting of the configuration](topics/splitting_configuration/). Create a `secrets.yaml` file in your Home assistant configuration directory (The location of the folder differs between operating systems: on OS X and Linux it's `~/.homeassistant` and on Windows it's `%APPDATA%/.homeassistant`).
|
||||
|
||||
|
||||
@ -42,4 +42,12 @@ homeassistant:
|
||||
assumed_state: false
|
||||
```
|
||||
|
||||
### {% linkable_title Reloading customize %}
|
||||
|
||||
Home Assistant offers a service to reload the core configuration while Home Assistant is running called `homeassistant/reload_core_config`. This allows you to change your customize section and see it being applied without having to restart Home Assistant. To call this service, go to the <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> service developer tools, select the service `homeassistant/reload_core_config` and click "Call Service".
|
||||
|
||||
<p class='note warning'>
|
||||
New customize information will be applied the next time the state of the entity gets updated.
|
||||
</p>
|
||||
|
||||
### [Next step: Setting up presence detection »](/getting-started/presence-detection/)
|
||||
|
||||
@ -17,7 +17,6 @@ Usually every entity needs its own entry in the `configuration.yaml` file. There
|
||||
|
||||
#### {% linkable_title Style 1: Collect every entity under the "parent" %}
|
||||
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
- platform: mqtt
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user