Merge remote-tracking branch 'origin/master' into next

Conflicts: source/getting-started/automation.markdown
2025-07-23 17:27:19 +00:00 · 2016-05-01 23:34:04 -07:00 · 2016-05-01 23:34:04 -07:00 · de586c5433
commit de586c5433
parent 4be4102776 16ac0e8dfb
120 changed files with 305 additions and 18 deletions
--- a/sass/custom/_paulus.scss
+++ b/sass/custom/_paulus.scss
@ -159,6 +159,10 @@ article.post, article.page, article.listing {
      text-decoration: none;
    }
  }
  .frontpage a {
    text-decoration: none;
  }
 }
 p.note {
--- a/source/_components/alarm_control_panel.alarmdotcom.markdown
+++ b/source/_components/alarm_control_panel.alarmdotcom.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: alarmdotcom.png
 ha_category: Alarm
 ha_release: 0.11
 ---
 The `alarmdotcom` platform is consuming the information provided by a [Alarm.com](https://www.alarm.com/).
--- a/source/_components/alarm_control_panel.manual.markdown
+++ b/source/_components/alarm_control_panel.manual.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Alarm
 ha_release: 0.7.6
 ---
--- a/source/_components/apcupsd.markdown
+++ b/source/_components/apcupsd.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: apcupsd.png
 ha_category: Hub
 ha_release: 0.13
 ---
 [APCUPSd](http://www.apcupsd.org/) status information can be integrated into Home Assistant when the Network Information Server (NIS) [is configured](http://www.apcupsd.org/manual/manual.html#nis-server-client-configuration-using-the-net-driver) is enabled on the APC device.
--- a/source/_components/binary_sensor.apcupsd.markdown
+++ b/source/_components/binary_sensor.apcupsd.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: apcupsd.png
 ha_category: Binary Sensor
 ha_release: 0.13
 ---
 In addition to the [APCUPSd Sensor](/components/sensor.apcupsd/) devices, you may also create a device which is simply "on" when the UPS status is online and "off" at all other times.
--- a/source/_components/binary_sensor.arest.markdown
+++ b/source/_components/binary_sensor.arest.markdown
@ -10,6 +10,7 @@ footer: true
 logo: arest.png
 ha_category: Binary Sensor
 ha_iot_class: "Local Polling"
 ha_release: 0.9
 ---
--- a/source/_components/binary_sensor.bloomsky.markdown
+++ b/source/_components/binary_sensor.bloomsky.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: bloomsky.png
 ha_category: Binary Sensor
 ha_release: 0.14
 ---
 The `bloomsky` binary sensor platform allows you to get data from your BloomSky device.
--- a/source/_components/binary_sensor.command_line.markdown
+++ b/source/_components/binary_sensor.command_line.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: command_line.png
 ha_category: Binary Sensor
 ha_release: 0.12
 ---
--- a/source/_components/binary_sensor.mqtt.markdown
+++ b/source/_components/binary_sensor.mqtt.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: mqtt.png
 ha_category: Binary Sensor
 ha_release: 0.9
 ---
--- a/source/_components/binary_sensor.mysensors.markdown
+++ b/source/_components/binary_sensor.mysensors.markdown
@ -9,7 +9,7 @@ sharing: true
 footer: true
 logo: mysensors.png
 ha_category: Binary Sensor
-featured: false
+ha_release: 0.14
 ---
 Integrates MySensors binary sensors into Home Assistant. See the [main component] for configuration instructions.
--- a/source/_components/binary_sensor.nx584.markdown
+++ b/source/_components/binary_sensor.nx584.markdown
@ -10,6 +10,7 @@ footer: true
 logo: networx.png
 ha_category: Binary Sensor
 ha_iot_class: "Local Push"
 ha_release: 0.14
 ---
 The `nx584` platform provides integration with GE, Caddx, Interlogix (and other brands) alarm panels that support the NX584 interface module (or have it built in). Supported panels include NX4/6/8/8E. Actual integration is done through [pynx584](http://github.com/kk7ds/pynx584) which is required for this to work.
--- a/source/_components/binary_sensor.rest.markdown
+++ b/source/_components/binary_sensor.rest.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Binary Sensor
 ha_release: 0.10
 ---
--- a/source/_components/binary_sensor.tcp.markdown
+++ b/source/_components/binary_sensor.tcp.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Binary Sensor
 ha_release: 0.14
 ---
 The TCP Binary Sensor is a type of [TCP Sensor](/components/sensor.tcp/) which is either "off" or "on". In order to use this sensor type, in addition to the configuration for the TCP Sensor, you must supply a `value_on` value to represent what is returned when the device is turned on.
--- a/source/_components/binary_sensor.wink.markdown
+++ b/source/_components/binary_sensor.wink.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: wink.png
 ha_category: Binary Sensor
 ha_release: 0.14
 ---
--- a/source/_components/binary_sensor.zwave.markdown
+++ b/source/_components/binary_sensor.zwave.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: z-wave.png
 ha_category: Binary Sensor
 ha_release: 0.14
 ---
 To get your Z-Wave binary sensors working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
--- a/source/_components/camera.rpi_camera.markdown
+++ b/source/_components/camera.rpi_camera.markdown
@ -10,6 +10,7 @@ footer: true
 logo: raspberry-pi.png
 ha_category: Camera
 ha_iot_class: "Local Polling"
 ha_release: 0.17
 ---
--- a/source/_components/camera.uvc.markdown
+++ b/source/_components/camera.uvc.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: ubiquiti.png
 ha_category: Camera
 ha_release: 0.13
 ---
--- a/source/_components/device_tracker.aruba.markdown
+++ b/source/_components/device_tracker.aruba.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: aruba.png
 ha_category: Presence Detection
 ha_release: 0.7
 ---
--- a/source/_components/device_tracker.bluetooth_tracker.markdown
+++ b/source/_components/device_tracker.bluetooth_tracker.markdown
@ -10,6 +10,7 @@ footer: true
 logo: bluetooth.png
 ha_category: Presence Detection
 ha_iot_class: "Local Poll"
 ha_release: 0.18
 ---
 This tracker discovers new devices on boot and tracks bluetooth devices periodically based on interval_seconds value. Devices discovered are stored with 'bt_' as the prefix for device mac in `known_devices.yaml`.
--- a/source/_components/device_tracker.fritz.markdown
+++ b/source/_components/device_tracker.fritz.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: avm.png
 ha_category: Presence Detection
 ha_release: 0.10
 ---
--- a/source/_components/device_tracker.icloud.markdown
+++ b/source/_components/device_tracker.icloud.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: icloud.png
 ha_category: Presence Detection
 ha_release: 0.10
 ---
--- a/source/_components/device_tracker.netgear.markdown
+++ b/source/_components/device_tracker.netgear.markdown
@ -24,6 +24,7 @@ device_tracker:
  host: YOUR_ROUTER_IP
  username: YOUR_ADMIN_USERNAME
  password: YOUR_ADMIN_PASSWORD
  port: YOUR_ROUTER_PORT
 ```
 Configuration variables:
@ -31,5 +32,6 @@ Configuration variables:
 - **host** (*Required*): The IP address of your router, e.g. 192.168.1.1.
 - **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
 - **password** (*Required*): The password for your given admin account.
 - **port** (*Optional*): The port your router communicates with (defaults to 5000, but 80 is also known to be used on some models)
 See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
--- a/source/_components/device_tracker.snmp.markdown
+++ b/source/_components/device_tracker.snmp.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: network-snmp.png
 ha_category: Presence Detection
 ha_release: 0.7.5
 ---
--- a/source/_components/device_tracker.ubus.markdown
+++ b/source/_components/device_tracker.ubus.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: openwrt.png
 ha_category: Presence Detection
 ha_release: 0.7.6
 ---
 _This is one of the two ways we support OpenWRT. If you encounter problems, try [luci](/components/device_tracker.luci/)._
--- a/source/_components/device_tracker.unifi.markdown
+++ b/source/_components/device_tracker.unifi.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: ubiquiti.png
 ha_category: Presence Detection
 ha_release: 0.14
 ---
--- a/source/_components/feedreader.markdown
+++ b/source/_components/feedreader.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: rss.gif
 ha_category: Other
 ha_release: 0.18
 ---
 Add an RSS/Atom feed reader that polls feeds every hour and sends new entries into the event bus.
@ -26,3 +27,25 @@ feedreader:
 Configuration variables:
 - **urls** (*Required*): List of URLS for your feeds.
 Feedreader events can be used out of the box to trigger automation actions, e.g.:
 ```yaml
 automation:
  - alias: Trigger action when new element(s) in RSS feed
    trigger:
      platform: event
      event_type: feedreader
    action:
      service: script.turn_on
      entity_id: script.my_action
 ```
 For more advanced use cases, a custom component registering to the `feedreader` event type could be used instead:
 ```python
 EVENT_FEEDREADER = "feedreader"
 hass.bus.listen(EVENT_FEEDREADER, event_listener)
 ```
 To get started developing custom components, please refer to the [developers](/developers) documentation
--- a/source/_components/garage_door.mqtt.markdown
+++ b/source/_components/garage_door.mqtt.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: mqtt.png
 ha_category: Garage Door
 ha_release: 0.18
 ---
--- a/source/_components/garage_door.wink.markdown
+++ b/source/_components/garage_door.wink.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: wink.png
 ha_category: Garage Door
 ha_release: 0.13
 ---
 Wink garage door functionality is currently limited to view only. Wink garage doors will still show the current state of the door, but control has been disabled for third parties. If you have a Chamberlain garage door, and would like to control it via Home Assistant, please contact Chamberlain and request that they re-enabled third-party control.
--- a/source/_components/graphite.markdown
+++ b/source/_components/graphite.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: 
 ha_category: History
 ha_release: 0.13
 ---
 The `graphite` component records all events and state changes and feeds the data to a [graphite](http://graphite.wikidot.com/) instance.
--- a/source/_components/influxdb.markdown
+++ b/source/_components/influxdb.markdown
@ -10,6 +10,7 @@ footer: true
 logo: influxdb.png
 ha_category: "History"
 featured: true
 ha_release: 0.9
 ---
 The `influxdb` component makes it possible to transfer all state changes to an external [InfluxDB](https://influxdb.com/) database. For more details, [see the blog post on InfluxDB](/blog/2015/12/07/influxdb-and-grafana/).
--- a/source/_components/input_select.markdown
+++ b/source/_components/input_select.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: home-assistant.png
 ha_category: Automation
 ha_release: 0.13
 ---
 The `input_select` component allows the user to define a list of values that can be selected via the frontend and can be used within conditions of automation. When a user selectes a new item, a state transition event is generated. This state event can be used in an `automation` trigger. 
--- a/source/_components/input_slider.markdown
+++ b/source/_components/input_slider.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: home-assistant.png
 ha_category: Automation
 ha_release: 0.16
 ---
 The `input_slider` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the slider generate state events. These state events can be utilized as `automation` triggers as well. 
--- a/source/_components/keyboard.markdown
+++ b/source/_components/keyboard.markdown
@ -28,7 +28,7 @@ keyboard:
 ## {% linkable_title Dependencies %}
-You may need to install platform-specific [dependencies for PyUserInput](https://github.com/SavinaRoja/PyUserInput#dependencies) in order to use the keyboard component. In most cases this can be done by running:
+You may need to install platform-specific [dependencies for PyUserInput](https://github.com/PyUserInput/PyUserInput#dependencies) in order to use the keyboard component. In most cases this can be done by running:
 ```bash
 $ pip3 install [package name]
--- a/source/_components/light.blinksticklight.markdown
+++ b/source/_components/light.blinksticklight.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: blinkstick.png
 ha_category: Light
 ha_release: 0.7.5
 ---
--- a/source/_components/light.hyperion.markdown
+++ b/source/_components/light.hyperion.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Light
 ha_release: 0.7.6
 ---
 This platform allows you to integrate your [Hyperion](https://github.com/tvdzwan/hyperion/wiki) into Home Assistant.
--- a/source/_components/light.lifx.markdown
+++ b/source/_components/light.lifx.markdown
@ -10,6 +10,7 @@ footer: true
 logo: lifx.png
 ha_category: Light
 ha_iot_class: "Local Push"
 ha_release: 0.12
 ---
 The `lifx` platform allows you to integrate your [LIFX](http://www.lifx.com) into Home Assistant.
--- a/source/_components/light.mysensors.markdown
+++ b/source/_components/light.mysensors.markdown
@ -10,6 +10,7 @@ footer: true
 logo: mysensors.png
 ha_category: Light
 featured: false
 ha_release: 0.13
 ---
 Integrates MySensors lights into Home Assistant. See the [main component] for configuration instructions.
--- a/source/_components/light.rfxtrx.markdown
+++ b/source/_components/light.rfxtrx.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Light
 ha_release: 0.7.5
 ---
 The `rfxtrx` platform support lights that communicate in the frequency range of 433.92 MHz.
--- a/source/_components/light.scsgate.markdown
+++ b/source/_components/light.scsgate.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: bus_scs.png
 ha_category: Light
 ha_release: 0.13
 ---
 The SCSGate device can control lights of the BTicino MyHome system.
--- a/source/_components/light.wemo.markdown
+++ b/source/_components/light.wemo.markdown
@ -10,6 +10,7 @@ footer: true
 logo: belkin_wemo.png
 ha_category: Light
 ha_iot_class: "Local Polling"
 ha_release: 0.14
 ---
--- a/source/_components/lock.mqtt.markdown
+++ b/source/_components/lock.mqtt.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: mqtt.png
 ha_category: Lock
 ha_release: 0.15
 ---
 The `mqtt` lock platform let you control your MQTT enabled locks.
--- a/source/_components/lock.verisure.markdown
+++ b/source/_components/lock.verisure.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: verisure.png
 ha_category: Lock
 ha_release: 0.13
 ---
--- a/source/_components/lock.wink.markdown
+++ b/source/_components/lock.wink.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: wink.png
 ha_category: Lock
 ha_release: 0.9
 ---
--- a/source/_components/media_player.firetv.markdown
+++ b/source/_components/media_player.firetv.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: firetv.png
 ha_category: Media Player
 ha_release: 0.7.6
 ---
--- a/source/_components/media_player.onkyo.markdown
+++ b/source/_components/media_player.onkyo.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: onkyo.png
 ha_category: Media Player
 ha_release: 0.17
 ---
--- a/source/_components/media_player.panasonic_viera.markdown
+++ b/source/_components/media_player.panasonic_viera.markdown
@ -10,6 +10,7 @@ footer: true
 logo: panasonic.png
 ha_category: Media Player
 featured: false
 ha_release: 0.17
 ---
 The `panasonic_viera` platform allows you to control a Panasonic Viera TV.
--- a/source/_components/media_player.samsungtv.markdown
+++ b/source/_components/media_player.samsungtv.markdown
@ -10,6 +10,7 @@ footer: true
 logo: samsung.png
 ha_category: Media Player
 featured: false
 ha_release: 0.13
 ---
 The `samsungtv` platform allows you to control a [Samsung Smart TV](http://www.samsung.com/uk/consumer/tv-audio-video/televisions/).
@ -35,6 +36,7 @@ Configuration variables:
 Currently known supported models:
 - C7700
 - D7000
 - D8000
 - ES5500
 - ES6800
--- a/source/_components/media_player.snapcast.markdown
+++ b/source/_components/media_player.snapcast.markdown
@ -10,6 +10,7 @@ footer: true
 logo:
 ha_category: Media Player
 featured: false
 ha_release: 0.13
 ---
 The `snapcast` platform allows you to control [SnapCast](https://github.com/badaix/snapcast) from Home Assistant.
--- a/source/_components/media_player.webostv.markdown
+++ b/source/_components/media_player.webostv.markdown
@ -10,6 +10,7 @@ footer: true
 logo: webos.png
 ha_category: Media Player
 ha_iot_class: "Local Poll"
 ha_release: 0.18
 ---
 The `webostv` platform allows you to control a LG WebOS Smart TV.
--- a/source/_components/media_player.yamaha.markdown
+++ b/source/_components/media_player.yamaha.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: yamaha.png
 ha_category: Media Player
 ha_release: 0.16
 ---
 The `yamaha` platform allows you to control [Yamaha Network Receivers](http://usa.yamaha.com/products/audio-visual/av-receivers-amps/rx) from Home Assistant.
--- a/source/_components/mqtt_eventstream.markdown
+++ b/source/_components/mqtt_eventstream.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: mqtt.png
 ha_category: Other
 ha_release: 0.11
 ---
 The `mqtt_eventstream` components connects two Home Assistant instances via MQTT.
--- a/source/_components/notify.command_line.markdown
+++ b/source/_components/notify.command_line.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: command_line.png
 ha_category: Notifications
 ha_release: 0.14
 ---
 The `command_line` platform allows you to use external tools for notifications from Home Assistant. The message will be passed in as STDIN.
--- a/source/_components/notify.free_mobile.markdown
+++ b/source/_components/notify.free_mobile.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: free_mobile.png
 ha_category: Notifications
 ha_release: 0.11
 ---
 The `free_mobile` platform is using the French mobile operator [Free Mobile](http://mobile.free.fr/) to send SMS to your own cell phone. 
--- a/source/_components/notify.gntp.markdown
+++ b/source/_components/notify.gntp.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: gntp.png
 ha_category: Notifications
 ha_release: 0.16
 ---
--- a/source/_components/notify.message_bird.markdown
+++ b/source/_components/notify.message_bird.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: message_bird.png
 ha_category: Notifications
 ha_release: 0.16
 ---
 The `MessageBird` notification platform sends notifications as SMS messages using [MessageBird](https://www.messagebird.com/) to your mobile phone.
--- a/source/_components/notify.rest.markdown
+++ b/source/_components/notify.rest.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Notifications
 ha_release: 0.13
 ---
--- a/source/_components/notify.telegram.markdown
+++ b/source/_components/notify.telegram.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: telegram.png
 ha_category: Notifications
 ha_release: 0.7.5
 ---
--- a/source/_components/notify.twitter.markdown
+++ b/source/_components/notify.twitter.markdown
@ -9,12 +9,13 @@ sharing: true
 footer: true
 logo: twitter.png
 ha_category: Notifications
 ha_release: 0.12
 ---
 The `twitter` platform uses [Twitter](https://twitter.com) to delivery notifications from Home Assistant.
-Go to [Twitter Apps](https://apps.twitter.com/app/new) and create an application. Visit "Keys and Access Tokens" of the application to get the details ("Consumer Key", "Consumer Secret", and "Access Token Secret" which needs to be generated).
+Go to [Twitter Apps](https://apps.twitter.com/app/new) and create an application. Visit "Keys and Access Tokens" of the application to get the details ("Consumer Key", "Consumer Secret", "Access Token" and "Access Token Secret" which needs to be generated).
 To add Twitter to your installation, add the following to your `configuration.yaml` file:
@ -25,6 +26,7 @@ notify:
  platform: twitter
  consumer_key: ABCDEFGHJKLMNOPQRSTUVXYZ
  consumer_secret: ABCDEFGHJKLMNOPQRSTUVXYZ
  access_token: ABCDEFGHJKLMNOPQRSTUVXYZ
  access_token_secret: ABCDEFGHJKLMNOPQRSTUVXYZ
 ```
@ -33,6 +35,7 @@ Configuration variables:
 - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
 - **consumer_key** (*Required*): Your "Consumer Key" (API Key) for the application.
 - **consumer_secret** (*Required*): Your "Consumer Secret" (API Secret) for the application.
 - **access_token** (*Required*): Your "Access Token" for the application.
 - **access_token_secret** (*Required*): Your "Access Token Secret" for the application.
 To use notifications, please see the [getting started with automation page](/getting-started/automation/).
--- a/source/_components/notify.webostv.markdown
+++ b/source/_components/notify.webostv.markdown
@ -10,6 +10,7 @@ footer: true
 logo: webos.png
 ha_category: Notifications
 ha_iot_class: "Local Poll"
 ha_release: 0.18
 ---
 The `webostv` platform allows you to send notifications to a LG WebOS Smart TV.
--- a/source/_components/proximity.markdown
+++ b/source/_components/proximity.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: home-assistant.png
 ha_category: Organization
 ha_release: 0.13
 ---
 The `proximity` component allows you to monitor the proximity of devices to a particular [zone](/components/zone/) and the direction of travel. The result is an entity created in Home Assistant which maintains the proximity data.
--- a/source/_components/rollershutter.command_line.markdown
+++ b/source/_components/rollershutter.command_line.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: command_line.png
 ha_category: Rollershutter
 ha_release: 0.14
 ---
 A rollershutter platform that issues specific commands when it is moved up, down and stopped. This might very well become our most powerful platform as it allows anyone to integrate any type of rollershutter into Home Assistant that can be controlled from the command line, including calling other scripts!
--- a/source/_components/rollershutter.mqtt.markdown
+++ b/source/_components/rollershutter.mqtt.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: mqtt.png
 ha_category: Rollershutter
 ha_release: 0.9
 ---
--- a/source/_components/scene.hunterdouglas_powerview.markdown
+++ b/source/_components/scene.hunterdouglas_powerview.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: hunter-douglas-powerview.png
 ha_category: Rollershutter
 ha_release: 0.15
 ---
 Implements the [Hunter Douglas PowerView](http://www.hunterdouglas.com/operating-systems/powerview-motorization/support) platform scene control. It queries the PowerView Hub and Home Assistant displays them as scenes.
--- a/source/_components/scsgate.markdown
+++ b/source/_components/scsgate.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: bus_scs.png
 ha_category: Hub
 ha_release: 0.13
 ---
 The SCSGate component support the [SCSGate](https://translate.google.com/translate?hl=en&sl=it&tl=en&u=http%3A%2F%2Fguidopic.altervista.org%2Feibscsgt%2Finterface.html) device. This a homebrew device allows to interact with the MyHome system from BTicino/Legrande.
--- a/source/_components/sensor.dht.markdown
+++ b/source/_components/sensor.dht.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: DIY
 ha_release: 0.7
 ---
--- a/source/_components/sensor.dweet.markdown
+++ b/source/_components/sensor.dweet.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: dweet.png
 ha_category: Sensor
 ha_release: 0.10
 ---
 The `dweet` sensor platform allows you to get details from your devices which are publishing their values to [Dweet.io](https://dweet.io/).
--- a/source/_components/sensor.eliqonline.markdown
+++ b/source/_components/sensor.eliqonline.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: eliq.png
 ha_category: Sensor
 ha_release: 0.10
 ---
--- a/source/_components/sensor.gtfs.markdown
+++ b/source/_components/sensor.gtfs.markdown
@ -10,6 +10,7 @@ footer: true
 logo: 'gtfs.png'
 ha_category: Sensor
 ha_iot_class: "Local Polling"
 ha_release: 0.17
 ---
--- a/source/_components/sensor.loop_energy.markdown
+++ b/source/_components/sensor.loop_energy.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: loop.png
 ha_category: Sensor
 ha_release: 0.17
 ---
--- a/source/_components/sensor.mqtt.markdown
+++ b/source/_components/sensor.mqtt.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: mqtt.png
 ha_category: Sensor
 ha_release: 0.7
 ---
--- a/source/_components/sensor.neurio_energy.markdown
+++ b/source/_components/sensor.neurio_energy.markdown
@ -10,6 +10,7 @@ footer: true
 logo: neurio.png
 ha_category: Sensor
 ha_iot_class: "Cloud Polling"
 ha_release: 0.14
 ---
--- a/source/_components/sensor.nzbget.markdown
+++ b/source/_components/sensor.nzbget.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 ha_category: Sensor
 ha_iot_class: "Local Polling"
 ha_release: 0.17
 ---
 The `NZBGet` platform will allow you to monitor your downloads with [NZBGet](http://NZBGet.net) from within Home Assistant and setup automation based on the information.
--- a/source/_components/sensor.onewire.markdown
+++ b/source/_components/sensor.onewire.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Sensor
 ha_release: 0.12
 ---
 The `onewire` platform supports sensors which are using the One wire (1-wire) bus for communication.
--- a/source/_components/sensor.speedtest.markdown
+++ b/source/_components/sensor.speedtest.markdown
@ -10,6 +10,7 @@ footer: true
 logo: speedtest.png
 ha_category: Sensor
 featured: false
 ha_release: 0.13
 ---
 The `speedtest` sensor component uses the [Speedtest.net](https://speedtest.net/) web service to measure network bandwidth performance.
--- a/source/_components/sensor.steam_online.markdown
+++ b/source/_components/sensor.steam_online.markdown
@ -2,13 +2,15 @@
 layout: page
 title: "Steam"
 description: "Instructions on how to set up Steam sensors in Home Assistant."
-date: 2015-12-19 09:00
+date: 2016-04-30 09:00
 sidebar: true
 comments: false
 sharing: true
 footer: true
 logo: steam.png
 ha_category: Sensor
 ha_iot_class: "Cloud Polling"
 ha_release: 0.14
 ---
--- a/source/_components/sensor.tcp.markdown
+++ b/source/_components/sensor.tcp.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Sensor
 ha_release: 0.14
 ---
 The TCP component allows the integration of some services for which a specific Home Assistant component does not exist. If the service communicates over a TCP socket with a simple request/reply mechanism then the chances are that this component will allow integration with it.
--- a/source/_components/sensor.template.markdown
+++ b/source/_components/sensor.template.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Sensor
 ha_release: 0.12
 ---
 The `template` platform supports sensors which breaks out `state_attributes` from other entities.
--- a/source/_components/sensor.thinkingcleaner.markdown
+++ b/source/_components/sensor.thinkingcleaner.markdown
@ -10,6 +10,7 @@ footer: true
 logo: thinkingcleaner.png
 ha_category: Sensor
 ha_iot_class: "Local Poll"
 ha_release: 0.18
 ---
 The `ThinkingCleaner` sensor platform simple displays information about your [ThinkingCleaner](http://www.thinkingcleaner.com) addon.
--- a/source/_components/sensor.torque.markdown
+++ b/source/_components/sensor.torque.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: torque.png
 ha_category: Sensor
 ha_release: 0.10
 ---
 The `torque` platform will allow you to monitor [Torque](http://torque-bhp.com/) data relayed from a bluetooth OBD2 stick via the Torque mobile application.
--- a/source/_components/sensor.twitch.markdown
+++ b/source/_components/sensor.twitch.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: twitch.png
 ha_category: Sensor
 ha_release: 0.10
 ---
--- a/source/_components/sensor.uber.markdown
+++ b/source/_components/sensor.uber.markdown
@ -10,6 +10,7 @@ footer: true
 logo: uber.png
 ha_category: Sensor
 ha_iot_class: "Cloud Polling"
 ha_release: 0.16
 ---
--- a/source/_components/sensor.yr.markdown
+++ b/source/_components/sensor.yr.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: yr.png
 ha_category: Weather
 ha_release: 0.11
 ---
--- a/source/_components/splunk.markdown
+++ b/source/_components/splunk.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: splunk.png
 ha_category: "History"
 ha_release: 0.13
 ---
 The `splunk` component makes it possible to log all state changes to an external [Splunk](http://splunk.com/) database using Splunk's HTTP Event Collector feature. You can either use this alone, or with the HomeAssistant for Splunk [app](https://github.com/miniconfig/splunk-homeassistant). Since the HEC feature is new to Splunk, you will need to use at least version 6.3.
--- a/source/_components/statsd.markdown
+++ b/source/_components/statsd.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: "History"
 ha_release: 0.12
 ---
 The `statsd` component makes it possible to transfer all state changes to an external [StatsD](https://github.com/etsy/statsd) instance.
--- a/source/_components/switch.arest.markdown
+++ b/source/_components/switch.arest.markdown
@ -10,6 +10,7 @@ footer: true
 logo: arest.png
 ha_category: Switch
 ha_iot_class: "Local Polling"
 ha_release: 0.16
 ---
 The `arest` switch platform allows you to toggle pins of your devices (like Arduino boards with a ethernet/wifi connection, ESP8266 based devices, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework.
--- a/source/_components/switch.dlink.markdown
+++ b/source/_components/switch.dlink.markdown
@ -10,6 +10,7 @@ footer: true
 logo: dlink.png
 ha_category: Switch
 ha_iot_class: "Local Polling"
 ha_release: 0.14
 ---
--- a/source/_components/switch.mqtt.markdown
+++ b/source/_components/switch.mqtt.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: mqtt.png
 ha_category: Switch
 ha_release: 0.7
 ---
 The `mqtt` switch platform let you control your MQTT enabled light.
--- a/source/_components/switch.pulseaudio_loopback.markdown
+++ b/source/_components/switch.pulseaudio_loopback.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: pulseaudio.png
 ha_category: Switch
 ha_release: 0.16
 ---
--- a/source/_components/switch.rest.markdown
+++ b/source/_components/switch.rest.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Switch
 ha_release: 0.7.6
 ---
--- a/source/_components/switch.rfxtrx.markdown
+++ b/source/_components/switch.rfxtrx.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Switch
 ha_release: 0.7.5
 ---
 The `rfxtrx` platform support switches that communicate in the frequency range of 433.92 MHz.
--- a/source/_components/switch.scsgate.markdown
+++ b/source/_components/switch.scsgate.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: bus_scs.png
 ha_category: Switch
 ha_release: 0.13
 ---
 The SCSGate device can control switches of the BTicino MyHome system.
--- a/source/_components/switch.template.markdown
+++ b/source/_components/switch.template.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Switch
 ha_release: 0.13
 ---
 The `template` platform creates switches that combine components.
--- a/source/_components/switch.thinkingcleaner.markdown
+++ b/source/_components/switch.thinkingcleaner.markdown
@ -10,6 +10,7 @@ footer: true
 logo: thinkingcleaner.png
 ha_category: Switch
 ha_iot_class: "Local Poll"
 ha_release: 0.18
 ---
 The `ThinkingCleaner` switch platform allows you to control your [ThinkingCleaner](http://www.thinkingcleaner.com) addon.
--- a/source/_components/switch.wake_on_lan.markdown
+++ b/source/_components/switch.wake_on_lan.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: ethernet.png
 ha_category: Switch
 ha_release: 0.16
 ---
 The `wake_on_lan` (WOL) switch platform allows you to turn on a [WOL](https://en.wikipedia.org/wiki/Wake-on-LAN) enabled computer.
--- a/source/_components/tellduslive.markdown
+++ b/source/_components/tellduslive.markdown
@ -10,6 +10,7 @@ footer: true
 logo: telldus.png
 ha_category: Hub
 featured: false
 ha_release: 0.11
 ---
 The `tellduslive` component let you connect to [Telldus Live](https://live.telldus.com). It's cloud platform that connects to your Tellstick connected gear at home.
--- a/source/_components/thermostat.ecobee.markdown
+++ b/source/_components/thermostat.ecobee.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: ecobee.png
 ha_category: Thermostat
 ha_release: 0.9
 ---
 To get your Ecobee thermostats working with Home Assistant, follow the instructions for the general [Ecobee component](/components/ecobee/).
--- a/source/_components/thermostat.heatmiser.markdown
+++ b/source/_components/thermostat.heatmiser.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: heatmiser.png
 ha_category: Thermostat
 ha_release: 0.10
 ---
--- a/source/_components/thermostat.homematic.markdown
+++ b/source/_components/thermostat.homematic.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: homematic.png
 ha_category: Thermostat
 ha_release: 0.9
 ---
--- a/source/_components/thermostat.proliphix.markdown
+++ b/source/_components/thermostat.proliphix.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: proliphix.png
 ha_category: Thermostat
 ha_release: 0.11
 ---
--- a/source/_components/thermostat.zwave.markdown
+++ b/source/_components/thermostat.zwave.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: z-wave.png
 ha_category: Thermostat
 ha_release: 0.17
 ---
 To get your Z-Wave thermostat working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
--- a/Show More
+++ b/Show More