mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-21 08:16:53 +00:00
Add 0.7.3 release blog
This commit is contained in:
Paulus Schoutsen
parent
6beb7b04ef
commit
6c09aee7de
2
_deploy
2
_deploy
@ -1 +1 @@
|
||||
Subproject commit a922794802498d06ecbc2a610ce3088e611bd846
|
||||
Subproject commit 6545a2d395cbab1761794d2814929e154998c05e
|
||||
@ -0,0 +1,73 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Alarms, Sonos and iTunes now supported"
|
||||
description: "Home Assistant 0.7.3 has been released with support for Sonos, iTunes and improved ."
|
||||
date: 2015-09-19 21:47:00 +0700
|
||||
date_formatted: "September 19, 2015"
|
||||
author: Paulus Schoutsen
|
||||
comments: true
|
||||
categories: release-notes
|
||||
---
|
||||
|
||||
It's like someone opened a can of rock solid developers and emptied it above our
|
||||
[chat channel](https://gitter.im/balloob/home-assistant) because it exploded with
|
||||
great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
|
||||
|
||||
See [GitHub](https://github.com/balloob/home-assistant/releases/tag/0.7.3) for more detailed release notes.
|
||||
|
||||
_Migration note: the `scheduler` component has been removed in favor of the `automation` component._
|
||||
|
||||
__Sonos__<br>
|
||||
<img src='/images/supported_brands/sonos.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
Sonos support has been added by [@rhooper](https://github.com/rhooper) and [@SEJeff](https://github.com/SEJeff). Home Assistant is now able to automatically
|
||||
detect Sonos devices in your network and set them up for you. It will allow you to control music
|
||||
playing on your Sonos and change the volume.
|
||||
|
||||
__iTunes and airplay speakers__<br>
|
||||
<img src='/images/supported_brands/itunes.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[@maddox](https://github.com/maddox) has contributed support for controlling iTunes and airplay speakers. For this to work you will
|
||||
have to run [itunes-api](https://github.com/maddox/itunes-api) on your Mac as middleware.
|
||||
|
||||
```
|
||||
# Example configuration.yaml entry
|
||||
media_player:
|
||||
platform: itunes
|
||||
name: iTunes
|
||||
host: http://192.168.1.50
|
||||
port: 8181
|
||||
```
|
||||
|
||||
<!--more-->
|
||||
|
||||
__Automation__<br>
|
||||
Automation has gotten a lot of love. It now supports conditions, multiple triggers and new types of
|
||||
triggers. The best to get started with it is to head over to the new
|
||||
[getting started with automation](/getting-started/automation.html) page.
|
||||
|
||||
```yaml
|
||||
# Example of entry in configuration.yaml
|
||||
automation:
|
||||
alias: Light on in the evening
|
||||
trigger:
|
||||
- platform: sun
|
||||
event: sunset
|
||||
offset: "-01:00:00"
|
||||
- platform: state
|
||||
entity_id: group.all_devices
|
||||
state: home
|
||||
condition:
|
||||
- platform: state
|
||||
entity_id: group.all_devices
|
||||
state: home
|
||||
- platform: time
|
||||
after: "16:00:00"
|
||||
before: "23:00:00"
|
||||
action:
|
||||
service: homeassistant.turn_on
|
||||
entity_id: group.living_room
|
||||
```
|
||||
|
||||
__Verisure Alarms__<br>
|
||||
<img src='/images/supported_brands/verisure.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
We now support arming and disarming your verisure alarm from within Home Assistant thanks to added
|
||||
support by [@persandstrom](https://github.com/persandstrom).
|
||||
@ -17,7 +17,7 @@ A configuration section of an automation requires a `trigger` and an `action` se
|
||||
full configuration but only the relevant part.
|
||||
|
||||
```yaml
|
||||
# Example of a full entry in configuration.yaml
|
||||
# Example of entry in configuration.yaml
|
||||
automation:
|
||||
alias: Light on in the evening
|
||||
trigger:
|
||||
@ -32,8 +32,8 @@ automation:
|
||||
entity_id: group.all_devices
|
||||
state: home
|
||||
- platform: time
|
||||
after: 16:00:00
|
||||
before: 23:00:00
|
||||
after: "16:00:00"
|
||||
before: "23:00:00"
|
||||
action:
|
||||
service: homeassistant.turn_on
|
||||
entity_id: group.living_room
|
||||
@ -101,12 +101,12 @@ automation:
|
||||
platform: state
|
||||
entity_id: device_tracker.paulus
|
||||
# Optional
|
||||
from: not_home
|
||||
to: home
|
||||
from: "not_home"
|
||||
to: "home"
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
Use quotes around your values for <code>state_from</code> and <code>state_to</code> to avoid the YAML parser interpreting some values as booleans.
|
||||
Use quotes around your values for <code>from</code> and <code>to</code> to avoid the YAML parser interpreting some values as booleans.
|
||||
</p>
|
||||
|
||||
#### {% linkable_title Sun trigger %}
|
||||
@ -135,7 +135,7 @@ automation:
|
||||
# All following are optional.
|
||||
# When 'after' is used, you cannot also match on hour, minute, seconds.
|
||||
# Military time format.
|
||||
after: 15:32:00
|
||||
after: "15:32:00"
|
||||
hours: 10
|
||||
minutes: 5
|
||||
seconds: 0
|
||||
@ -199,8 +199,8 @@ automation:
|
||||
condition:
|
||||
platform: time
|
||||
# At least one of the following is required.
|
||||
after: 15:00:00
|
||||
before: 23:00:00
|
||||
after: "15:00:00"
|
||||
before: "23:00:00"
|
||||
weekday:
|
||||
- mon
|
||||
- wed
|
||||
|
||||
@ -10,21 +10,14 @@ footer: true
|
||||
---
|
||||
|
||||
<img src='/images/supported_brands/itunes.png' class='brand pull-right' />
|
||||
The iTunes platform allows you to control [iTunes](http://apple.com/itunes/) via
|
||||
[itunes-api](https://github.com/maddox/itunes-api) from Home Assistant. Play,
|
||||
pause, or skip songs remotely on iTunes running on your Mac.
|
||||
The iTunes platform allows you to control [iTunes](http://apple.com/itunes/) from Home Assistant.
|
||||
It uses a 3rd party server that you run on your Mac called
|
||||
[itunes-api](https://github.com/maddox/itunes-api). Play, pause, or skip songs remotely on iTunes
|
||||
running on your Mac.
|
||||
|
||||
Your AirPlay speakers will also be exposed as simple media players inside Home
|
||||
Assistant. They will be available to be turned on or off or set their volume.
|
||||
|
||||
<p class='note'>
|
||||
iTunes itself can not be remotely controlled. In order to control your iTunes,
|
||||
you'll need to install middleware named itunes-api. itunes-api is a simple REST
|
||||
server that talks to a local instance of iTunes via Applescript. It's very easy to set up
|
||||
and run. You can find more about it on it's [GitHub repo](https://github.com/maddox/itunes-api).
|
||||
</p>
|
||||
|
||||
|
||||
To add iTunes to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
<img src='/images/supported_brands/denon.png' class='brand pull-right' />
|
||||
<img src='/images/supported_brands/sonos.png' class='brand pull-right' />
|
||||
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.
|
||||
|
||||
@ -17,7 +17,7 @@ offers [a few built-in automations](/components/#automation) but mainly you'll b
|
||||
|
||||
Every automation rule consists of triggers, an action to be performed and optional conditions.
|
||||
|
||||
Triggers can be any event observed in Home Assistant. For example, it can be a certain point in time
|
||||
Triggers can be anything observed in Home Assistant. For example, it can be a certain point in time
|
||||
or a person coming home, which can be observed by the state changing from `not_home` to `home`.
|
||||
|
||||
Actions will call services within Home Assistant. For example, turn a light on, set the temperature
|
||||
@ -52,9 +52,13 @@ example tell which device to turn on or what color to use.
|
||||
|
||||
## {% linkable_title Creating your first automation rule %}
|
||||
|
||||
Before we dive deeper into what every piece of automation _can_ do, let's loot at a simple automation
|
||||
Before we dive deeper into what every piece of automation _can_ do, let's look at a simple automation
|
||||
rule: **Turn on the lights when the sun sets**
|
||||
|
||||
In this example, we are defining a trigger to track the sunset and tell it to fire when the sun is
|
||||
setting. When this event is triggered, the service `light.turn_on` is called without any
|
||||
parameters. Because we specify no parameters, it will turn on all the lights.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
automation:
|
||||
@ -66,10 +70,6 @@ automation:
|
||||
service: light.turn_on
|
||||
```
|
||||
|
||||
In this example, we are defining a trigger to track the sunset and tell it to fire one hour before
|
||||
the sun is setting. When this event is triggered, the service `light.turn_on` is called without any
|
||||
parameters. Because we specify no parameters, it will turn on all the lights.
|
||||
|
||||
After a few days of running this automation rule you come to realize that this automation rule is not
|
||||
good enough. It was already dark when the lights went on and the one day you weren't home, the lights
|
||||
turned on anyway. Time for some tweaking. Let's add an offset to the sunset trigger and a condition
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user