Add blog post 0.22
This commit is contained in:
parent
2a234754ff
commit
de1a60b0f9
8 changed files with 90 additions and 10 deletions
|
@ -270,8 +270,8 @@ First create a file called `alexa_confirm.yaml` with something like the followin
|
|||
{% raw %}
|
||||
>
|
||||
{{ [
|
||||
"OK",
|
||||
"Sure",
|
||||
"OK",
|
||||
"Sure",
|
||||
"If you insist",
|
||||
"Done",
|
||||
"No worries",
|
||||
|
|
|
@ -15,7 +15,7 @@ ha_release: 0.22
|
|||
|
||||
The `local_file` camera platform allows you to integrate any readable image file from disk into Home Assistant as a camera. If the image is updated on the file system the image displayed in Home Assistant will also be updated.
|
||||
|
||||
This can for example be used with various camera platforms that save a temporary images localy.
|
||||
This can for example be used with various camera platforms that save a temporary images locally. It can also be used to display a graph that you render periodacally and will then be displayed in Home Assistant.
|
||||
|
||||
To enable this camera in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
@ -31,7 +31,7 @@ Configuration variables:
|
|||
|
||||
- **name** (*Optional*): Name of the camera
|
||||
- **file_path** (*Required*): File to serve as the camera.
|
||||
|
||||
|
||||
<p class='note'>
|
||||
The given `file_path` must be an existing file because the camera platform setup make a readable check on it.
|
||||
</p>
|
||||
|
|
|
@ -13,7 +13,6 @@ featured: true
|
|||
ha_release: 0.7.3
|
||||
---
|
||||
|
||||
|
||||
The `sonos` platform allows you to control your [Sonos](http://www.sonos.com) HiFi wireless speakers and audio components from Home Assistant.
|
||||
|
||||
To add your Sonos components to your installation, add the following to your `configuration.yaml` file. It will perform auto-discovery of your connected speakers.
|
||||
|
@ -33,3 +32,8 @@ media_player:
|
|||
hosts: IP
|
||||
```
|
||||
|
||||
### {% linkable_title Service %}
|
||||
|
||||
There are two extra services exposed that will allow you to take a snapshot of what is currently playing and restore it afterwards. This is useful if you want to play a doorbell or notification sound and resume playback afterwards.
|
||||
|
||||
The services are called `sonos_snapshot` and `snapshot_restore`.
|
||||
|
|
|
@ -27,7 +27,9 @@ Configuration variables:
|
|||
- Alias for the command
|
||||
- Command itself.
|
||||
|
||||
The commands can be dynamic, using templates to insert values of other entities. For example
|
||||
The commands can be dynamic, using templates to insert values of other entities. When using templates you are limited to only template the arguments. You are also no longer allowed to use pipe symbols when using templates.
|
||||
|
||||
Any service data passed into the service call to activate the shell command will be available as a variable within the template.
|
||||
|
||||
```yaml
|
||||
# Apply value of a GUI slider to the shell_command
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue