home-assistant · fabaff · Oct 22, 2016 · Oct 8, 2016 · Oct 8, 2016 · Oct 9, 2016
diff --git a/source/_components/alarm_control_panel.concord232.markdown b/source/_components/alarm_control_panel.concord232.markdown
@@ -0,0 +1,29 @@
+---
+layout: page
+title: "Concord232 Alarm Control Panel"
+description: "Instructions how to integrate Interlogix/GE Concord4 with RS-232 Automation Control Module into Home Assistant."
+date: 2016-10-11 10:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: interlogix.png
+ha_category: Alarm
+ha_release: 0.31
+---
+
+The `concord232` platform provides integration with GE, Interlogix (and other brands) alarm panels that support the RS-232 Automation Control Panel interface module (or have it built in). Supported panels include Concord 4.
+
+To enable this, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+alarm_control_panel:
+  - platform: concord232
+```
+
+Configuration variables:
+
+- **host** (*Optional*): The host where the concord232 server process is running. Defaults to localhost.
+- **port** (*Optional*): The port where the Alarm panel ist listening. Defaults to 5007.
+
diff --git a/source/_components/alexa.markdown b/source/_components/alexa.markdown
@@ -12,9 +12,13 @@ ha_category: Voice
 featured: true
 ---
 
-There are two ways that you can use Amazon Echo and Home Assistant together.
+There are a few ways that you can use Amazon Echo and Home Assistant together.
 
-No matter which method(s) you decide to use, please remember that Amazon Echo requires an active Internet connection to function. If your Internet is down or experiencing issues (or Amazon's infrastructure is having issues), neither of these methods will work.
+- [Turning devices on and off](#i-just-want-to-turn-devices-on-and-off-using-echo)
+- [Build custom commands to use](#i-want-to-build-custom-commands-to-use-with-echo)
+- [Create a new Flash Briefing source](#flash-briefing-skills)
+
+No matter which method(s) you decide to use, please remember that Amazon Echo requires an active Internet connection to function. If your Internet is down or experiencing issues (or Amazon's infrastructure is having issues), none of these methods will work.
 
 Amazon has released [Echosim], a website that simulates the Alexa service in your browser. That way it is easy to test your skills without having access to a physical Amazon Echo.
 
@@ -56,22 +60,25 @@ The built-in Alexa component allows you to integrate Home Assistant into Alexa/A
 
 ### {% linkable_title Requirements %}
 
-Amazon requires the endpoint of a skill to be hosted via SSL. Self-signed certificates are ok because our skills will only run in development mode. Read more on [our blog][blog-lets-encrypt] about how to set up encryption for Home Assistant. If you are unable to get HTTPS up and running, consider using [this AWS Lambda proxy for Alexa skills](https://forums.developer.amazon.com/forums/thread.jspa?messageID=18604).
+Amazon requires the endpoint of a skill to be hosted via SSL. Self-signed certificates are ok because our skills will only run in development mode. Read more on [our blog][blog-lets-encrypt] about how to set up encryption for Home Assistant. If you are unable to get HTTPS up and running, consider using [this AWS Lambda proxy for Alexa skills](https://community.home-assistant.io/t/aws-lambda-proxy-custom-alexa-skill-when-you-dont-have-https/5230).
 
 [blog-lets-encrypt]: https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/
 
 To get started with Alexa skills:
 
- - Log in to [Amazon developer console](https://developer.amazon.com)
- - Go to Apps & Services => Alexa => Alexa Skill Kit - Get Started
- - Add a new skill
+ - Log in to [Amazon developer console][amazon-dev-console]
+ - Click the Alexa button at the top of the console
+ - Click the yellow "Add a new skill" button in the top right
+   - Skill Type: Custom Interaction Model (default)
    - Name: Home Assistant
    - Invocation name: home assistant (or be creative, up to you)
    - Version: 1.0
    - Endpoint:
      - https
      - https://YOUR_HOST/api/alexa?api_password=YOUR_API_PASSWORD
 
+You can use this [specially sized Home Assistant logo][large-icon] as the large icon and [this one][small-icon] as the small one.
+
 ### {% linkable_title Configuring your Amazon Alexa skill %}
 
 Alexa works based on intents. Each intent has a name and variable slots. For example, a `LocateIntent` with a slot that contains a `User`. Example intent schema:
@@ -119,7 +126,6 @@ You can use [templates] for the values of `speech/text`, `card/title` and `card/
 
 Actions are using the [Home Assistant Script Syntax] and also have access to the variables from the intent.
 
-[templates]: /topics/templating/
 [Home Assistant Script Syntax]: /getting-started/scripts/
 
 Configuring the Alexa component for the above intents would look like this:
@@ -256,7 +262,7 @@ Then add the intent to your Alexa Section in your HA config file:
 
 Now say `Alexa ask homeassistant to run <some script>` and Alexa will run that script for you.
 
-## {% linkable_title Giving Alexa Some Personality%}
+## {% linkable_title Giving Alexa Some Personality %}
 
 In the examples above, we told Alexa to say `OK` when she successfully completed the task. This is effective but a little dull! We can again use [templates] to spice things up a little.
 
@@ -298,3 +304,57 @@ text: !include alexa_confirm.yaml
 Alexa will now respond with a random phrase each time. You can use the include for as many different intents as you like so you only need to create the list once.
 
 
+## {% linkable_title Flash Briefing Skills %}
+
+As of version [0.31][zero-three-one] Home Assistant supports the new [Alexa Flash Briefing Skills API][flash-briefing-api]. A Flash Briefing Skill adds a new Flash Briefing source that is generated by Home Assistant.
+
+### {% linkable_title Configuring a Flash Briefing skill in Home Assistant %}
+
+You can use [templates] for the `title`, `audio`, `text` and `display_url` configuration parameters.
+
+Here's an example configuration of a Flash briefing skill that will tell you who is at home:
+
+```yaml
+{% raw %}# Example configuration.yaml entry
+alexa:
+  flash_briefings:
+    whoishome:
+      - title: Who's at home?
+        text: >
+          {%- if is_state('device_tracker.paulus', 'home') and
+                 is_state('device_tracker.anne_therese', 'home') -%}
+            You are both home, you silly
+          {%- else -%}
+            Anne Therese is at {{ states("device_tracker.anne_therese") }}
+            and Paulus is at {{ states("device_tracker.paulus") }}
+          {% endif %}{% endraw %}
+```
+
+You can add multiple items for a feed if you want. The Amazon required uid and timestamp will be randomly generated at startup and change at every restart of Home Assistant.
+
+Please refer to the [Amazon documentation][flash-briefing-api-docs] for more information about allowed configuration parameters and formats.
+
+### {% linkable_title Configuring your Flash Briefing skill %}
+
+- Log in to [Amazon developer console][amazon-dev-console]
+- Click the Alexa button at the top of the console
+- Click the yellow "Add a new skill" button in the top right
+  - Skill Information
+    - For Skill Type select Flash Briefing Skill API
+    - You can enter whatever name you want
+    - Hit next
+  - Interaction Model
+    - Nothing to do here
+  - Configuration
+    - Add new feed
+      - For URL, enter `https://YOUR_HOST/api/alexa/flash_briefings/BRIEFING_ID?api_password=YOUR_API_PASSWORD` where `BRIEFING_ID` is the key you entered in your configuration (such as `whoishome` in the above example)
+      - You can use this [specially sized Home Assistant logo][large-icon] as the Feed Icon
+      - All other settings are up to you
+
+[amazon-dev-console]: https://developer.amazon.com
+[flash-briefing-api]: https://developer.amazon.com/alexa-skills-kit/flash-briefing
+[flash-briefing-api-docs]: https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/flash-briefing-skill-api-feed-reference
+[large-icon]: /images/components/alexa/alexa-512x512.png
+[small-icon]: /images/components/alexa/alexa-108x108.png
+[templates]: /topics/templating/
+[zero-three-one]: /blog/2016/10/22/flash-briefing-updater-hacktoberfest/
diff --git a/source/_components/binary_sensor.concord232.markdown b/source/_components/binary_sensor.concord232.markdown
@@ -0,0 +1,29 @@
+---
+layout: page
+title: "Concord232 Binary Sensor"
+description: "Instructions how to integrate Interlogix/GE Concord4 binary sensors into Home Assistant."
+date: 2016-10-11 10:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: interlogix.png
+ha_category: Binary sensor
+ha_release: 0.31
+---
+
+The `concord232` platform provides integration with GE, Interlogix (and other brands) alarm panels that support the RS-232 Automation Control Panel interface module (or have it built in). Supported panels include Concord 4.
+
+To enable this, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+binary_sensor:
+  - platform: concord232
+```
+
+Configuration variables:
+
+- **host** (*Optional*): The host where the concord232 server process is running. Defaults to localhost.
+- **port** (*Optional*): The port where the Alarm panel ist listening. Defaults to 5007.
+
diff --git a/source/_components/binary_sensor.netatmo.markdown b/source/_components/binary_sensor.netatmo.markdown
@@ -0,0 +1,52 @@
+---
+layout: page
+title: "Netatmo Binary Sensor"
+description: "Instructions how to integrate Netatmo binary sensor into Home Assistant."
+date: 2016-09-19 15:10
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: netatmo.png
+ha_category: Binary Sensor
+ha_release: 0.31
+---
+
+### {% linkable_title Basic Configuration %}
+
+The `netatmo` binary sensor platform is consuming the information provided by a [Netatmo Welcome](https://www.netatmo.com) camera. This component allows you to get the latest event seen by the camera.
+
+To enable the Netatmo binary sensor, you have to set up [netatmo](/components/netatmo/), this will use discovery to add your binary sensor.
+
+### {% linkable_title Advanced configuration %}
+
+If you want to select a specific sensor, set discovery to False for [netatmo](/components/netatmo/) and add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+binary_sensor:
+  platform: netatmo
+  home: home_name
+  cameras:
+    - camera_name1
+  monitored_conditions:
+    - Someone known
+    - Someone unknown 
+    - Motion
+```
+
+Configuration variables:
+
+- **home** (*Optional*): Will use the cameras of this home only.
+- **cameras** array (*Optional*): Cameras to use. Multiple enties allowed.
+    - 'camera_name': Name of the camera to display.
+- **monitored_conditions** array (*Optional*): List of monitored conditions.
+    - 'Someone known'
+    - 'Someone unknown'
+    - 'Motion'
+
+If **home** and **cameras** is not provided, all cameras will be used. If multiple cameras are available then each monitored conditions will create a specific sensor for each camera
+
+<p class='note'>
+[Welcome tags](https://www.netatmo.com/product/security/welcome/tags) are not yet supported, but will be in a next update.
+</p>
diff --git a/source/_components/camera.netatmo.markdown b/source/_components/camera.netatmo.markdown
@@ -12,10 +12,15 @@ ha_category: Camera
 ha_release: 0.22
 ---
 
+### {% linkable_title Basic Configuration %}
 
 The `netatmo` camera platform is consuming the information provided by a [Netatmo Welcome](https://www.netatmo.com) camera. This component allows you to view the current photo created by the Camera.
 
-To enable the Netatmo camera, you first have to set up [netatmo](/components/netatmo/), and add the following lines to your `configuration.yaml`:
+To enable the Netatmo camera, you have to set up [netatmo](/components/netatmo/), this will use discovery to add your camera.
+
+### {% linkable_title Advanced configuration %}
+
+If you want to select a specific camera, set discovery to False for [netatmo](/components/netatmo/) and add the following lines to your `configuration.yaml`:
 
 ```yaml
 # Example configuration.yaml entry

diff --git a/source/_components/camera.synology.markdown b/source/_components/camera.synology.markdown
@@ -0,0 +1,51 @@
+---
+layout: page
+title: "Synology Camera"
+description: "Instructions how to integrate Synolog Surveillance Station cameras within Home Assistant."
+date: 2016-10-13 08:01
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: synology.png
+ha_category: Camera
+ha_release: 0.31
+---
+
+
+The `synology` platform allows you to watch the live streams of your [Synology](https://www.synology.com/) Surveillance Station based IP cameras in Home Assistant.
+
+To enable your Surveillance Station cameras in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Minimum configuration.yaml entry
+camera:
+  - platform: synology
+    url: SYNOLOGY_URL
+    username: USERNAME
+    password: PASSWORD
+```
+
+Configuration variables:
+
+- **url** (*Required*): The URL to your synology, including port.
+- **username** (*Required*): The username for accessing surveillance station.
+- **password** (*Required*): The password for accessing surveillance station.
+- **whitelist** (*Optional*): A list of which cameras you want to add, the names must be the same as in Surveillance Station.  If omited all cameras are added.
+- **verify_ssl** (*Optional*): True to require a valid certificate, False to disable certificate checking. Defaults to `True`.
+
+A full sample configuration for the `synology` platform is shown below:
+
+```yaml
+# Example configuration.yaml entry
+camera:
+  - platform: synology
+    url: https://192.168.1.120:5001
+    username: USERNAME
+    password: PASSWORD
+    verify_ssl: False
+```
+
+<p class='note'>
+Most users will need to set `valid_ssl` to false unless they have installed a valid SSL certificate in place of the built in self-signed certificate.
+</p>
diff --git a/source/_components/camera.verisure.markdown b/source/_components/camera.verisure.markdown
@@ -0,0 +1,19 @@
+---
+layout: page
+title: "Verisure Camera"
+description: "Instructions how to setup the Verisure cameras within Home Assistant."
+date: 2016-10-22 09:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: verisure.png
+ha_category: Camera
+ha_release: 0.31
+---
+
+
+The `verisure` camera platform allows you to control your [Verisure](https://www.verisure.com/) cameras.
+
+The requirement is that you have setup your [Verisure hub](/components/verisure/).
+
diff --git a/source/_components/climate.netatmo.markdown b/source/_components/climate.netatmo.markdown
@@ -0,0 +1,46 @@
+---
+layout: page
+title: "Netatmo Thermostat"
+description: "Instructions how to integrate Netatmo thermostat into Home Assistant."
+date: 2016-11-10 08:10
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: netatmo.png
+ha_category: Climate
+ha_release: 0.31
+---
+
+### {% linkable_title Basic Configuration %}
+
+The `netatmo` thermostat platform is consuming the information provided by a [Netatmo Smart Thermostat](https://www.netatmo.com/product/energy/thermostat) thermostat. This component allows you to view the current temperature and setpoint.
+
+To enable the Netatmo thermostat, you first have to set up [netatmo](/components/netatmo/), this will use discovery to add your thermostat.
+
+### {% linkable_title Basic Configuration %}
+
+If you want to select a specific thermostat, set discovery to False for [netatmo](/components/netatmo/) and add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+climate:
+  platform: netatmo
+```
+
+Configuration variables:
+
+- **relay** (*Optional*): Will display the thermostats of this relay only.
+- **thermostat** array (*Optional*): Thermostat to use.
+    - **thermostat_name**: Name of the thermostat to display.
+
+If **relay** and **thermostat** are not provided, all thermostats will be displayed.
+
+```yaml
+# Example configuration.yaml entry
+climate:
+  platform: netatmo
+  relay: relay_name
+  thermostat:
+    - thermostat_name
+```