diff --git a/source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown b/source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown
new file mode 100644
index 00000000000..6ebdb75ffd0
--- /dev/null
+++ b/source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown
@@ -0,0 +1,129 @@
+---
+layout: post
+title: "IP Cameras, Arduinos, Kodi and Efergy Energy Monitors now supported"
+description: "New support for IP Cameras, Arduinos, Kodi and Efergy monitors"
+date: 2015-07-11 01:37 -0700
+date_formatted: "July 11, 2015"
+comments: true
+categories: release-notes
+---
+
+Another month has passed and some great new features have landed in Home Assistant. This month release has been made possible by [balloob](https://github.com/balloob), [ettisan](https://github.com/ettisan), [fabaff](https://github.com/fabaff), [gyran](https://github.com/gyran), [jamespcole](https://github.com/jamespcole), [michaelarnauts](https://github.com/michaelarnauts), [miniconfig](https://github.com/miniconfig) and [rmkraus](https://github.com/rmkraus).
+
+This release includes some architectural changes by me. The first is that the frontend is now based on a [NuclearJS](http://optimizely.github.io/nuclear-js/) JavaScript backend. This has greatly helped to organize and optimize the frontend code. Another change is that Home Assistant will now install dependencies on-demand instead of installing dependencies for all supported devices.
+
+__IP Camera Support__
+James has worked very hard to add support for IP cameras to Home Assistant which is included in this release. The initial release focusses on providing generic IP camera support. This means that any webcam that can exposes a JPEG image via a url can be integrated.
+
+Home Assistant will route the requests to your camera via the server allowing you to expose IP camera's inside your network via the Home Assistant app.
+
+```yaml
+# Example configuration.yaml entry
+camera:
+ platform: generic
+ name: my sample camera
+ username: MY_USERNAME
+ password: MY_PASSWORD
+ still_image_url: http://194.218.96.92/jpg/image.jpg
+```
+
+
+To update to the latest version, run scripts/update. Please report any issues on GitHub.
+
+
+
+
+__Arduino__
+
+Fabian has contributed support for interfacing with Arduinos. This makes it possible to connect your Arduino via USB and expose pins as sensor data and write to pins via switches. Have a look at [the docs](/components/arduino.html) for an extensive guide to get started.
+
+```yaml
+# Example configuration.yaml entry
+switch:
+ platform: arduino
+ pins:
+ 11:
+ name: Fan Office
+ type: digital
+ 12:
+ name: Light Desk
+ type: digital
+
+sensor:
+ platform: arduino
+ pins:
+ 1:
+ name: Door switch
+ type: analog
+ 0:
+ name: Brightness
+ type: analog
+```
+
+__Kodi (XBMC)__
+
+Ettisan has contributed a Kodi (XBMC) platform for the media player component. This allows you to track all the media that you are playing and allow you to control it.
+
+```
+# Example configuration.yaml entry
+media_player:
+ platform: kodi
+ name: Kodi
+ url: http://192.168.0.123/jsonrpc
+ user: kodi
+ password: my_secure_password
+```
+
+__TP-Link__
+
+Michael has added TP-Link support to the device tracker. This allows you to now detect presence if you have a TP-Link router.
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+ platform: tplink
+ host: YOUR_ROUTER_IP
+ username: YOUR_ADMIN_USERNAME
+ password: YOUR_ADMIN_PASSWORD
+```
+
+__Efergy energy monitor__
+
+Miniconfig has contributed support for the [Efergy energy meters](https://efergy.com). To get an app token, log in to your efergy account, go to the Settings page, click on App tokens, and click "Add token".
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+ platform: efergy
+ app_token: APP_TOKEN
+ utc_offset: UTC_OFFSET
+ monitored_variables:
+ - type: instant_readings
+ - type: budget
+ - type: cost
+ period: day
+ currency: $
+```
+
+__Forecast.io__
+Fabian has added support for [Forecast.io](https://forecast.io/) to get weather forecasts for Home Assistant. You need an API key which is free but requires a [registration](https://developer.forecast.io/register). To add Forecast.io to your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+ platform: forecast
+ api_key: YOUR_APP_KEY
+ monitored_conditions:
+ - summary
+ - precip_type
+ - precip_intensity
+ - temperature
+ - dew_point
+ - wind_speed
+ - wind_bearing
+ - cloud_cover
+ - humidity
+ - pressure
+ - visibility
+ - ozone
+```
diff --git a/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown b/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown
new file mode 100644
index 00000000000..8845471af0f
--- /dev/null
+++ b/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown
@@ -0,0 +1,120 @@
+---
+layout: post
+title: "MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported"
+description: "New support for MQTT, Rasperry PI GPIO, Logitech Squeezebox and ASUSWRT routers"
+date: 2015-08-09 18:01 -0700
+date_formatted: "August 9, 2015"
+comments: true
+categories: release-notes
+---
+
+It's time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to [@balloob](https://github.com/balloob). If you're a developer, make sure you read up on [the deprecation notices](https://github.com/balloob/home-assistant/pull/251). [@fabaff](https://github.com/fabaff) did another great round of documentating all the various components.
+
+__MQTT Support__
+
+The big new addition in this release is the support for the MQTT protocol by [@fabaff](https://github.com/fabaff) with some help from [@balloob](https://github.com/balloob). It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics ([see the example][mqtt-example]) and also support for the automation component [has been added][mqtt-automation]. For more information, see [the MQTT component page][mqtt-component].
+
+[mqtt-example]: https://github.com/balloob/home-assistant/blob/dev/config/custom_components/mqtt_example.py
+[mqtt-automation]: /components/automation.html#mqtt-based-automation
+[mqtt-component]: /components/mqtt.html
+
+```yaml
+# Example configuration.yaml entry
+mqtt:
+ broker: IP_ADDRESS_BROKER
+ # All the other options are optional:
+ port: 1883
+ keepalive: 60
+ qos: 0
+ username: your_username
+ password: your_secret_password
+```
+
+
+
+__Raspberry PI GPIO Support__
+
+[@gbarba](https://github.com/gbarba) has contributed support to use the general purpose input and output pins on a Raspberry PI as switches inside Home Assistant.
+
+```
+# Example configuration.yaml entry
+switch:
+ platform: rpi_gpio
+ ports:
+ 11: Fan Office
+ 12: Light Desk
+```
+
+__ASUSWRT based routers__
+
+[@persandstrom](https://github.com/persandstrom) has contributed support to do prescence detection using ASUSWRT based routers.
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+ platform: asuswrt
+ host: YOUR_ROUTER_IP
+ username: YOUR_ADMIN_USERNAME
+ password: YOUR_ADMIN_PASSWORD
+```
+
+__Logitech Squeezebox media player support__
+
+[@persandstrom](https://github.com/persandstrom) also contributed support for the Logitech Squeezebox media player. This allows you to control your Logitech Squeezebox from Home Assistant.
+
+```
+# Example configuration.yaml entry
+media_player:
+ platform: squeezebox
+ host: 192.168.1.21
+ port: 9090
+ username: user
+ password: password
+```
+
+__Slack notification support__
+
+[@jamespcole](https://github.com/jamespcole) has contributed a Slack platform for the notification platform. This allows you to deliver messages to any channel.
+
+```yaml
+# Example configuration.yaml entry
+notify:
+ platform: slack
+ api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
+ default_channel: '#general'
+```
+
+__Edimax Smart Switches support__
+
+[@rkabadi](https://github.com/rkabadi) has contributed support for integrating Edimax Smart Switches into Home Assistant.
+
+```
+# Example configuration.yaml entry
+switch:
+ platform: edimax
+ host: 192.168.1.32
+ username: YOUR_USERNAME
+ password: YOUR_PASSWORD
+ name: Edimax Smart Plug
+```
+
+__RFXtrx sensor support__
+[@danielhiversen](https://github.com/danielhiversen) has contributed support for RFXtrx sensors. It supports sensors that communicate in the frequency range of 433.92 MHz.
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+ - platform: rfxtrx
+ device: PATH_TO_DEVICE
+```
+
+The path to your device, e.g. `/dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0`
+
+__TEMPer temperature sensor support__
+Support for Temper temperature sensors has been contributed by [@rkabadi](https://github.com/rkabadi).
+
+```
+# Example configuration.yaml entry
+sensor:
+ platform: temper
+```
diff --git a/source/_posts/2015-08-17-verisure-and-modern-tp-link-router-support.markdown b/source/_posts/2015-08-17-verisure-and-modern-tp-link-router-support.markdown
new file mode 100644
index 00000000000..983d48d3370
--- /dev/null
+++ b/source/_posts/2015-08-17-verisure-and-modern-tp-link-router-support.markdown
@@ -0,0 +1,33 @@
+---
+layout: post
+title: "Verisure devices and modern TP-Link routers now supported"
+description: "New support for Verisure switches, sensors and hygrometers and modern TP-Link routers"
+date: 2015-08-17 20:00 -0700
+date_formatted: "August 17, 2015"
+comments: true
+categories: release-notes
+---
+
+A minor bug fix release to fix some issues that have come up since the last release. Please upgrade as soon as possible by running `git pull` from the Home Assistant directory.
+
+This release is a major milestone in our test coverage as we've crossed into the 80s! It has to be noted that this covers mainly the core and automation components. Platforms that communicate with IoT devices have been excluded.
+
+As we didn't want to just push out bug fixes, this release includes a few additions:
+
+ - Support for modern TP-Link routers like the ArcherC9 line has been contributed by [@chrisvis](https://github.com/chrisvis).
+ - Improved support for MQTT topic subscriptions has been contributed by [@qrtn](https://github.com/qrtn)
+
+__Verisure Support__
+
+Home Assistant support to integrate your [Verisure](https://www.verisure.com/) alarms, hygrometers, sensors and thermometers has been contributed by [@persandstrom](https://github.com/persandstrom).
+
+```yaml
+# Example configuration.yaml entry
+verisure:
+ username: user@example.com
+ password: password
+ alarm: 1
+ hygrometers: 0
+ smartplugs: 1
+ thermometers: 0
+```
diff --git a/source/components/automation.markdown b/source/components/automation.markdown
index 74ac93b01bb..306d9fa57a6 100644
--- a/source/components/automation.markdown
+++ b/source/components/automation.markdown
@@ -29,10 +29,10 @@ automation:
service_data: {"message":"The sun has set"}
```
-## Setting up triggers
+## {% linkable_title Setting up triggers %}
-#### Time-based automation
-This allows you to trigger actions whenever the time matches your filter. You can setup filters to match on hours, minutes and seconds. Any filter that you omit will match all values.
+#### {% linkable_title Time-based automation %}
+This allows you to trigger actions whenever the time matches your filter. You can setup filters to match on hours, minutes and seconds. Any filter that you omit will match all values.
Here are some example values:
@@ -49,7 +49,7 @@ Here are some example values:
time_seconds: 0
```
-#### State-based automation
+#### {% linkable_title State-based automation %}
This allows you to trigger actions based on state changes of any entity within Home Assistant. You can omit the `state_from` and `state_to` to match all.
```
@@ -76,7 +76,21 @@ This allows you to trigger actions based on state changes of any entity within H
Use quotes around your values for state_from and state_to to avoid the YAML parser interpreting some values as booleans.
-## Setting up the action
+#### {% linkable_title MQTT-based automation %}
+This allows you to trigger actions based on messages on an MQTT topic. You can specify an optional payload to match as well.
+
+```
+ # Match any changes to bathroom light
+ platform: mqtt
+ mqtt_topic: home/bathroom/light
+
+ # Match only if bathroom light is turned on
+ platform: mqtt
+ mqtt_topic: home/bathroom/light
+ mqtt_payload: 'on'
+```
+
+## {% linkable_title Setting up the action %}
Currently the only supported action is calling a service. Services are what devices expose to be controlled, so this will allow us to control anything that Home Assistant can control.
@@ -95,7 +109,7 @@ Currently the only supported action is calling a service. Services are what devi
service_data: {"message":"YAY"}
```
-## Putting it all together
+## {% linkable_title Putting it all together %}
For every combination of a trigger and an action we will have to combine the configuration lines and add it to an `automation` component entry in `configuration.yaml`. You can add an optional `alias` key to the configuration to make the logs more understandable. To setup multiple entries, append 2, 3 etc to the section name. An example of a `configuration.yaml` file:
```
diff --git a/source/components/camera.generic.markdown b/source/components/camera.generic.markdown
new file mode 100644
index 00000000000..b0d54041383
--- /dev/null
+++ b/source/components/camera.generic.markdown
@@ -0,0 +1,25 @@
+---
+layout: page
+title: "Generic IP Camera"
+description: "Instructions how to integrate IP cameras within Home Assistant."
+date: 2015-07-11 0:36
+sidebar: false
+comments: false
+sharing: true
+footer: true
+---
+
+
+This component allows you to integrate any IP camera into Home Assistant. It supports fetching images from a url with optional HTTP authentication.
+
+Home Assistant will serve the images via its server, making it possible to view your IP camera's while outside of your network.
+
+```yaml
+# Example configuration.yaml entry
+camera:
+ platform: generic
+ name: my sample camera
+ username: MY_USERNAME
+ password: MY_PASSWORD
+ still_image_url: http://194.218.96.92/jpg/image.jpg
+```
diff --git a/source/components/device_tracker.asuswrt.markdown b/source/components/device_tracker.asuswrt.markdown
new file mode 100644
index 00000000000..362a30a3a3e
--- /dev/null
+++ b/source/components/device_tracker.asuswrt.markdown
@@ -0,0 +1,28 @@
+---
+layout: page
+title: "ASUSWRT support"
+description: "Instructions how to integrate ASUSWRT based routers into Home Assistant."
+date: 2015-08-06 19:00
+sidebar: false
+comments: false
+sharing: true
+footer: true
+---
+
+
+This platform offers presence detection by looking at connected devices to a [ASUSWRT](http://event.asus.com/2013/nw/ASUSWRT/) based router.
+
+To use an ASUSWRT router in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+ platform: asuswrt
+ host: YOUR_ROUTER_IP
+ username: YOUR_ADMIN_USERNAME
+ password: YOUR_ADMIN_PASSWORD
+```
+
+This device tracker needs telnet to be enabled on the router.
+
+See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
diff --git a/source/components/device_tracker.ddwrt.markdown b/source/components/device_tracker.ddwrt.markdown
index c7b8b00a47e..4435eda1b27 100644
--- a/source/components/device_tracker.ddwrt.markdown
+++ b/source/components/device_tracker.ddwrt.markdown
@@ -12,6 +12,8 @@ footer: true
This platform offers presence detection by looking at connected devices to a [DD-WRT](http://www.dd-wrt.com/site/index) based router.
+To use a DD-WRRT router in your installation, add the following to your `configuration.yaml` file:
+
```yaml
# Example configuration.yaml entry
device_tracker:
diff --git a/source/components/device_tracker.tplink.markdown b/source/components/device_tracker.tplink.markdown
index 159e0fb9c95..d10750af4ba 100644
--- a/source/components/device_tracker.tplink.markdown
+++ b/source/components/device_tracker.tplink.markdown
@@ -10,7 +10,7 @@ footer: true
---
-This platform allows you to detect presence by looking at connected devices to a [TP-Link](https://www.tp-link.com) device.
+This platform allows you to detect presence by looking at connected devices to a [TP-Link](https://www.tp-link.com) device. This includes the ArcherC9 line.
```yaml
# Example configuration.yaml entry
diff --git a/source/components/index.markdown b/source/components/index.markdown
index 198109b3696..6ee4d4426eb 100644
--- a/source/components/index.markdown
+++ b/source/components/index.markdown
@@ -64,6 +64,18 @@ Entities are things that you want to observe within Home Assistant. Support for
Integrate any IP camera or image url into a camera feed.
+
+
@@ -180,13 +228,15 @@ the manufacturers of these devices.
Home Assistant integrates with a variety of third party Home Automation hubs and networks. It allows you to control the connected switches, lights and sensors via Home Assistant. Click on the following logos for setup instructions:
-[](/components/zwave.html)
-[](/components/tellstick.html)
-[](/components/vera.html)
-[](/components/wink.html)
-[](/components/isy994.html)
-[](/components/modbus.html)
-[](/components/arduino.html)
+[](/components/zwave.html)
+[](/components/tellstick.html)
+[](/components/vera.html)
+[](/components/wink.html)
+[](/components/isy994.html)
+
+[](/components/modbus.html)
+[](/components/arduino.html)
+[](/components/verisure.html)
Support for these devices is provided by the Home Assistant community and not
@@ -250,6 +300,12 @@ the manufacturers of these devices.
diff --git a/source/components/media_player.squeezebox.markdown b/source/components/media_player.squeezebox.markdown
new file mode 100644
index 00000000000..af69465f39e
--- /dev/null
+++ b/source/components/media_player.squeezebox.markdown
@@ -0,0 +1,26 @@
+---
+layout: page
+title: "Logitech Squeezebox support"
+description: "Instructions how to integrate a Logitech Squeezebox into Home Assistant."
+date: 2015-08-09 11:00
+sidebar: false
+comments: false
+sharing: true
+footer: true
+---
+
+
+The squeezebox platform allows you to control a [Logitech Squeezebox](https://en.wikipedia.org/wiki/Squeezebox_%28network_music_player%29) multimedia system from Home Assistant.
+
+To add your Squeezebox to your installation, add the following to your `configuration.yaml` file:
+
+```
+# Example configuration.yaml entry
+media_player:
+ platform: squeezebox
+ host: 192.168.1.21
+ port: 9090
+ username: user
+ password: password
+```
+
diff --git a/source/components/modbus.markdown b/source/components/modbus.markdown
index a0dcd86b762..73f3abf6313 100644
--- a/source/components/modbus.markdown
+++ b/source/components/modbus.markdown
@@ -38,6 +38,9 @@ sensor:
name: My boolean sensor
2:
name: My other boolean sensor
+ coils:
+ 0:
+ name: My coil switch
switch:
platform: modbus
diff --git a/source/components/mqtt.markdown b/source/components/mqtt.markdown
new file mode 100644
index 00000000000..97962444823
--- /dev/null
+++ b/source/components/mqtt.markdown
@@ -0,0 +1,65 @@
+---
+layout: page
+title: "MQTT"
+description: "Instructions how to setup MQTT within Home Assistant."
+date: 2015-08-07 18:00
+sidebar: false
+comments: false
+sharing: true
+footer: true
+---
+
+MQTT (aka MQ Telemetry Transport) is a machine-to-machine or "Internet of Things" connectivity protocol on top of TCP/IP. It allows extremely lightweight publish/subscribe messaging transport.
+
+The MQTT component needs an MQTT broker like [Mosquitto](http://mosquitto.org/) or [Mosca](http://www.mosca.io/). The Eclipse Foundation is running a public MQTT broker at [iot.eclipse.org](iot.eclipse.org) or the Mosquitto Project under [test.mosquitto.org](http://test.mosquitto.org). If you prefer to use a public, keep in mind to adjust the topic and that your messages may be publicly accessible.
+
+To integrate MQTT into Home Assistant, add the following section to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+mqtt:
+ broker: IP_ADDRESS_BROKER
+ # All the other options are optional:
+ port: 1883
+ keepalive: 60
+ qos: 0
+ username: your_username
+ password: your_secret_password
+```
+
+
+The MQTT component has no TLS support at the moment. This means that only plain-text communication is possible.
+
+
+## Building on top of MQTT
+
+There are two ways to integrate MQTT into your process. One is by using the [MQTT-automation rule](/components/automation.html#mqtt-based-automation). The other one is by integrating it into a component. See the [MQTT example component](https://github.com/balloob/home-assistant/blob/dev/config/custom_components/mqtt_example.py) how to do this.
+
+## Testing
+
+For debugging purposes `mosquitto` is shipping commandline tools to send and recieve MQTT messages. For sending test messages to a broker running on localhost:
+
+```bash
+mosquitto_pub -h 127.0.0.1 -t home-assistant/switch/1/on -m "Switch is ON"
+```
+
+Another way to send MQTT messages by hand is to use the "Developer Tools" in the Frontend. Choose "Call Service" and then `mqtt/mqtt_send` under "Available Services". Enter something similar to the example below into the "Service Data" field.
+
+```json
+{
+ "topic":"home-assistant/switch/1/on",
+ "payload":"Switch is ON"
+}
+```
+
+The message should appear on the bus:
+
+```bash
+... [homeassistant] Bus:Handling
+```
+
+For reading all messages sent on the topic `home-assistant` to a broker running on localhost:
+
+```bash
+mosquitto_sub -h 127.0.0.1 -v -t "home-assistant/#"
+```
diff --git a/source/components/notify.slack.markdown b/source/components/notify.slack.markdown
new file mode 100644
index 00000000000..27dac99a978
--- /dev/null
+++ b/source/components/notify.slack.markdown
@@ -0,0 +1,26 @@
+---
+layout: page
+title: "Slack notification support"
+description: "Instructions how to add Slack notifications to Home Assistant."
+date: 2015-08-06 18:00
+sidebar: false
+comments: false
+sharing: true
+footer: true
+---
+
+
+The slack platform allows you to deliver notifications from Home Assistant to [Slack](https://slack.com/).
+
+You need to obtain the [Slack API token](https://api.slack.com/web?sudo=1) to be able to send notifications.
+
+To enable the slack notification in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+notify:
+ platform: slack
+ api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
+ default_channel: '#general'
+```
+
diff --git a/source/components/sensor.efergy.markdown b/source/components/sensor.efergy.markdown
new file mode 100644
index 00000000000..7886ef0e459
--- /dev/null
+++ b/source/components/sensor.efergy.markdown
@@ -0,0 +1,27 @@
+---
+layout: page
+title: "Efergy support"
+description: "Instructions how to integrate Efergy devices within Home Assistant."
+date: 2015-07-11 0:15
+sidebar: false
+comments: false
+sharing: true
+footer: true
+---
+
+
+Integrate your [Efergy](https://efergy.com) meter information into Home Assistant. To get an app token, log in to your efergy account, go to the Settings page, click on App tokens, and click "Add token".
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+ platform: efergy
+ app_token: APP_TOKEN
+ utc_offset: UTC_OFFSET
+ monitored_variables:
+ - type: instant_readings
+ - type: budget
+ - type: cost
+ period: day
+ currency: $
+```
diff --git a/source/components/sensor.rfxtrx.markdown b/source/components/sensor.rfxtrx.markdown
new file mode 100644
index 00000000000..c1309abcded
--- /dev/null
+++ b/source/components/sensor.rfxtrx.markdown
@@ -0,0 +1,23 @@
+---
+layout: page
+title: "RFXtrx sensors support"
+description: "Instructions how to integrate RFXtrx sensors into Home Assistant."
+date: 2015-08-06 17:15
+sidebar: false
+comments: false
+sharing: true
+footer: true
+---
+The rfxtrx platform support sensors that communicate in the frequency range of 433.92 MHz.
+
+To enable the RFXtrx sensors in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+ - platform: rfxtrx
+ device: PATH_TO_DEVICE
+```
+
+The path to your device, e.g. `/dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0`
+
diff --git a/source/components/sensor.temper.markdown b/source/components/sensor.temper.markdown
new file mode 100644
index 00000000000..352584ca224
--- /dev/null
+++ b/source/components/sensor.temper.markdown
@@ -0,0 +1,20 @@
+---
+layout: page
+title: "TEMPer sensors support"
+description: "Instructions how to integrate TEMPer sensors into Home Assistant."
+date: 2015-08-06 19:00
+sidebar: false
+comments: false
+sharing: true
+footer: true
+---
+
+This temper sensor platform allows you to get the current temperature from a TEMPer device.
+
+To use your TEMPer sensor in your installation, add the following to your `configuration.yaml` file:
+
+```
+# Example configuration.yaml entry
+sensor:
+ platform: temper
+```
diff --git a/source/components/switch.command_switch.markdown b/source/components/switch.command_switch.markdown
index 39905e8a0ba..407fdee7372 100644
--- a/source/components/switch.command_switch.markdown
+++ b/source/components/switch.command_switch.markdown
@@ -19,7 +19,7 @@ To enable it, add the following lines to your `configuration.yaml`:
switch:
platform: command_switch
switches:
- - kitchen_light:
- oncmd: switch_command on kitchen
- offcmd: switch_command off kitchen
+ kitchen_light:
+ oncmd: switch_command on kitchen
+ offcmd: switch_command off kitchen
```
diff --git a/source/components/switch.edimax.markdown b/source/components/switch.edimax.markdown
new file mode 100644
index 00000000000..cbe99fafe09
--- /dev/null
+++ b/source/components/switch.edimax.markdown
@@ -0,0 +1,25 @@
+---
+layout: page
+title: "Edimax switches support"
+description: "Instructions how to integrate Edimax switches into Home Assistant."
+date: 2015-06-10 22:54
+sidebar: false
+comments: false
+sharing: true
+footer: true
+---
+
+
+This edimax switch platform allows you to control the state of your [Edimax](http://www.edimax.com/edimax/merchandise/merchandise_list/data/edimax/global/home_automation_smart_plug/) switches.
+
+To use your Edimax switch in your installation, add the following to your `configuration.yaml` file:
+
+```
+# Example configuration.yaml entry
+switch:
+ platform: edimax
+ host: 192.168.1.32
+ username: YOUR_USERNAME
+ password: YOUR_PASSWORD
+ name: Edimax Smart Plug
+```
diff --git a/source/components/switch.rpi_gpio.markdown b/source/components/switch.rpi_gpio.markdown
new file mode 100644
index 00000000000..76a5bbbde98
--- /dev/null
+++ b/source/components/switch.rpi_gpio.markdown
@@ -0,0 +1,26 @@
+---
+layout: page
+title: "Raspberry PI GPIO support"
+description: "Instructions how to integrate the GPIO of a Raspberry PI into Home Assistant."
+date: 2015-08-07 14:00
+sidebar: false
+comments: false
+sharing: true
+footer: true
+---
+
+
+The rpi_gpio switch platform allows you to control the GPIOs of your [Raspberry Pi](https://www.raspberrypi.org/).
+
+To use your Raspberry Pi's GPIO in your installation, add the following to your `configuration.yaml` file:
+
+```
+# Example configuration.yaml entry
+switch:
+ platform: rpi_gpio
+ ports:
+ 11: Fan Office
+ 12: Light Desk
+```
+
+For more details about the GPIO layout, visit the Wikipedia [article](https://en.wikipedia.org/wiki/Raspberry_Pi#GPIO_connector) about the Raspberry Pi.
diff --git a/source/components/switch.wemo.markdown b/source/components/switch.wemo.markdown
index 13e1c27b0de..1d680f2f54d 100644
--- a/source/components/switch.wemo.markdown
+++ b/source/components/switch.wemo.markdown
@@ -10,11 +10,12 @@ footer: true
---
-The wemo platform allows you to control your [Belkin WeMo](http://www.belkin.com/us/p/P-F7C027/) switches from within Home Assistant.
+The wemo platform allows you to control your [Belkin WeMo](http://www.belkin.com/us/p/P-F7C027/) switches from within Home Assistant.
To add Wemo switches to your installation, add the following to your `configuration.yaml` file:
```yaml
+# Example configuration.yaml entry
switch:
- platform: wemo
+ - platform: wemo
```
diff --git a/source/components/verisure.markdown b/source/components/verisure.markdown
new file mode 100644
index 00000000000..e8962b91040
--- /dev/null
+++ b/source/components/verisure.markdown
@@ -0,0 +1,33 @@
+---
+layout: page
+title: "Verisure"
+description: "Instructions how to setup Verisure devices within Home Assistant."
+date: 2015-08-17 20:28
+sidebar: false
+comments: false
+sharing: true
+footer: true
+---
+
+
+
+Home Assistant has support to integrate your [Verisure](https://www.verisure.com/) devices.
+
+We support:
+
+ * Smartplugs
+ * Reading from thermometers and hygrometers integrated in various devices
+ * Reading alarm status
+
+Username and password are required. Other variables are optional and allow you to disable certain devices.
+
+```yaml
+# Example configuration.yaml entry
+verisure:
+ username: user@example.com
+ password: password
+ alarm: 1
+ hygrometers: 0
+ smartplugs: 1
+ thermometers: 0
+```
diff --git a/source/demo/frontend.html b/source/demo/frontend.html
index b1c6d302076..ae077e87c5f 100644
--- a/source/demo/frontend.html
+++ b/source/demo/frontend.html
@@ -1,5811 +1,6 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+ @-webkit-keyframes ha-spin {
+ 0% {
+ -webkit-transform: rotate(0deg);
+ transform: rotate(0deg);
+ }
+ 100% {
+ -webkit-transform: rotate(359deg);
+ transform: rotate(359deg);
+ }
+ }
+ @keyframes ha-spin {
+ 0% {
+ -webkit-transform: rotate(0deg);
+ transform: rotate(0deg);
+ }
+ 100% {
+ -webkit-transform: rotate(359deg);
+ transform: rotate(359deg);
+ }
+ }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- It looks like we have nothing to show you right now. It could be that we have not yet discovered all your devices but it is more likely that you have not configured Home Assistant yet.
-
-
- Please see the Getting Started section on how to setup your devices.
-
-
-
-
-
-
-
-
-
-
-
Hi there!
It looks like we have nothing to show you right now. It could be that we have not yet discovered all your devices but it is more likely that you have not configured Home Assistant yet.
Please see the Getting Started section on how to setup your devices.
- It looks like we have nothing to show you right now. It could be that we have not yet discovered all your devices but it is more likely that you have not configured Home Assistant yet.
-
-
- Please see the Getting Started section on how to setup your devices.
-
-
-
-
-
-
-
-
-
-
-
- [[computeHeaderTitle(filter)]]
Hi there!
It looks like we have nothing to show you right now. It could be that we have not yet discovered all your devices but it is more likely that you have not configured Home Assistant yet.
Please see the Getting Started section on how to setup your devices.