home-assistant · fabaff · Jun 16, 2017 · Jun 17, 2017 · Jun 17, 2017 · Jun 17, 2017
diff --git a/Gemfile b/Gemfile
@@ -3,7 +3,7 @@ source "https://rubygems.org"
 group :development do
   gem 'rake', '~> 10.0'
   gem 'jekyll', '~> 3.0'
-  gem 'pygments.rb', '~> 0.6.3'
+  gem 'pygments.rb', '~> 1.1.2'
   gem 'rdiscount', '~> 2.0'
   gem 'RedCloth', '~> 4.2'
   gem 'haml', '~> 4.0'

diff --git a/Gemfile.lock b/Gemfile.lock
@@ -45,6 +45,7 @@ GEM
       rb-inotify (~> 0.9, >= 0.9.7)
     mercenary (0.3.6)
     method_source (0.8.2)
+    multi_json (1.12.1)
     octopress (3.0.11)
       jekyll (>= 2.0)
       mercenary (~> 0.3.2)
@@ -71,14 +72,12 @@ GEM
       jekyll (>= 2.0)
     pathutil (0.14.0)
       forwardable-extended (~> 2.6)
-    posix-spawn (0.3.11)
     pry (0.10.4)
       coderay (~> 1.1.0)
       method_source (~> 0.8.1)
       slop (~> 3.4)
-    pygments.rb (0.6.3)
-      posix-spawn (~> 0.3.6)
-      yajl-ruby (~> 1.2.0)
+    pygments.rb (1.1.2)
+      multi_json (>= 1.0.0)
     rack (1.6.4)
     rack-protection (1.5.3)
       rack
@@ -107,7 +106,6 @@ GEM
       ref
     tilt (2.0.5)
     titlecase (0.1.1)
-    yajl-ruby (1.2.1)
 
 PLATFORMS
   ruby
@@ -127,7 +125,7 @@ DEPENDENCIES
   octopress-filters
   octopress-include-tag
   pry
-  pygments.rb (~> 0.6.3)
+  pygments.rb (~> 1.1.2)
   rake (~> 10.0)
   rb-fsevent (~> 0.9)
   rdiscount (~> 2.0)
@@ -138,4 +136,4 @@ DEPENDENCIES
   therubyracer
 
 BUNDLED WITH
-   1.10.6
+   1.14.6
diff --git a/source/_components/binary_sensor.template.markdown b/source/_components/binary_sensor.template.markdown
@@ -56,36 +56,40 @@ sensor:
 Some movement sensors and door/window sensors will appear as a switch. By using a template binary sensor, the switch can be displayed as a binary sensors. The original switch can then be hidden by [customizing.](/getting-started/customizing-devices/)
 
 ```yaml
-binary_sensor: 
-  - platform: template 
+binary_sensor:
+  - platform: template
     sensors:
       movement:
         value_template: {% raw %}"{{ states.switch.movement.state == 'on' }}"{% endraw %}
         device_class: motion
       door:
-        value_template: {% raw %}"{{ states.switch.door.state == 'on' }}"{% endraw %} 
+        value_template: {% raw %}"{{ states.switch.door.state == 'on' }}"{% endraw %}
         device_class: opening
 ```
 
 
 ### {% linkable_title Combining multiple sensors, and using entity_id: %}
 
-This example combines multiple CO sensors into a single overall status. It also shows how to use `entity_id`
+This example combines multiple CO sensors into a single overall
+status. When using templates with binary sensors, you need to return
+`True` or `False` explicitly. `entity_id` is used to limit which
+sensors are being monitored to update the state, making computing this
+sensor far more efficient.
 
 ```yaml
-binary_sensor: 
-  - platform: template 
+binary_sensor:
+  - platform: template
     sensors:
       co:
         friendly_name: 'CO'
         device_class: 'gas'
         value_template: {% raw %}>-
-          {%- if is_state("sensor.bedroom_co_status", "Ok") 
+          {%- if is_state("sensor.bedroom_co_status", "Ok")
               and is_state("sensor.kitchen_co_status", "Ok")
               and is_state("sensor.wardrobe_co_status", "Ok") -%}
-          Off
+          False
           {%- else -%}
-          On
+          True
           {%- endif %}{% endraw %}
         entity_id:
           - sensor.bedroom_co_status
@@ -104,5 +108,41 @@ sensor:
         friendly_name: 'Day/Night'
         value_template: {% raw %}'{% if is_state("sun.sun", "above_horizon") %}Day{% else %}Night{% endif %}'{% endraw %}
         icon_template: {% raw %}'{% if is_state("sun.sun", "above_horizon") %}mdi:weather-sunny{% else %}mdi:weather-night{% endif %}'{% endraw %}
-
+```
+
+### {% linkable_title Is anyone home? %}
+
+This example is determining if anyone is home based on the combination
+of device tracking and motion sensors. It's extremely useful if you
+have kids / baby sitter / grand parrents who might still be in your
+house that aren't represented by a trackable device in home
+assistant. This is providing a composite of wifi based device tracking
+and z-wave multisensor presence sensors.
+
+```yaml
+binary_sensor:
+  - platform: template
+    sensors:
+      people_home:
+        value_template: {% raw %}>-
+          {%- if is_state("device_tracker.sean", "home")
+          or is_state("device_tracker.susan", "home")
+          or is_state("binary_sensor.office_124", "on")
+          or is_state("binary_sensor.hallway_134", "on")
+          or is_state("binary_sensor.living_room_139", "on")
+          or is_state("binary_sensor.porch_ms6_1_129", "on")
+          or is_state("binary_sensor.family_room_144", "on")
+              -%}
+          True
+          {%- else -%}
+          False
+          {%- endif %}{% endraw %}
+        entity_id:
+          - device_tracker.sean
+          - device_tracker.susan
+          - binary_sensor.office_124
+          - binary_sensor.hallway_134
+          - binary_sensor.living_room_139
+          - binary_sensor.porch_ms6_1_129
+          - binary_sensor.family_room_144
 ```
diff --git a/source/_components/camera.generic.markdown b/source/_components/camera.generic.markdown
@@ -35,6 +35,7 @@ Configuration variables:
 - **password** (*Optional*): The password for accessing your camera.
 - **authentication** (*Optional*): Type for authenticating the requests `basic` (default) or `digest`.
 - **limit_refetch_to_url_change** (*Optional*): True/false value (default: false). Limits refetching of the remote image to when the url changes. Only relevant if using a template to fetch the remote image.
+- **content_type** (*Optional*): Set the content type for the IP camera if it is not a jpg file (default: `image/jpeg`). Use `image/svg+xml` to add a dynamic svg file.
 
 <p class='img'>
   <a href='/cookbook/google_maps_card/'>
@@ -43,3 +44,16 @@ Configuration variables:
   </a>
 </p>
 
+## {% linkable_title Examples %}
+
+In this section you find some real life examples of how to use this camera platform.
+
+### {% linkable_title Weather graph from yr.no %}
+
+```yaml
+camera:
+  - platform: generic
+    name: Weather
+    still_image_url: https://www.yr.no/place/Norway/Oslo/Oslo/Oslo/meteogram.svg
+    content_type: 'image/svg+xml'
+```
diff --git a/source/_components/cover.knx.markdown b/source/_components/cover.knx.markdown
@@ -0,0 +1,34 @@
+---
+layout: page
+title: "KNX Cover"
+description: "Instructions on how to integrate KXN covers with Home Assistant."
+date: 2017-06-18 12:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: knx.png
+ha_category: DIY
+ha_release: 0.48
+ha_iot_class: "Local Polling"
+---
+
+
+The `knx` cover platform is used as in interface with KNX covers.
+
+To use your KNX covers in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+cover:
+  - platform: knx
+    updown_address: 9/0/0
+    stop_address: 9/0/1
+```
+
+- **updown_address** (*Required*): The KNX group address that is used to move the cover up and down.
+- **stop_address** (*Required*): The group address that is used to stop the cover.
+- **setposition_address** (*Optional*): The group address that is used to set the position.
+- **getposition_address** (*Optional*): The group address that is used to read the position.
+- **name** (*Optional*): A name for this devices used within Home Assistant.
+
diff --git a/source/_components/cover.template.markdown b/source/_components/cover.template.markdown
@@ -0,0 +1,77 @@
+---
+layout: page
+title: "Template Cover"
+description: "Instructions how to integrate Template covers into Home Assistant."
+date: 2017-06-19 20:32
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_category: Cover
+ha_release: 0.48
+ha_iot_class: "Local Push"
+logo: home-assistant.png
+---
+
+The `template` platform can create covers that combine components and provides the ability to run scripts or invoke services for each of the open, close, stop, position, and tilt commands of a cover. 
+
+To enable Template covers in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+cover:
+  - platform: template
+    covers:
+      garage_door:
+        friendly_name: "Garage Door"
+        value_template: "{% raw %}{{is_state('sensor.garage_door > 0'}}{% endraw %}"
+        open_cover:
+          service: script.open_garage_door
+        close_cover:
+          service: script.close_garage_door
+        stop_cover:
+          service: script.stop_garage_door
+```
+
+Configuration variables:
+
+- **covers** array (*Required*): List of your coverss.
+  - **open_cover** (*Required*): Defines an [action](/getting-started/automation/) to run when the cover is opened.
+  - **close_cover** (*Required*): Defines an [action](/getting-started/automation/) to run when the cover is closed.
+  - **stop_cover** (*Required*): Defines an [action](/getting-started/automation/) to run when the cover is stopped.
+  - **set_cover_position** (*Optional*): Defines an [action](/getting-started/automation/) to run when the cover is set to a specific value (between 0 and 100).
+  - **set_cover_tilt_position** (*Optional*): Defines an [action](/getting-started/automation/) to run when the cover tilt is set to a specific value (between 0 and 100).
+  - **friendly_name** (*Optional*): Name to use in the frontend.
+  - **value_template** (*Optional*): Defines a [template](/topics/templating/) to get the state of the cover. Valid values are open/true or closed/false. Either `value_template` or `position_template` must be specified.
+  - **position_template** (*Optional*): Defines a [template](/topics/templating/) to get the state of the cover. Legal values are numbers between 0 (closed) and 100 (open). Either `value_template` or `position_template` must be specified.
+  - **icon_template** (*Optional*): Defines a [template](/topics/templating/) to specify which icon to use. Either `value_template` or `position_template` must be specified.
+  - **entity_id** (*Optional*): Add a list of entity IDs so the switch only reacts to state changes of these entities. This will reduce the number of times the cover will try to update it's state.
+
+
+## {% linkable_title Examples %}
+
+In this section you will find some real life examples of how to use this cover.
+
+### {% linkable_title Garage Door %}
+
+This example converts a garage door with a controllable switch and position sensor into a cover.
+
+```yaml
+cover:
+  - platform: template
+    covers:
+      garage_door:
+        friendly_name: 'Garage Door'
+        value_template: "{% raw %}{{ sensor.garage_door }}{% endraw %}"
+        open_cover:
+          service: switch.turn_on
+          entity_is: switch.garage_door
+        close_cover:
+          service: switch.turn_off
+          entity_is: switch.garage_door
+        stop_cover:
+          service: switch.turn_on
+          entity_is: switch.garage_door
+        icon_template: "{% raw %}{% if not is_state('sensor.garage_door', 'on') %}mdi:garage-open{% else %}mdi:garage{% endif %}{% endraw %}"
+
+```
diff --git a/source/_components/device_tracker.linksys_smart.markdown b/source/_components/device_tracker.linksys_smart.markdown
@@ -0,0 +1,31 @@
+---
+layout: page
+title: "Linksys Smart Wifi Router"
+description: "Instructions how to integrate Linksys Smart Wifi Router into Home Assistant."
+date: 2017-06-22 01:40
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_category: Presence Detection
+logo: linksys.png
+ha_release: 0.48
+---
+
+The `linksys_smart` platform offers presence detection by looking at connected devices to a Linksys Smart Wifi based 
+router. It was tested with a LINKSYS WRT3200ACM MU-MIMO Gigabit Wi-Fi Wireless Router.
+
+To use a Linksys Smart Wifi Router in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+  - platform: linksys_smart
+    host: 192.168.1.1
+```
+
+Configuration variables:
+
+- **host** (*Required*): The hostname or IP address of your router, eg. `192.168.1.1`.
+
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/fan.comfoconnect.markdown b/source/_components/fan.comfoconnect.markdown
@@ -0,0 +1,56 @@
+---
+layout: page
+title: "Zehnder ComfoAir Q Ventilation"
+description: "Instructions how to integrate Zehnder ComfoAir Q350/450/600 ventilation systems into Home Assistant."
+date: 2017-06-28 18:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: zehnder.png
+ha_category: Fan
+ha_release: "0.48"
+---
+
+The `comfoconnect` component lets you control Zehnder ComfoAir [Q350](http://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q350-st)/[450](http://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q450-st)/[600](http://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q600-st)
+ventilation units from Home Assistant. You need a [ComfoConnect LAN C](http://www.zehnder.co.uk/products-and-systems/comfortable-indoor-ventilation/ms-comfoair-q/ideal-control#node-21233)
+bridge to connect the unit to your local network.
+
+There is an official iPhone and Android app to configure and control your unit. This platform connects with the help of
+the unofficial [pycomfoconnect](https://github.com/michaelarnauts/comfoconnect) library.
+
+The component has a fan platform to view and control the ventilation speed, and a sensors platform to read out the outdoor temperature and humidity, the indoor temperature and humidity, and the extract and supply air flow (in m³ per hour).
+
+To set it up, add the following information to your `configuration.yaml` file:
+
+```yaml
+climate:
+  - platform: comfoconnect
+    host: 192.168.1.213
+```
+
+Configuration variables:
+
+- **host** (*Required*): The ip or hostname of the ComfoConnect LAN C bridge.
+- **name** (*Optional*): The name of this device as you want to see it in Home Assistant.
+- **token** (*Optional*): The token you want to use when registering with the device. This is a random 32 char hexadecimal string. The default value is `00000000000000000000000000000001`.
+- **user_agent** (*Optional*): The name you want to supply when registering with the device. The default value is `Home Assistant`.
+- **pin** (*Optional*): The pin code to use when registering. This is `0000` by default. You only need to change this if you have changed the factory default pin.
+
+To register the sensors, add the following to your `configuration.yaml` file:
+
+```yaml
+sensor:
+  - platform: comfoconnect
+    resources:
+      - current_temperature
+      - current_humidity
+      - outside_temperature
+      - outside_humidity
+      - air_flow_supply
+      - air_flow_exhaust
+```
+
+<p class='note'>
+Note that it's not possible to have multiple connection to the bridge at the same time. This component will keep the connection open, and if you open the app, it will ask you to disconnect Home Assistant. If you close the app again, Home Assistant will reconnect automatically.
+</p>
diff --git a/source/_components/ha.markdown b/source/_components/ha.markdown
@@ -1,6 +1,6 @@
 ---
 layout: page
-title: "Home Assistant 0.47"
+title: "Home Assistant 0.48"
 description: ""
 date: 2016-12-16 17:00
 sidebar: true
@@ -9,7 +9,7 @@ sharing: true
 footer: true
 logo: home-assistant.png
 ha_category: Other
-ha_release: 0.47
+ha_release: 0.48
 ---
 
 Details about the latest release can always be found at: