+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__
+[@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
+```
+
+
+
+__Automation__
+We now support arming and disarming your verisure alarm from within Home Assistant thanks to added
+support by [@persandstrom](https://github.com/persandstrom).
diff --git a/source/components/automation.markdown b/source/components/automation.markdown
index 07e4a00af6c..a4927480050 100644
--- a/source/components/automation.markdown
+++ b/source/components/automation.markdown
@@ -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"
```
- Use quotes around your values for state_from and state_to to avoid the YAML parser interpreting some values as booleans.
+ Use quotes around your values for from and to to avoid the YAML parser interpreting some values as booleans.
- 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.
--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). -
- - To add iTunes to your installation, add the following to your `configuration.yaml` file: ``` diff --git a/source/components/media_player.sonos.markdown b/source/components/media_player.sonos.markdown index 617c6982d6a..6632add1ea7 100644 --- a/source/components/media_player.sonos.markdown +++ b/source/components/media_player.sonos.markdown @@ -9,7 +9,7 @@ sharing: true footer: true --- -
+
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.
diff --git a/source/getting-started/automation.markdown b/source/getting-started/automation.markdown
index 91ef06394b5..e8afa80b762 100644
--- a/source/getting-started/automation.markdown
+++ b/source/getting-started/automation.markdown
@@ -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